Upgraded by beta site to 13.0.0beta1. When visiting the "Check for Updates" tab under Plugins I get this:
Fatal error: Uncaught --> Smarty Compiler: Syntax error in template "file:/usr/local/piwigo-beta/admin/themes/default/template/updates_ext.tpl" on line 212 "{/foreach}" unclosed {if} tag <-- thrown in /usr/local/piwigo-beta/include/smarty/libs/sysplugins/smarty_internal_templatecompilerbase.php on line 212
Tried purging compiled templates under Maintenance but that didn't fix it. Also noticed on the Maintenance page that the styling for the "Purge Sessions" button is messed up so the text on that button is larger than the rest.
Environment
Piwigo 13.0.0beta1
Operating system: Linux
PHP: 8.0.8 (Show info) [2022-03-24 18:57:06]
MySQL: 8.0.28-0ubuntu0.21.10.3 [2022-03-24 18:57:06]
Graphics Library: ImageMagick 6.9.11-60
Cache size 292.38 Mo calculated 1 minute ago Refresh
Activated plugin list
Admin Tools
Advanced Menu Manager
Batch Manager, Photo Description
Extended Description
Grum Plugins Classes.3
LocalFiles Editor
Photo Update
Physical Photo Move
Read Metadata
Rotate Image
RV Thumb Scroller
Thumbnail Tooltip
VideoJS
Write Metadata
Offline
Ok, for this one it looks like there's a missing {/if} in admin/themes/default/template/updates_ext.tpl that needs to go with {if $isWebmaster == 1} on line 165. I just added it to the end of the file and that let the page load without error.
[Github] Piwigo issue #1643
Offline
Also logged [Github] Piwigo issue #1645 for the "Purge Sessions" text being too large.
Offline
Both issues still present in beta2. Same template error occurs if I navigate via Tools > Updates > Extension Updates (https://site/admin.php?page=updates&tab=ext).
Last edited by windracer (2022-05-10 23:17:49)
Offline
The "check for updates" issue has been fixed in RC1 (thanks!) but the large "purge sessions" text is still present.
Offline
Hello,
An issue is open about this, it will be fixed for the 13RC2 release.
See -> [Github] Piwigo issue #1645
Have a good day !
Offline
Matthieulp wrote:
Hello,
An issue is open about this, it will be fixed for the 13RC2 release.
I'm the one who logged the issue. :-) Thank you!
Offline
Confirming this was fixed in RC2. Thanks!
Offline