After upgrade from 13.8 to 14.1 when I try search function I got error
"Unknown column 'search_uuid' in 'where clause' SELECT COUNT(*) FROM piwigo_search WHERE search_uuid = 'psk-20240109-8txoOz4znJ' ; in /var/www/html/piwigo/include/dblayer/functions_mysqli.inc.php on line 847"
No errors in upgrade_feed.php (0 upgrades to apply)
Environment
Before updating
Piwigo 13.8.0 Check for updates
Installed April 8, 2023, 9 months/months 1 day ago
Operating system: Linux (Debian GNU/Linux 11 (bullseye))
PHP: 7.4.33 (Show info) [2024-01-09 22:21:56]
MySQL: 5.5.5-10.5.18-MariaDB-0+deb11u1 [2024-01-09 22:21:56]
Graphics Libraries: GD 2.3.0
Cache size 2068.42 MB now Refresh
After updating
Piwigo 14.1.0 Check for updates
Installed April 8, 2023, 9 months/months 1 day ago
Operating system: Linux
PHP: 7.4.33 (Show info) [2024-01-09 22:28:05]
MySQL: 5.5.5-10.5.18-MariaDB-0+deb11u1 [2024-01-09 22:28:05]
Graphics Libraries: GD 2.3.0
Cache size 2056.59 MB calculated now Refresh
After upgrade from 13.8 to 14.1 when I try search function I got error
"Unknown column 'search_uuid' in 'where clause' SELECT COUNT(*) FROM piwigo_search WHERE search_uuid = 'psk-20240109-8txoOz4znJ' ; in /var/www/html/piwigo/include/dblayer/functions_mysqli.inc.php on line 847"
No errors in upgrade_feed.php (0 upgrades to apply)
Environment
Before updating
Piwigo 13.8.0 Check for updates
Installed April 8, 2023, 9 months/months 1 day ago
Operating system: Linux (Debian GNU/Linux 11 (bullseye))
PHP: 7.4.33 (Show info) [2024-01-09 22:21:56]
MySQL: 5.5.5-10.5.18-MariaDB-0+deb11u1 [2024-01-09 22:21:56]
Graphics Libraries: GD 2.3.0
Cache size 2068.42 MB now Refresh
After updating
Piwigo 14.1.0 Check for updates
Installed April 8, 2023, 9 months/months 1 day ago
Operating system: Linux
PHP: 7.4.33 (Show info) [2024-01-09 22:28:05]
MySQL: 5.5.5-10.5.18-MariaDB-0+deb11u1 [2024-01-09 22:28:05]
Graphics Libraries: GD 2.3.0
Cache size 2056.59 MB calculated now Refresh

<!-- github-sync-id:2073154758 -->
Can you show us the structure of your table piwigo_search ?
And also, the latest lines in your table piwigo_upgrade?
Can you show us the structure of your table `piwigo_search` ?
And also, the latest lines in your table `piwigo_upgrade`?
<!-- github-comment-id:1898265725 -->
For me it's an upgrade issue. Please run upgrade.php or see our upgrade guide https://piwigo.org/guides/update/manual
<!-- github-comment-id:1908091705 -->
On Thu, 18 Jan 2024 03:04:59 -0800
Pierrick Le Gall @.***> wrote:
Can you show us the structure of your table piwigo_search ?
And also, the latest lines in your table piwigo_upgrade?
Hello Pierrick
Thank You for the update.
Sorry I didn't reply, but I've been very busy lately and haven't had
time to debug the problem in the database.
Regards
Chrisopher
On Thu, 18 Jan 2024 03:04:59 -0800
Pierrick Le Gall ***@***.***> wrote:
> Can you show us the structure of your table `piwigo_search` ?
> And also, the latest lines in your table `piwigo_upgrade`?
>
Hello Pierrick
Thank You for the update.
Sorry I didn't reply, but I've been very busy lately and haven't had
time to debug the problem in the database.
Regards
Chrisopher
<!-- github-comment-id:1908132104 -->
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.
After upgrade from 13.8 to 14.1 when I try search function I got error
"Unknown column 'search_uuid' in 'where clause' SELECT COUNT(*) FROM piwigo_search WHERE search_uuid = 'psk-20240109-8txoOz4znJ' ; in /var/www/html/piwigo/include/dblayer/functions_mysqli.inc.php on line 847"
No errors in upgrade_feed.php (0 upgrades to apply)
Environment
Before updating
After updating
Can you show us the structure of your table
piwigo_search?And also, the latest lines in your table
piwigo_upgrade?For me it's an upgrade issue. Please run upgrade.php or see our upgrade guide https://piwigo.org/guides/update/manual
On Thu, 18 Jan 2024 03:04:59 -0800
Pierrick Le Gall @.***> wrote:
Hello Pierrick
Thank You for the update.
Sorry I didn't reply, but I've been very busy lately and haven't had
time to debug the problem in the database.
Regards
Chrisopher