diff options
author | Sem <sembrestels@riseup.net> | 2013-11-09 16:22:50 +0100 |
---|---|---|
committer | Sem <sembrestels@riseup.net> | 2013-11-09 16:22:50 +0100 |
commit | f448cd91f9ecebea37daf40aada2fa1a20200817 (patch) | |
tree | 4636059da6a1be133a4974e5098b7c1e08944dd5 /mod/lightpics/FAQ.txt | |
parent | 52335325e5ea8c89c711e1ba40d9ac1657004e61 (diff) | |
parent | 324f39c3a9aa41e9e23bafba38882a2b72f62441 (diff) | |
download | elgg-f448cd91f9ecebea37daf40aada2fa1a20200817.tar.gz elgg-f448cd91f9ecebea37daf40aada2fa1a20200817.tar.bz2 |
Add 'mod/lightpics/' from commit '324f39c3a9aa41e9e23bafba38882a2b72f62441'
git-subtree-dir: mod/lightpics
git-subtree-mainline: 52335325e5ea8c89c711e1ba40d9ac1657004e61
git-subtree-split: 324f39c3a9aa41e9e23bafba38882a2b72f62441
Diffstat (limited to 'mod/lightpics/FAQ.txt')
-rw-r--r-- | mod/lightpics/FAQ.txt | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/mod/lightpics/FAQ.txt b/mod/lightpics/FAQ.txt new file mode 100644 index 000000000..2f0de8165 --- /dev/null +++ b/mod/lightpics/FAQ.txt @@ -0,0 +1,31 @@ +White screen when uploading images +================================== +Tidypics tries to calculate the maximum size of an image that your server will support. If it +guesses incorrectly and someone uploads a photo that is too large, the script may crash when +resizing the image if you are using GD. The easiest way to test this is to set display_errors +to 1 in your .htaccess file and upload large images. If this causes a problem, a php memory error +should display on the screen. You can increased your php memory limit. A better option is to use +imagick if your server supports it (again see the docs directory). + +If it is not a memory issue, you should see some other error appear. Once you have fixed the error, +change display_error back to 0. + + +Question mark images appear +=========================== +If you see question mark images when you look at your albums, this means the resizing of the images +failed. This could be due to the memory limits as described above. There are other causes. Tidypics +tries to detect these problems and write the cause to the error log. You should check your server +error log right after an upload that results in a question mark for these error messages. The messages +will begin with "Tidypics warning:". It is possible if you have turned off php warnings that you will +not see these warnings. + +Another possible cause is using command line ImageMagick when your server does not +support it or specifying the wrong path to the ImageMagick executables. + + +Unable to save settings +======================= +If you are unable to settings, Apache may be configured to block pages that use +file paths as Tidypics does when setting the location of the ImageMagick executable. +In this case, leave that field blank. |