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: Publisher Preview iFrame
| Status | Resolved |
| Add-on / Version | Publisher 1.7.1 |
| Severity | |
| EE Version | 2.11.3 |
Fabcom
Dec 05, 2016Wondering if you’ve ever heard from anyone reporting that the “preview” modal, that Publisher pops up when an edit is committed, is blank? Normally this would display the edited/published page.
It is only blank for pages/entries that have already been published.
BoldMinded (Brian)
This would be the first I’ve heard of such a thing. Did you inspect the iframe to see if its loading any html? What about taking the iframe url and just loading it into a new browser tab?
BoldMinded (Brian)
Would also need to know a lot more about the page… is it a Pages/Structure page or is it a template path url? Did you configure custom preview templates? What is in the template that you’re trying to view? What status did you save it as? If draft, did you include the {publisher:entry_status} variable in the entry tag (see the docs)? Have you tried simplifying the page and removing all tags to see if it rendered, then started adding html content back until it breaks?
Fabcom
Yes the iframe SRC URL works just fine when pasted into a browser. The iframe contains the string “#document” followed by what is essentially an empty HTML structure (html/head/body tags… all empty) before the closing iframe tag.
This is not a single page based on a single template. It is several hundred Pages/Structure pages based on dozens of templates. It only happens on an edit of an already published page. New page/entry drafts and first-time publishes render fine. In other words, this seems to be systemic rather than an isolated case of code conflict. “Draft” v.s. “Published” doesn’t make a difference.
We will review your comments re entry_status and report findings.
Thanks.