Freemius loaded on frontend
-
Hello,
I’m the author of Freesoul Deactivate Plugins. A user of FDP reported an issue with your plugin, please, read here for more details.
FDP gives the possibility to selectively disable plugins where you don’t need them.
However, when it detects the class FS_Plugin_Updater provided by Freemius, it will not deactivate any plugin. If it did it, the users may see some plugins globally deactivated without their intention, because inside the Freemius class FS_Plugin_Updater there is code that saves the WP core option active_plugins in some situations. If this happens when FDP applies its filter to the same option, that option is saved with the wrong set of active plugins.Freemius should never save the option active_plugins, no code that isn’t the WP core should do it. FDP only filters that option. However, Freemius does it in some situations, and the only way FDP has to prevent a disaster is by keeping all the plugins active before Freemius saves that option.
By doing that FDP can work with most plugins that use Freemius because they practically all load Freemius only in the backend when needed, but your plugin does it also on the frontend during a normal page loading.
This is both bad for performance and a conflict with FDP.Is it possible for you to load Freemius only when your plugin needs to send data to Freemius? At least not when a normal page loads on the frontend?
Thank you in advance
Best regards
Jose
- The topic ‘Freemius loaded on frontend’ is closed to new replies.