I have a reference in my personal plugin to the path constant defined by another plugin (Community) and when I ran the update that recently appeared on my 16.0.0RC3 install the process failed due to a PHP error of that constant not being defined.
I could rewrite my personal plugin to check the plugins table first but I wonder if there is a way for the update process to run in a fail safe manner relative to the other plugins, or at least the personal plugin?
Offline
Hi :-)
Piwigo RC versions are for testing purposes only.
The update process in RC is for developers. ;-)
Offline
I am using the RC version for testing. I am trying to determine if Piwigo can be configured or extended to satisfy a particular use case so its not yet deployed in production.
I had done some plugin updates before but I hadn't noticed that the plugin being updated would deactivate meaning that in the case I observed its path constant was temporarily unavailable.
Does your statement mean that in the regular release version the built-in update process does not temporarily deactivate the plugin?
I have already rewritten my local-only plugins and the code I have in the personal plugin where this was an issue, but if that is a unique artifact of the development version then its irrelevant.
Offline
Hi :-)
Thank you for the feedback, it is appreciated.
In minor version upgrades, plugins are not disabled.
In major version upgrades, plugins are disabled. the personal plugin as well, normally
Offline