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
Lychee says php.exec() is optional, but it is used in one step of the installation and later used by exif when uploading a photo.
Situation 1:
Install lychee from the 4.0.0 release with php.exec() function disabled (In my case it is disabled by the system administrator and it cannot be activated) and get an error with 500 status code on the final step of the installation (after configuring the .env variables from the GUI).
I modified the following files to bypass the version check using exec(). These were the files that caused problems in proceding with the installation process mentioned above.
1.-Lychee/database/migrations/2019_12_25_0600_config_exiftool_ternary.php
- failed on line 23
2.- Lychee/database/migrations/2020_01_04_1200_config_has_ffmpeg.php
- failed on line 24
I knew this because the error page showing the status code 500 mentioned one of these files. I tried to bypass one, then the error page reapeared but this time pointing the error to a different file. It stoped after modifying the second file.
Then i could install lychee with no problems.
Situation 2:
1.- Try to upload a photo in any directory using the super admin account.
Diagnostics
-----------
Warning: Dropbox import not working. dropbox_key is empty.
Warning: You may experience problems when uploading a photo of large size. Take a look in the FAQ for details.
Warning: You may experience problems when uploading a photo of large size. Take a look in the FAQ for details.
Warning: You may experience problems when uploading a photo of large size or handling many/large albums. Take a look in the FAQ for details.
Warning: exec function has been disabled. You may experience some error 500, please report them to us.
Error: PHP zip extension not activated
Description of the problem
Lychee says php.exec() is optional, but it is used in one step of the installation and later used by exif when uploading a photo.
Situation 1:
Install lychee from the 4.0.0 release with php.exec() function disabled (In my case it is disabled by the system administrator and it cannot be activated) and get an error with 500 status code on the final step of the installation (after configuring the .env variables from the GUI).
I modified the following files to bypass the version check using exec(). These were the files that caused problems in proceding with the installation process mentioned above.
1.-Lychee/database/migrations/2019_12_25_0600_config_exiftool_ternary.php
- failed on line 23
2.- Lychee/database/migrations/2020_01_04_1200_config_has_ffmpeg.php
- failed on line 24
I knew this because the error page showing the status code 500 mentioned one of these files. I tried to bypass one, then the error page reapeared but this time pointing the error to a different file. It stoped after modifying the second file.
Then i could install lychee with no problems.
Situation 2:
1.- Try to upload a photo in any directory using the super admin account.
When trying to upload a photo, exif uses exec() to get the path of the tool it is going to use.
https://github.com/LycheeOrg/php-exif/blob/568b56c6b33cca87dcb56103d1d1eb0609091def/lib/PHPExif/Adapter/Exiftool.php
on line 99
Output of the diagnostics [REQUIRED]
Diagnostics
-----------
Warning: Dropbox import not working. dropbox_key is empty.
Warning: You may experience problems when uploading a photo of large size. Take a look in the FAQ for details.
Warning: You may experience problems when uploading a photo of large size. Take a look in the FAQ for details.
Warning: You may experience problems when uploading a photo of large size or handling many/large albums. Take a look in the FAQ for details.
Warning: exec function has been disabled. You may experience some error 500, please report them to us.
Error: PHP zip extension not activated
Browser and system
Lychee hosted on Centos 7
The text was updated successfully, but these errors were encountered: