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: Error when upgrading from Publisher 2.10.7 to 3.1.5

Status	Resolved
Add-on / Version	Publisher 3.1.5
Severity
EE Version	5.3.2

Mighty Citizen

Jun 09, 2020

Hello! We’re trying to upgrade Publisher on a site from 2.10.7 to 3.1.5. After moving over the addon files and the theme files we just see this error when trying to access the Control Panel to complete the upgrade:

Fatal error: Uncaught Error: Call to undefined method Basee\App::isInstallingOrUninstallingAddon() in /.../system/user/addons/publisher/ext.publisher.php:2125 
Stack trace: 
#0 /.../system/user/addons/publisher/ext.publisher.php(325): Publisher_ext->validateInstallation() 
#1 /.../system/ee/legacy/libraries/Extensions.php(222): Publisher_ext->core_boot() 
#2 /.../system/ee/legacy/libraries/Extensions.php(117): EE_Extensions->call_class('Publisher_ext', 'core_boot', Array, Array) 
#3 /.../system/ee/legacy/core/Controller.php(85): EE_Extensions->call('core_boot') 
#4 /.../system/ee/legacy/core/Controller.php(99): EE_Controller->__construct() 
#5 /.../system/ee/EllisLab/ExpressionEngine/Controll in /../system/user/addons/publisher/ext.publisher.php on line 2125

This is on a development server running PHP 7.2.31and MySQL 5.6.

Thanks!

BoldMinded (Brian)

That error means there is a 99% chance you have other Boldminded addons that need to be upgraded to the latest versions too.

Mighty Citizen

Strange - I spun up a new environment and didn’t run into this issue there, so I’ll try to narrow down the difference. The only other Boldminded addons we have on this site are Bloqs and Publisher NavEE Support. Bloqs is slightly behind (4.0.19) so I’ll upgrade that on the environment with the error to rule that out.

Thanks for your help!

BoldMinded (Brian)

Doesn’t help now, but the next releases of my add-ons should avoid this issue, but this is almost certainly an issue with other add-ons being out of date. They all share the same Basee Composer package, and due to a lack of global Composer support in EE there can be file load order issues when multiple add-ons share the same package. I.e. an outdated package is getting loaded first, then 3 other add-ons might end up referencing that out-of-date file instead of the new one in it’s own folder.