aboutsummaryrefslogtreecommitdiff
path: root/views/default/tidypics/admin/help.php
diff options
context:
space:
mode:
authorCash Costello <cash.costello@gmail.com>2012-07-13 22:02:22 -0400
committerCash Costello <cash.costello@gmail.com>2012-07-13 22:02:22 -0400
commit695651451b262c526d6aaf9d0988ce557ff50e95 (patch)
tree92afd91c81f851e78dd87af0e1f6c2f848f5a8b2 /views/default/tidypics/admin/help.php
parenta2e4f84be4da51b7ec8fbe625b1b26dde2ad9289 (diff)
parent67d855d73499f36f15331e1ff18cccd13aa8aa74 (diff)
downloadelgg-695651451b262c526d6aaf9d0988ce557ff50e95.tar.gz
elgg-695651451b262c526d6aaf9d0988ce557ff50e95.tar.bz2
Merging admin changes from Brett's repo
Diffstat (limited to 'views/default/tidypics/admin/help.php')
-rw-r--r--views/default/tidypics/admin/help.php32
1 files changed, 0 insertions, 32 deletions
diff --git a/views/default/tidypics/admin/help.php b/views/default/tidypics/admin/help.php
deleted file mode 100644
index b939a74a8..000000000
--- a/views/default/tidypics/admin/help.php
+++ /dev/null
@@ -1,32 +0,0 @@
-<br />
-<h3>White screen when uploading images</h3>
-<p>
-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 (see the docs directory).
-A better option is to use ImageMagick if your server supports it (again see the docs directory).
-</p><p>
-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.
-</p>
-<h3>Question mark images appear</h3>
-<p>
-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.
-</p><p>
-Another possible cause is using ImageMagick when your server does not support it or specifying
-the wrong path to the ImageMagick executables.
-</p>
-<h3>Unable to save settings</h3>
-<p>If you are unable to settings, there are two possible causes. First,
-Apache can 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. Second, there is some bad code in the Izaps video
-plugin that can prevent the settings from being saved. Try disabling that plugin.
-</p> \ No newline at end of file