Many users have updated their Piwigo to version 12. We're happy to have "not so many" problems due to specific environments but still... the community has detected bugs and here is the first list of issues fixed!
Piwigo 12.1.0 release note
Photo by Ryan Stone on Unsplash
Offline
Offline
With your webmaster role account being logged in, the Admin -> Dashboard page displays if there are upgrades available, Piwigo and extensions. Just click the first Piwigo upgrade, in this case it will also upgrade the accompanying extensions. You can also use Admin -> Tools -> Updates to check and install, it's the same page clicking the Dashboard link leads to.
Offline
erAck wrote:
With your webmaster role account being logged in, the Admin -> Dashboard page displays if there are upgrades available, Piwigo and extensions. Just click the first Piwigo upgrade, in this case it will also upgrade the accompanying extensions. You can also use Admin -> Tools -> Updates to check and install, it's the same page clicking the Dashboard link leads to.
Yes, I was hoping for instructions about whether an upgrade would overwrite any customisations, or any other caveats I should be aware of.
Last edited by cbiweb (2021-11-12 15:38:46)
Offline
It will overwrite only distribution source files, so if you didn't modify any of those there's nothing to adapt. It won't touch configuration, template, css or translation changes under local/
Offline
Perhaps the question should be asked of the plugin developers? Piwigo is the platform on which these developers write plugins for. Not the other way around. The effort for plugins is user and/or community contribution, not Piwigo.
nobby wrote:
Hello,
Why are the plugins not adapted before the new Piwigo release?
The way it is handled at the moment is counterproductive.
I will only initiate an update when all my plugins in use have been adapted.
nobby
Offline
Just upgraded to 12.1.0 from a working installation which was at the latest version working well. System is CentOS, PHP 7.2. After clicking the link in the notification email, it throws the error below. I did try to run upgrade_feed.php and upgrade.php again to no avail. Other than the broken Admin functions (Tools, Configuration...), the gallery works fine. Here's the error:
Warning: Use of undefined constant LOUNGE_TABLE - assumed 'LOUNGE_TABLE' (this will throw an Error in a future version of PHP) in /VirtualHost/photos.****.com/admin/include/functions.php on line 3271
Warning: [mysql error 1146] Table 'piwigo-photos.LOUNGE_TABLE' doesn't exist
SELECT
image_id
FROM LOUNGE_TABLE
; in /VirtualHost/photos.****.com/include/dblayer/functions_mysqli.inc.php on line 864
Fatal error: Uncaught Error: Call to a member function fetch_assoc() on boolean in /VirtualHost/photos.****.com/include/dblayer/functions_mysqli.inc.php:925 Stack trace: #0 /VirtualHost/photos.****.com/admin/include/functions.php(3273): query2array('\nSELECT\n ima...', NULL, 'image_id') #1 /VirtualHost/photos.****.com/admin.php(254): get_orphans() #2 {main} thrown in /VirtualHost/photos.****.com/include/dblayer/functions_mysqli.inc.php on line 925
Offline
nobby wrote:
Why are the plugins not adapted before the new Piwigo release?
The way it is handled at the moment is counterproductive.
I will only initiate an update when all my plugins in use have been adapted.
[Forum, topic 31581] Piwigo 12
plg wrote:
We know by experience that you're going to quickly ask for extensions to be compatible with this version 12. As said in [Forum, post 178992 by plg in topic 30882] Piwigo 11 :
plg wrote:
Yes, that's the problem with software having plugins: we do as much as we can to have them compatible with the new version, but we can't wait for them to be all compatible to release the new version (or you would wait forever)
We hope extensions will be made compatible as soon as possible :-)
Offline
Hi,
Manage to update from 11.5 to 12.1 without any issues.
Piwigo inside iocage on TrueNAS + HP Gen8 Microserver.
Offline
It deactivates plugins and themes, and installs a milion languages that I have to delete one by one. Don't do that.
Keep plugins activated.
Keep themes activated.
Don't add languages. Make languages optional downloads for those that need them.
Don't add plugins that are deleted (like the usless "tour").
Offline
It's better to deactivate plugins that are not known to be compatible than rendering the entire gallery or even its admin area inaccessible due to incompatibilities. Similar for themes. What's the point of deleting languages? The TakeATour plugin is always part of the release.
Offline
russmcclay wrote:
Just upgraded to 12.1.0 from a working installation which was at the latest version working well. System is CentOS, PHP 7.2. After clicking the link in the notification email, it throws the error below. I did try to run upgrade_feed.php and upgrade.php again to no avail. Other than the broken Admin functions (Tools, Configuration...), the gallery works fine. Here's the error:
Warning: Use of undefined constant LOUNGE_TABLE - assumed 'LOUNGE_TABLE' (this will throw an Error in a future version of PHP) in /VirtualHost/photos.****.com/admin/include/functions.php on line 3271
Warning: [mysql error 1146] Table 'piwigo-photos.LOUNGE_TABLE' doesn't exist
SELECT
image_id
FROM LOUNGE_TABLE
; in /VirtualHost/photos.****.com/include/dblayer/functions_mysqli.inc.php on line 864
Fatal error: Uncaught Error: Call to a member function fetch_assoc() on boolean in /VirtualHost/photos.****.com/include/dblayer/functions_mysqli.inc.php:925 Stack trace: #0 /VirtualHost/photos.****.com/admin/include/functions.php(3273): query2array('\nSELECT\n ima...', NULL, 'image_id') #1 /VirtualHost/photos.****.com/admin.php(254): get_orphans() #2 {main} thrown in /VirtualHost/photos.****.com/include/dblayer/functions_mysqli.inc.php on line 925
No comments on this?
Offline