You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker image linuxserver/piwigo or scr.io/linuxserver/piwigo:latest
This issue does not appear, if Piwigo is installed via the manual installation instructions
Symptoms
After requesting the zip file by the cloud button of Batch Downloader the browser reports an HTTP Error 500
In the nginx error.log messages like the following appear:
2024/09/28 11:29:08 [error] 294#294: *7179 FastCGI sent in stderr: "PHP message: PHP Warning: include(../../include/common.inc.php): Failed to open stream: No such file or directory in /config/www/plugins/BatchDownloader/download.php on line 3; PHP message: PHP Warning: include(): Failed opening '../../include/common.inc.php' for inclusion (include_path='.:/usr/share/php83') in /config/www/plugins/BatchDownloader/download.php on line 3; PHP message: PHP Fatal error: Uncaught Error: Call to undefined function check_status() in /config/www/plugins/BatchDownloader/download.php:5
Not your fault but others might see the same issue
I am aware, this is not directly a Batch Downloader issue, but caused by the set up of the docker image. But many Piwigo administrators do use docker to run Piwigo and might interprete this as a Batch Downloader issue first.
Environment
This issue does not appear, if Piwigo is installed via the manual installation instructions
Symptoms
Not your fault but others might see the same issue
I am aware, this is not directly a Batch Downloader issue, but caused by the set up of the docker image. But many Piwigo administrators do use docker to run Piwigo and might interprete this as a Batch Downloader issue first.
I also reported this to the maintainer of the Piwigo docker image.
Workaround
Adjust the path in to the plugin/BatchDownloader/download.php script:
After this change the issue does not exist anymore in this environment.
The text was updated successfully, but these errors were encountered: