added server configuration to docs

diff --git a/docs/configure_server.txt b/docs/configure_server.txt
new file mode 100644 (file)
index 0000000..057c4ee
--- /dev/null
+++ b/docs/configure_server.txt
@@ -0,0 +1,51 @@
+Server Configuration\r
+-----------------------------------\r
+\r
+Run your server analysis located in the Tidypics Administration section and \r
+then read through this document.\r
+\r
+If you are experiencing errors, please check your server error log. Tidypics \r
+writes warnings for most upload related problems. You will see something \r
+along these lines: "Tidypics warning: user exceeded post limit on image upload"\r
+\r
+\r
+\r
+GD: Elgg requires GD for image resizing. Tidypics uses GD by default for \r
+resizing. There are two versions GD and GD2. It generally does not matter \r
+which one you are using and it isn't always apparent which one you are\r
+running anyways.\r
+\r
+ImageMagick: A significantly better image library than GD. It uses less \r
+memory during resizing. Use this if it is available.\r
+\r
+Memory Available to PHP: The amount of RAM available to a single PHP \r
+process. This can have an effect on how large an image you can resize\r
+(especially if you are running Tidypics with GD). The best place to\r
+change it is .htaccess.\r
+\r
+Memory Used to Load This Page: This gives you a baseline of how much\r
+memory is being used to load the Elgg framework and plugins. \r
+\r
+Max File Upload Size: The largest file that can be uploaded. You can\r
+adjust this in .htaccess.\r
+\r
+Max Post Size: The largest amount of data that can be submitted. For\r
+Tidypics, this affects how many large images can be uploaded in a \r
+single upload. If this is exceeded, nothing is uploaded and the \r
+user gets an error message. It can be adjusted in .htaccess.\r
+\r
+Max Input Time: This is the amount of time PHP will wait for an \r
+upload to finish. Your users may experience failures if they are\r
+uploading large images on a poor connection or if your server \r
+does not have a lot of bandwidth.\r
+\r
+Max Execution Time: The longest time a PHP script can run on your\r
+server. If a user uploads many large images, the resize code may take\r
+a long time to complete and will be stopped by PHP. If you are seeing\r
+problems with this, you probably have a slow server.\r
+\r
+GD imagejpeg: jpeg resizing with GD\r
+\r
+GD imagegif: gif resizing with GD\r
+\r
+GD imagepng: png resizing with GD
\ No newline at end of file

diff --git a/system.php b/system.php
index 82a7059326a05a804527ada470b6c00b78420f81..ef781b92a5a95657dac95c58ba806aafa1c2af40 100644 (file)
--- a/system.php
+++ b/system.php
@@ -89,7 +89,25 @@
                        <td><?php echo ini_get('max_execution_time'); ?> s</td>
                        <td>Max time a script will run</td>
                </tr>
+               <tr>
+                       <td>GD imagejpeg</td>
+                       <td><?php echo (is_callable('imagejpeg')) ? 'Enabled' : 'Disabled'; ?></td>
+                       <td></td>
+               </tr>
+               <tr>
+                       <td>GD imagepng</td>
+                       <td><?php echo (is_callable('imagepng')) ? 'Enabled' : 'Disabled'; ?></td>
+                       <td></td>
+               </tr>
+               <tr>
+                       <td>GD imagegif</td>
+                       <td><?php echo (is_callable('imagegif')) ? 'Enabled' : 'Disabled'; ?></td>
+                       <td></td>
+               </tr>
        </table>
+       <div style="margin-top:20px;">
+               <a href="<?php echo $CONFIG->url . "mod/tidypics/docs/configure_server.txt"; ?>">Server configuration doc</a>
+       </div>
 </div>
 <?php