Hi I'm receiving this message every time I try to enable a deactivated plugin, I first thought it was related to the plugin themselves, but installed from the gallery plugins released today and the problem remains, so I can't activate any plugin and if I force them the gallery crashes and I have to do a manual upgrade procedure for it to come up again.
What can be wrong? It worked flawlessly with piwigo 11, the problem appeared when I upgraded to 12.1
Thanks!
Environment
Piwigo 12.1.0 Check for upgrade
Operating system: Linux
PHP: 7.4.25 (Show info) [2021-11-18 21:21:50]
MySQL: 5.7.36 [2021-11-18 21:21:50]
Graphics Library: GD bundled (2.1.0 compatible)
Cache size 0 Mo calculated 1 hour ago Refresh
Activated plugin list4
Admin Tools
Language Switch
LocalFiles Editor
Take A Tour of Your Piwigo
Piwigo URL: http://peu.net
Offline
Removed all files but the folders in the manual update tutorial,
removed all plugins from the plugin folder,
uncompressed piwigo 12.1,
waited for the site to come up.
Only the plugins in the package appear.
went to other plugins available tab,
looked for gdthumb, installed it
when I try to activate it it gives the error I posted above.
Tried other plugin, fotorama, same thing happens...
purged the user cache, nothing changes
if I force enable the plugin and go to its settings the site crashes and I have to start from the first line in this post.
Last edited by PEU (2021-11-19 03:13:35)
Offline
Same issue here. I completed the same steps prior to seeing your message, and my outcome was the same. I appear to be stuck in this spot. I hope there is someone out there who has encountered this as well and had some success in resolving it.
Offline
RESOLVED: I turned on the developer tools in Chrome and watched for error messages when trying to enable plugins. I saw a 403 error and did some research through the forum threads.
The problem is related to MOD_SECURITY rule 941130. I disabled that on the server and everything is working perfectly now.
Of course... now I'm wondering if there is a way to modify the rule rather than disabling it. It seems like an security rule serves a purpose and disabling it might have some negative consequences. I welcome anyone's input/advice/instruction on this matter.
Offline
You can define exceptions to ModSecurity rules. Don't ask me how or which specifically for this problem. Search the net. General pointer to documentation https://github.com/SpiderLabs/ModSecurity/wiki/
Offline
I was seeing the same behavior with piwigo 12+. I tracked it down to a faulty language file, I believe it was sl_SI.php.
It has what appear to be some malformed php code lines of the form:
';
Probably from a script error.
When I commented out those lines the plugin error went away and piwigo stopped hanging.
To debug it, I looked in _data/logs.
-Randy
Offline
language/sl_SI/admin.lang.php was fixed already in January with [Github] Piwigo commit f46404b4 .
Offline
Piwigo 13.6.0 Проверить обновления
Installed on 29 Апрель 2023, 18 секунды назад
Операционная система: Linux
PHP: 7.4.27 (Показать информацию) [2023-04-29 13:49:01]
MySQL: 5.7.36-cll-lve [2023-04-29 16:49:01]
Библиотека изображений: External ImageMagick 6.9.10-68
When you try to enable the plugin, an error appears and the plugin is not activated. The file admin.lang.php has been checked and there are no errors. What to do?
Offline