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: Warning and Notice on none-english language site
| Status | Resolved |
| Add-on / Version | Publisher 3.10.2 |
| Severity | |
| EE Version | 7.3.12 Pro |
Dotcom Developers
Nov 17, 2023Hello!
After upgrading Publisher to version 3.10.2 (from 3.10.1) we run into the issue. After switching to other languages (jp, zh-cn, zh-tw) some of the pages display an error (see on the screenshot). There are no rendered content, only site error. After rollback to previous version 3.10.1, everything is working well.
Second issues appear, when we will go in Control Panel to “Add-ons -> Publisher -> Pending Approvals” we see warning:
Trying to get property ‘screen_name’ of non-object
.../addons/publisher/Service/Approval/ApprovalTableRenderer.php, line 55
Thanks for help!
BoldMinded (Brian)
What version of PHP are you running these days?
Dotcom Developers
Comment has been marked private.
BoldMinded (Brian)
Curious why member_data is null. Change line 55 to this, at least it fixes the error.
$entryApproval->data->member_data->screen_name ?? ‘unknown’,
Dotcom Developers
Comment has been marked private.
BoldMinded (Brian)
The parsing error is b/c it’s trying to re-write the hidden and encoded form field values to append a language segment to any of the form return and submit urls. I don’t actually see the errors on any of those pages even after bypassing the cache. Anyway, based on the error and line number I think it’s from an attempted PHP 8.x fix. The next comment will include a new build that is using Symfony’s Polyfill for the mb string methods, so it should fix the issue and work regardless of the version of PHP.
BoldMinded (Brian)
Comment has been marked private.
Dotcom Developers
Comment has been marked private.