Author
Topic: Minigallery (v2.5.0) - better again (Read 1996 times)

Minigallery (v2.5.0) now has the possibility to sort the images. No more naming the images to get them in the correct alphabetical order.Just drag and drop them around in the backend and sorting is done.

Since version 2.4.0 a new justify script was added that is used for both the square thumbnails as well as when they are different sized.

Captions are also added and the possibility to delete per single image is there now (since version 2.3.0).Bulk upload was the other big improvement of that version. Just drop your complete album in the module upload section and it should work.

I have deleted all images, the directories wash empty afterwards.I changed the line 210 so.Then the pictures uploaded again via the BE from the module and the pictures updated.The error message still appears.

The message is shown by WB when your error-reporting is set to "Development" mode.For some reason WB switches off the standard way of suppressing errors (using the @ character) when this setting is used.

Somehow the minigallery sorting does not work.I can't explain it, i have inserted the photos with sort numbers about 9000 but seems it has no effect.Manually dragging file works, but number to sql comes 99 107 or similiar.

In the code there is sort parameter many place but no sort setting in the admin gallery settings ?

Somehow the minigallery sorting does not work.I can't explain it, i have inserted the photos with sort numbers about 9000 but seems it has no effect.Manually dragging file works, but number to sql comes 99 107 or similiar.

Not really sure what you mean here..

Remember that for sorting routines 10000 comes before 99.Sorting is initially done per filename characters , so the 1 from 10000 is lower than the 9 from 99.If you want to sort numeric imagenames correctly use 00001, 00002 etc..

After this first load the sorted filenames are stored in the settings and you can drag&drop them around for manual sorting. Any additional uploads will be appended behind the existing sortlist (sorted on filename) whenever the images are reloaded (either backend/frontend page refresh).

PHP-Error in WB-Options is "Developer"because it is a developer environment and there WebsiteBaker is tried to code without "messages" in the ErrorLog.For testing purposes we also install all modules from our own repro and popular modules there.

Extended error handling The already existing error handling in WB 2.10.0 has been extended by a few setting possibilities. The error reporting setting in the WB options has been re-enabled. The following settings are possible:

"Switched Off" = No error messages. "Production Mode" = All error messages are not suppressed by the @error control operator. "Developer Mode" = Show all error messages, even those with @error control operator.

the @ is a allowed php-error control operator and in use, if you know, a empty answer for a special request is possible, but not the standard answer.it's not a real error, it's a info, that you suppress somewhere a information from the script with the @error control operator.

Warning: imagecreatetruecolor(): Invalid image dimensions in /var/www/xxxx/modules/minigal2/functions.php on line 169

Warning: imagecopyresampled() expects parameter 1 to be resource, boolean given in /var/www/xxxx/modules/minigal2/functions.php on line 187

Warning: imagejpeg() expects parameter 1 to be resource, boolean given in /var/www/xxxx/modules/minigal2/functions.php on line 195

Warning: imagedestroy() expects parameter 1 to be resource, boolean given in /var/www/xxxx/modules/minigal2/functions.php on line 203this seems to be some kind of problem of my php / website baker creating dir & filesthat does not have enough permissions..

Tried to reproduce the warning on PHP 7.2.13. (minigal2 v2.5.1)For me it seems to work ok. No problems or warnings.

The warning is caused because the function "imagecreatetruecolor" is called with wrong parameters.These parameters are basically created by the call in line 102 ( $info = getimagesize($source); )The manual for the PHP function getimagesize says to be sure the file is a valid image or it will giive unexpected result (without failure). So it could be one of the images in the directory is corrupt or not an image at all.

possible, that you add some pic's via FTP there? maybe, a hidden file inside of this folder (not every ftp-client show all files in the default settings).i test it with different PHP-Version (7.2.0, 7.2.8, 7.3.0), no problems

this part of the script build's the preview-thumbs for this sectionthe 4 warnings in your last message show's everywhere the same problem. this four functions works with a path or the informations from there. (for example: if getimagesize() has no informations about the size, this size is missing in the next function imagecopyresampled() ). equal in all this functions is the source path to the image. Ruud write the answer: a image (or the info inside of the image) is broken or the selected file is not an image

try to call all images in this folder step by step in a browser. you can also delete all the thumbs in this yolder /media/minigal2/[your-section-id]/thumbs and reload the section in you wb-backend again, then compare the pictures in this picture folder with the pictures in the thumb-folder. normalize, the script breaks in this step with the result, that one pic is missing in the thumb-folder - so you found the source picture with the problem

if the problem coms again, we can set some exeption inside of this function, so that you see, what the source is