Let's take an example : you're running plugin SmartAlbums 14.a and you update it to 16.c with the Piwigo provided UI.
Unfortunately we have discovered and understood that a powerful magic behind the opcache system prevents PHP from reloading the new maintain.class.php provided in the zip file. The result is that even after extracting SmartAlbums 16.c files (including the new maintain.class.php) the update action from the 14.a is actually performed 😢
We need to force Piwigo to reload it before using it.
Related to https://fr.piwigo.org/forum/viewtopic.php?id=31122
Let's take an example : you're running plugin SmartAlbums 14.a and you update it to 16.c with the Piwigo provided UI.
<img width="912" height="368" alt="Image" src="https://github.com/user-attachments/assets/40fdd749-5312-4de0-ab24-eca9c2b9d556" />
Unfortunately we have discovered and understood that a powerful magic behind the opcache system prevents PHP from reloading the new `maintain.class.php` provided in the zip file. The result is that even after extracting SmartAlbums 16.c files (including the new `maintain.class.php`) the update action from the 14.a is actually performed 😢
We need to force Piwigo to reload it before using it.
<!-- github-sync-id:4344013820 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Related to https://fr.piwigo.org/forum/viewtopic.php?id=31122
Let's take an example : you're running plugin SmartAlbums 14.a and you update it to 16.c with the Piwigo provided UI.
Unfortunately we have discovered and understood that a powerful magic behind the opcache system prevents PHP from reloading the new
maintain.class.phpprovided in the zip file. The result is that even after extracting SmartAlbums 16.c files (including the newmaintain.class.php) the update action from the 14.a is actually performed 😢We need to force Piwigo to reload it before using it.