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: Uninstalling add-on causing legacy facade issue

Status Resolved
Add-on / Version Publisher Lite 3.10.3
Severity
EE Version 7.3.14

Ben Houghton

Dec 07, 2023

I have a core_boot extension hook getting called in my own code that adds a config value to the global javascript object. This works as expected and is not impacted by adding/removing any other add-on, but when I uninstall publisher lite my core_boot extension can no longer access the javascript facade and causes fig_1.

When it gets into this state I need to check if the javascript library is set, and if not get ee to load it again.

if (! isset(ee()->javascript)) {
    ee()->load->library('javascript');
}

ee()->javascript->set_global ....

Whilst this does get me back into a working state it injects

<script type="text/javascript" charset="utf-8" src="https://dev.my.domain.com/js"></script>

into the CP page with all the other scripts. Then my console is complaining that that new src path can not be found. I would much prefer if the core_boot hook was called after EE has loaded all the libraries as I know the javascript library would already there so I could just add my global variable after the fact, but unfortunately, that is not the case.

If I reinstall the publisher add on the problem goes away again. I don’t know if there is something getting deregistered that should not be or if any kind of values are not totally getting cleaned up when publisher get uninstalled! Any help you could give on this would be appreciated.

P.S. I don’t think it is a cache thing as I have rebooted the server and tried in incognito and the problem remains, so it smells like some hangover left in the DB perhaps.

#1

BoldMinded (Brian)

If Publisher is un-installed and you’re getting this error then I don’t see how Publisher is relevant in this case.

#2

Ben Houghton

Comment has been marked private.

#3

BoldMinded (Brian)

Comment has been marked private.

Login to reply