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: Unexpected behaviour with non-translated channels entries
| Status | Resolved |
| Add-on / Version | Publisher |
| Severity | Trivial |
| EE Version | 24 |
Filip Vanderstappen
Feb 15, 2013When I mark a channel as ‘Ignored’ in the Publisher settings and create a Structure entry (Page) for it, it all works fine in the Publish layout. I can visit that page on the front-end as long as I’m in the default language.
However, when I try to visit the page after visiting a non-default language page, it’s prefixing the page with the language segment, and throwing a PHP Notice (http://cl.ly/image/2k2u2C1D231y) and the page is not working either.
Removing the language segment results in the same issue. When browsing back to a default language page solves the issue for that language.
Filip Vanderstappen
When a listing channel is ‘ignored’ for translation, the same PHP notice appears when the entry is visited in the default language. (eg: /nl/autos/bmw-520d-touring)
When the entry is visited in an non-default language (eg: /en/cars/bmw-520d-touring) this results in a 404.
BoldMinded (Brian)
Thanks for the report, I’ll try to replicate it this weekend and get a fix out.
BoldMinded (Brian)
Filip, I created a new Products listing channel and set it as ignored and everything worked as expected: http://cl.ly/image/293L0B1v0J3U
Filip Vanderstappen
I’ve been testing this several times on clean environments and I wasn’t able to get this working with the current release of Publisher and Structure. Always getting the undefined offset error.
Am I missing something?
BoldMinded (Brian)
Sent you the 0.98 build, please try it.
BoldMinded (Brian)
Going to close this b/c I think the latest build fixes it. If not, just open a new ticket and reference this one.