This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 2 replies, has 2 voices.
Last updated by 4 years, 6 months ago.
Assisted by: Christian Cox.
Hello, that's odd because a Single Field block should allow you to display on the front-end a link to the file stored in a "file" type custom field. If the field doesn't appear in the Dynamic Sources options, there must be something else going on. In my screenshot here, you can see an example where a File field "book file 1" is available in the Dynamic Sources of a Single Field block. A quick test of this setup shows a link to the file on the front-end of my test site, so it seems to be working in a simple test scenario for me.
- If you create a new custom field while another Block Editor page is open in another browser tab, the new fields will not yet be propagated to the Dynamic Field Sources in the Block Editor. If you refresh the Block Editor page and test again, does the file field appear in Dynamic Sources for the Single Field block?
- Is it possible the wrong field group is selected in your Single Field configurations? Perhaps the file field is in a different field group from the one selected?
- Is the file field in the same post being displayed on the front-end of the site, or is it in a related post type?
- Is the file field set up to allow multiple instances, or is there only one value allowed per post?
