All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Custom fields not visible when previewing unpublished (draft) structure pages
| Status | Resolved |
| Add-on / Version | Publisher Lite 1.6.11 |
| Severity | |
| EE Version | 2.11.2 |
KeesTM
Aug 30, 2016
Hello,
When creating a new page in structure and saving the entry as draft, custom fields are not visible. When saving an entry for the first time as draft, data is stored in the following tables:
exp_channel_titles
exp_publisher_titles
exp_publisher_data
Data is not being saved in exp_channel_data. The following code works for previewing the page with the title, but custom fields are not visible.
{!-- exp:channel:entries channel=“my_channel” dynamic="yes" status="{publisher:entry_status}" publisher_status="draft|open" --}
<h1>Custom fields not visible after previewing unpublished (draft) structure pages</h1>
<p>{custom_plain_textarea_field}</p>
<p>{!-- /exp:channel:entries --}
Steps to reproduce the issue:
1. Create a new structure page with a custom field (e.g. textarea, wygwam)
2. Safe the page as “draft” (do not really publish the page)
3. Try previewing the page
—
Edit 12:34: Changed spelling mistake in title
BoldMinded (Brian)
This is not something I’m able to replicate. When viewing a draft make sure ?publisher_status=draft is in the URL, otherwise {publisher:entry_status} does not work. If the data is not in exp_publisher_data, then you need to disable all other add-ons, or create a new/clean environment, to replicate the issue. Since there are no other similar reports, and I haven’t seen something like this happen in a couple of years, my gut tells me something else is interfering with the data saving.
BoldMinded (Brian)
Closing due to lack of response. Please re-open or create a new ticket referencing this one if this is still an issue.