[Sommaire] [Imprimer]

   1  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
   2  <html>
   3  <head>
   4    <title>Geeklog Documentation - Installation Instructions</title>
   5    <link rel="stylesheet" type="text/css" href="docstyle.css" title="Dev Stylesheet">
   6  </head>
   7  
   8  <body>
   9  <table cellpadding="2" cellspacing="2" border="0" width="100%">
  10  <tr>
  11    <td valign="top"><img src="images/newlogo.gif" alt="Geeklog Documentation" width="243" height="90" border="0"></td>
  12  </tr>
  13  <tr>
  14    <td valign="top" class="menu"><a href="index.html">Geeklog Documentation</a> - Installation Instructions</td>
  15  </tr>
  16  </table>
  17  
  18  <h1>Installing Geeklog</h1>
  19  
  20  <table width="100%" border="0" cellspacing="0" cellpadding="4">
  21  <tr>
  22      <td valign="top">
  23          <blockquote>
  24              <table width="100%" border="0" cellspacing="2" cellpadding="4">
  25                  <tr>
  26                      <td align="left" valign="top" bgcolor="#aec7e8" width="33%"><b>New Installation</b></td>
  27                      <td align="left" valign="top" bgcolor="#ffe7af" width="33%"><b>Upgrading To New Version</b></td>
  28                      <td align="left" valign="top" bgcolor="#ffa6a6" width="33%"><b>Common Problems</b></td>
  29                  </tr>
  30                  <tr>
  31                      <td align="left" valign="top" bgcolor="#cdeeff" width="33%">
  32                          <ul>
  33                              <li type="disc"><a href="#preinstall">Pre-Installation Checklist</a>
  34                              <li type="disc"><a href="#install">Installation Instructions</a>
  35                          </ul>
  36                      </td>
  37                      <td align="left" valign="top" bgcolor="#f5ffc7" width="33%">
  38                          <ul>
  39                              <li type="disc"><a href="#preupgrade">Pre-Upgrade Checklist</a>
  40                              <li type="disc"><a href="#upgrade">Upgrade Instructions</a>
  41                          </ul>
  42                      </td>
  43                      <td align="left" valign="top" bgcolor="#ffdbd5" width="33%">
  44                          <ul>
  45                              <li type="disc"><a href="#installprob">Installation</a>
  46                              <li type="disc"><a href="#postinstall">Post-Installation</a>
  47                          </ul>
  48                      </td>
  49                  </tr>
  50                  <tr>
  51                      <td colspan="3" align="left" valign="top">Glossary
  52                          <ul>
  53                              <li type="disc">path: A physical location on a server that describes 
  54                    where files and directories are. On Windows paths begin with 
  55                    the drive letter (<code>c:/inetpub/wwwroot/</code>), on 
  56                    *nix paths start at root (<code>/</code>) like (<code>/var/www/</code>)
  57                              <li type="disc">url: Uniform Resource Locator, the address of a specific 
  58                    piece of information on the web (<code>http://www.foo.com/</code>)
  59                          </ul>
  60                      </td>
  61                  </tr>
  62              </table>
  63          </blockquote>
  64      </td>
  65  </tr>
  66  <tr>
  67      <td valign="top"><br>
  68      </td>
  69  </tr>
  70  <tr>
  71      <td valign="top" bgcolor="#aec7e8"><a name="preinstall"><b>PRE-INSTALLATION CHECKLIST (new installation)</b></a></td>
  72  </tr>
  73  <tr>
  74      <td valign="top" bgcolor="#cdeeff">
  75          <p>Before installing Geeklog for the first time, please make sure you have or know the following:</p>
  76          <ol>
  77              <li>A web server running PHP 4.1.0 or higher 
  78              <li>A web server running MySQL 3.23.2 or higher, with access to a database or the ability to create a database 
  79              <li>The ability to create a new database in MySQL or access to an existing one 
  80              <li>A telnet or SSH connection to your web server (although FTP will work). This document will be written assuming you have command line access to your server, but we will note the major differences for FTP users. 
  81              <li>The ability to unpack a tarball (file ending in tar.gz) 
  82              <li>You know the difference between a path and a URL 
  83              <li>You know how to determine your system paths<br>
  84                  <br>
  85              
  86              
  87              <table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
  88                  <tr>
  89                      <td bgcolor="white">
  90                          <div align="left">
  91                              <p><a name="ParseError"><font color="#FF0000">SPECIAL NOTE ABOUT PARSE ERRORS: </font></a></p>
  92                              <p>Some users have reported that WinZip corrupts certain files in the Geeklog tarball during decompression which will cause errors during the installation process. You are strongly urged not to use WinZip. Try WinRAR if you must decompress the file locally, or better yet, unpack the file from your server (requires telnet/SSH access).</p>
  93                              <p>Parse errors can also be caused by using a WYSIWYG editor on lib-common.php, e.g. Dreamweaver - you should use a "plain text editor".</p>
  94                          </div>
  95                      </td>
  96                  </tr>
  97              </table>
  98              <br>
  99          </ol>
 100  
 101  <p>The following instructions will refer to the
 102  <a name="public_html"><tt>public_html</tt></a> directory a lot. Here is what
 103  this is all about:<p>
 104  
 105  <p>Basically, a Geeklog installation consists of two parts: The part that is
 106  visible "to the world" - which is everything in the public_html directory.
 107  "public_html" is a popular name for the world-accessible directory that can be
 108  found on a webserver ("htdocs" and "www" are other popular names). So if you
 109  have such a directory, just copy everything from Geeklog's public_html
 110  directory into that directory on your webserver. Then you only need to set up
 111  $_CONF['path_html'] (in config.php) to point to that directory.</p>
 112  
 113  <p>The other part of Geeklog, which is everything outside the public_html
 114  directory, should not be accessible via a URL since it contains sensitive
 115  information. So you should really put those files and directories outside of
 116  your document root (i.e. outside the web server's public_html, htdocs, or www 
 117  directory). Then you only need to set up $_CONF['path'] (again, in config.php)
 118  to point to the place where you put those files and directories.</p>
 119  
 120  <p>Separating the install in this way will also ensure that you can access your
 121  Geeklog site directly via a domain name (if you have one), e.g.
 122  http://www.yourdomain.com/, and that you don't need to include "public_html"
 123  in the URL.</p>
 124  
 125  <p>If your hosting service does not allow you to install files outside of your document root, please see this FAQ entry on geeklog.net: <a href="http://www.geeklog.net/faqman/index.php?op=view&amp;t=56">Installing Geeklog entirely within the web root</a>.</p>
 126      </td>
 127  </tr>
 128  <tr>
 129      <td valign="top"><br>
 130          <br>
 131          <br>
 132          <br>
 133      </td>
 134  </tr>
 135  <tr>
 136      <td valign="top" bgcolor="#aec7e8"><b><a name="install">INSTALLATION INSTRUCTIONS (new installation)</a></b></td>
 137  </tr>
 138  <tr>
 139      <td valign="top" bgcolor="#cdeeff">
 140          <p>Please read this section <b>COMPLETELY</b> before beginning.</p>
 141          <ol>
 142              <li>Unpack the tarball *within* your web tree by running the following in your shell (this assumes you have ssh access and that you are working with the tarball <i>on the designated server </i>- this can be locally or hosted elsewhere):<br>
 143                  <br>
 144                  <code>tar -zxvf geeklog-1.4.1.tar.gz</code><br>
 145                  <br>
 146                  <b>FTP, Windows Users:</b> unpack the tarball on your <i>local computer</i> and upload the result to your designated server. Everything uploads as ASCII except the images.<br>
 147                  <br>
 148              <li>For *nix installations the following may be required: <br>
 149                  <br>
 150                  <code>chown -R <i>webuser</i>:<i>webuser</i> /path/to/geeklog</code><br>
 151                  <br>This guarantees that everything in that path belongs to you, typical settings are www:www or nobody:nobody and more often than not doesn't matter.<br>
 152                  <br>
 153              <li>For *nix installations cd into /path/to/geeklog and do the following:<br>
 154                  <br>
 155                  <code>chmod -R 775 logs<br>
 156                      chmod -R 775 data<br>
 157                      chmod -R 775 backups<br>
 158                      chmod -R 775 public_html/backend<br>
 159                      chmod -R 775 public_html/images/articles<br>
 160                      chmod -R 775 public_html/images/topics<br>
 161                      chmod -R 775 public_html/images/userphotos</code><br>
 162                  <br>
 163                  <b>FTP Users:</b> If you're doing the chmod via a FTP client, you must also apply the chmod to the files <b>in</b> logs/ and public_html/backend as well as the directories themselves. Most, if not all, ftp clients do not perform this command recursively.  That means you need to set each file within each of these directories manually.<br>
 164                  <br>
 165              
 166              
 167              <table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
 168                  <tr>
 169                      <td bgcolor="white">
 170                          <p><font color="#FF0000">SPECIAL NOTE: </font></p>
 171                          <p><b>Not following step #3 correctly is the #1 reason why people receive errors when they first try to use Geeklog</b>. Take your time and get it right. Also, some users have reported problems if the above permissions are not set to 777. Try 775 first and only be more permissive if you receive an error message.</p>
 172  <p>There is also a script at <b>http://yourgeeklogsite/admin/install/check.php</b> that can test the permissions for you.</p>
 173                      </td>
 174                  </tr>
 175              </table>
 176              <br>
 177              <li>Create the database you want Geeklog to reside in. You only need to create an empty database - the install script (see below) will create the tables for you.<br><br>If you are not familiar with using MySQL, you are urged to get <a href="http://www.phpmyadmin.net/">phpMyAdmin</a> and use it to create a new database. If you have no idea what the previous two sentences mean, contact your sysadmin for help.<br>
 178                  <br>
 179              <li>Edit config.php with the appropriate settings for your server. For installation, this basically means "set your paths," as all other variables can be changed after a successful installation. The config.php file contains comments to help you out.<br><br>
 180  Windows users, you should be able to use the Unix '/' in your paths without any problems. Otherwise, you will need to use the doubled Windows slashes '\\'.<br><br>
 181  <em>Please read the comments in config.php carefully.</em><br>
 182                  <br>
 183              <li>Edit <b>lib-common.php</b> and change the require_once() at the top to point to the location of your <b>config.php</b> file.<br>
 184                  <br>
 185              <li>Open your browser and navigate to <b>http://yourgeeklogsite/admin/install/install.php</b> and follow the directions!<br>
 186                  <br>
 187              <li>Once you see the success message, you are ready to go. <b>You can now 
 188                delete the admin/install directory</b> (and all files within 
 189                it).<br><br>
 190        <li>Read the first story on your Geeklog site to learn how to log in 
 191          as the administrator. Please remember to change the default passwords on all pre-configured accounts right away.<br>
 192                  <br>
 193              
 194              
 195          </ol>
 196  <p>If you run into problems or keep getting error messages, please see the section on <a href="#installprob">common installation problems</a> below.</p>
 197      </td>
 198  </tr>
 199  <tr>
 200      <td valign="top"><br>
 201          <br>
 202          <br>
 203          <br>
 204      </td>
 205  </tr>
 206  <tr>
 207      <td valign="top" bgcolor="#ffe7af"><a name="preupgrade"><b>PRE-UPGRADE CHECKLIST (upgrade)</b></a></td>
 208  </tr>
 209  <tr>
 210      <td valign="top" bgcolor="#f5ffc7">
 211          <div align="center">
 212              <table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
 213                  <tr>
 214                      <td bgcolor="white">
 215                          <div align="left">
 216                              <p><font color="#FF0000">WARNING:</font></p>
 217                              <p>Take extreme care to back up any files from your current Geeklog installation that have any custom code in them, especially lib-custom.php (where all custom code should reside). Be sure to back up any modified themes, images, and static pages from your current installation.</p>
 218                              <p>Also, please be sure to back up your database. We can't stress the importance of backing up your files and database enough. </p>
 219                              <p><b>YOU HAVE BEEN WARNED.</b></p>
 220                          </div>
 221                      </td>
 222                  </tr>
 223              </table>
 224              <br>
 225          </div>
 226      </td>
 227  </tr>
 228  <tr>
 229      <td valign="top"><br>
 230          <br>
 231          <br>
 232          <br>
 233      </td>
 234  </tr>
 235  <tr>
 236      <td valign="top" bgcolor="#ffe7af"><b><a name="upgrade">UPGRADE INSTRUCTIONS (upgrade)</a></b></td>
 237  </tr>
 238  <tr>
 239      <td valign="top" bgcolor="#f5ffc7">
 240          <p>Upgrading is no different than a fresh installation except your database already exists and needs to be upgraded.</p>
 241          <ol>
 242              <li>Back up any files with custom code in them and back up your database. <br>
 243                  <br>
 244              <table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
 245                  <tr>
 246                      <td bgcolor="white">
 247                          <p><font color="#FF0000">SPECIAL NOTE:</font></p>
 248                          <p>Please pay special attention to the older config.php and lib-common.php files, as these files contain database and path information you entered the last time you installed Geeklog and this information MUST be copied over to the NEW config.php and lib-common.php files.<br>
 249                          </p>
 250                      </td>
 251                  </tr>
 252              </table>
 253              <br>
 254              <li>You can choose to either rename or remove your current Geeklog directory.  Although in the end you will be deleting the older install it's probably safer to keep the old copy around for a few days *just* in-case you forgot to transfer some files.<br>
 255                  <br>
 256              <li>Uncompress the new version and copy the result to the same path that your old installation had. For instance, if your old Geeklog was in <code>/usr/home/www/geeklog/</code>, then your new installation should also be in <code>/usr/home/www/geeklog/</code>.<br>
 257                  <br>
 258                          <li>As with a fresh install, edit your <strong>config.php</strong> and <strong>lib-common.php</strong>, basically just copying over the information from your old copies of these files.<br>
 259                  <br>
 260              <li><em>If</em> you are upgrading <strong>from Geeklog 1.2 or earlier</strong>, change to <code>/path/to/geeklog/sql/updates</code> and apply all needed database updates. For example, if you are upgrading from Geeklog 1.1, you will need to apply 1.1_to_1.2.sql and 1.2_to_1.2.2.sql which will upgrade your database to Geeklog 1.2.5-1. I say 1.2.5-1 because there were no database changes from 1.2.2 to 1.2.5-1 (e.g. a 1.2.2 database is the same as a 1.2.5-1 database). If you are uncomfortable using the MySQL command line to do this, you can do it via phpMyAdmin as well.<br><br>
 261              If you are upgrading from Geeklog 1.3 or later, you can skip this step.<br>
 262                  <br>
 263              <li>Open your browser and navigate to <strong>http://yourgeeklogsite/admin/install/install.php</strong>. Enter your path to Geeklog and make sure you select <strong>Upgrade Database</strong> as the installation type, before you click on the "Next" button. The second step of the installation script should have an option to convert your database to the current version.<br>
 264                  <br>
 265  Please note that only "basic" version numbers are listed, because, for example, Geeklog 1.3.7 and 1.3.7sr2 use the same database. So if you're upgrading from Geeklog 1.3.7sr2, just select "1.3.7" (the same applies to 1.3.5 / 1.3.5sr1 / 1.3.5sr2 and all the various 1.3.8 versions).<br>
 266                  <br>
 267              <li>Once you see the success message, your upgrade is complete. <b>You can now delete the admin/install directory</b> (and all files within it).<br><br>
 268          </ol>
 269      </td>
 270  </tr>
 271  <tr>
 272      <td valign="top"><br>
 273          <br>
 274          <br>
 275          <br>
 276      </td>
 277  </tr>
 278  <tr>
 279      <td valign="top" bgcolor="#ffa6a6"><b><a name="installprob">INSTALLATION PROBLEMS (common problems)</a></b></td>
 280  </tr>
 281  <tr>
 282      <td valign="top" bgcolor="#ffdbd5">
 283          <div align="center">
 284              <table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
 285                  <tr>
 286                      <td bgcolor="white">
 287                          <p><font color="#FF0000">SPECIAL NOTE:</font></p>
 288                          <p>Before you go any further, please open config.php <b>AND DOUBLE CHECK YOUR PATHS</b>. Bad paths, or typos in the paths will cause all sorts of errors in Geeklog.</p>
 289                      </td>
 290                  </tr>
 291              </table>
 292          </div>
 293                  <br>
 294                  <br>
 295  <div align="center">
 296  <table width="95%" border="0" cellspacing="0" cellpadding="4"><tr><td>
 297  <p>When you get an error message, please read it carefully. Even if you're not
 298  familiar with PHP, it will give you a hint about what is wrong. Pay special
 299  attention at the paths contained in the error message. Wrong paths are the
 300  most common cause for problems.</p>
 301  <p>If you get more than one error message, always start with the very first
 302  error - the others will often go away automatically once you've fixed the first
 303  one.</p>
 304  </td></tr></table>
 305  </div>
 306                  <a name="parse-error"><br>
 307                  <br></a>
 308  <div align="center">
 309  <table width="95%" border="0" cellspacing="0" cellpadding="4"><tr>
 310  <td bgcolor="#ffedf2">
 311  <p><b>I get the following error:</b></p>
 312  <p><code>Parse error: parse error in /path/to/your/config.php on line 76</code></p>
 313  </td></tr><tr><td>
 314  <p><small>(line number may vary)</small></p>
 315  <p><strong>Answer:</strong></p>
 316  <p>A parse error usually hints at a typo you've made. Check the file at the
 317  given line (the actual error may be in the line preceding the one mentioned
 318  in the error message).</p>
 319  <p>Common problems are:</p>
 320  <ul>
 321  <li>not enclosing paths in single quotes properly</li>
 322  <li>missing semicolon at the end of the line</li>
 323  <li>using single quotes within a string (you need to write <b>Joe's Site</b> as
 324      <b>Joe\'s Site</b>, escaping the extra quote)
 325  </ul>
 326  </td></tr></table>
 327  </div>
 328                  <a name="failed-to-open"><br>
 329                  <br></a>
 330  <div align="center">
 331  <table width="95%" border="0" cellspacing="0" cellpadding="4"><tr>
 332  <td bgcolor="#ffedf2">
 333  <p><b>I get the following errors:</b></p>
 334  <p><code>Warning: main(some/path/to/system/databases/mysql.class.php): failed to open stream: No such file or directory in /path/to/your/system/lib-database.php on line 110</code></p>
 335  <p><code>Fatal error: main(): Failed opening required 'some/path/to/system/databases/mysql.class.php' (include_path='.:/some/other/path/') in /some/path/to/system/lib-database.php on line 110</code></p>
 336  </td></tr><tr><td>
 337  <p><small>(line numbers may vary)</small></p>
 338  <p><strong>Answer:</strong></p>
 339  <p>The path that you've entered for the <b>$_CONF['path']</b> variable in config.php is not correct. Make sure you typed it correctly. Also make sure it uses
 340  an <em>absolute</em> path, i.e. one that starts at the root of your file
 341  system (and that it starts with a / under Unix/Linux or a drive letter under
 342  Windows).</p>
 343  </td></tr></table>
 344  </div>
 345                  <a name="already-exists"><br>
 346                  <br></a>
 347  <div align="center">
 348  <table width="95%" border="0" cellspacing="0" cellpadding="4"><tr>
 349  <td bgcolor="#ffedf2">
 350  <p><b>I get the following error:</b></p>
 351  <p><code>1050: Table 'gl_access' already exists</code></p>
 352  </td></tr><tr><td>
 353  <p><strong>Answer:</strong></p>
 354  <p>You must have run the install script before (possibly unsuccessfully). To
 355  be on the save side, drop the database and create a  new, empty database
 356  before trying to run the install script again.</p>
 357  </td></tr></table>
 358  </div>
 359                  <a name="corrupted"><br>
 360                  <br></a>
 361          <div align="center">
 362              <table width="95%" border="0" cellspacing="0" cellpadding="4">
 363                  <tr>
 364                      <td bgcolor="#ffedf2"><b>During installation, I get one of the following errors:</b>
 365  <p><b>Case 1:</b></p>
 366                          <p><code>Parse error: parse error in ../../lib-common.php on line 2231 </code></p>
 367                          <p><code>Fatal error: Cannot instantiate non-existent class: template in ../../lib-common.php on line 335 </code></p>
 368  
 369  <p><b>Case 2:</b></p>
 370  <p><code>Parse error: parse error in /path/to/geeklog/public_html/lib-common.php on line 3036</code></p>
 371  <p><code>Fatal error: Call to undefined function: plg_showcenterblock() in /path/to/geeklog/public_html/index.php on line 67</code></p>
 372  
 373  <p><b>Case 3:</b></p>
 374  <p><code>Parse error: parse error, unexpected T_CONSTANT_ENCAPSED_STRING in /path/to/geeklog/public_html/lib-common.php on line 3815</code></p>
 375  
 376  <p><code>Fatal error: Cannot instantiate non-existent class: template in /path/to/geeklog/public_html/lib-common.php on line 709</code></p>
 377                      </td>
 378                  </tr>
 379                  <tr>
 380                      <td>
 381                          <p><small>(line numbers may vary)</small></p>
 382                          <p><strong>Answer:</strong></p>
 383  
 384  <p>All of the above cases (and similar "parse error" messages you may get for lib-common.php, typically with a line number in the 3000 or 4000 range) indicate a <b>corrupted lib-common.php</b> file.</p>
 385  <p>As noted <a href="#ParseError">at the top of this document</a> this is usually caused by one of the following:</p>
 386  <ul>
 387  <li>Uncompressing the tarball with certain versions of <b>WinZip</b> (try using WinRar instead)</li>
 388  <li>Editing the lib-common.php with <b>Dreamweaver</b> or other so-called WYSIWYG HTML editors (use a simple text editor instead)</li>
 389  <li>Editing the lib-common.php with "on-site" text editors built into tools like <b>Cpanel</b> (again, use a simple text editor instead)</li>
 390  </ul>
 391  
 392  <p>You will need to unpack a fresh copy of the lib-common.php and edit it again, using a "normal" text editor. Windows users can find some recommendations for editors to use in <a href="http://www.geeklog.net/forum/viewtopic.php?forum=3&amp;showtopic=11866" title="Forum thread: Text editors?">this</a> and <a href="http://www.geeklog.net/forum/viewtopic.php?forum=3&amp;showtopic=15807" title="Forum thread: How to edit lib-common without Notepad on Windows?">this</a> thread in the forums on geeklog.net.</p>
 393  
 394                      </td>
 395                  </tr>
 396              </table>
 397          </div>
 398                  <a name="template-error"><br>
 399                  <br></a>
 400  <div align="center">
 401  <table width="95%" border="0" cellspacing="0" cellpadding="4"><tr>
 402  <td bgcolor="#ffedf2">
 403  <p><b>I get the following error:</b></p>
 404  <p><code>Template Error: set_root: /some/path/to/public_html/layout/professional is not a directory.
 405  Halted.</code></p>
 406  </td></tr><tr><td>
 407  <p><strong>Answer:</strong></p>
 408  <p>This is a path problem again. Check the setting for <b>$_CONF['path_html']</b>. If you did not change or rename Geeklog's <tt>public_html</tt> directory, then there's no need to change that setting at all (restore the line to its
 409  original content). Otherwise, please read the comments above that line in
 410  config.php again carefully to understand how to change that line properly.</p>
 411  </td></tr></table>
 412  </div>
 413                  <a name="access-denied"><br>
 414                  <br></a>
 415  <div align="center">
 416  <table width="95%" border="0" cellspacing="0" cellpadding="4"><tr>
 417  <td bgcolor="#ffedf2">
 418  <p><b>I get the following error:</b></p>
 419  <p><code>Warning: mysql_connect(): Access denied for user: 'username@localhost' (Using password: YES) in<br>
 420  /path/to/geeklog/system/databases/mysql.class.php on line 104<br>
 421  Cannnot connect to DB server</code></p>
 422  </td></tr><tr><td>
 423  <p><small>(line number may vary)</small></p>
 424  <p><strong>Answer:</strong></p>
 425  <p>First of all, make sure the database settings in <tt>config.php</tt> are correct, specifically the name and password of your MySQL user, the name of your database, and the name of your MySQL server.</p>
 426  <p>If you're running your own server, you may need to give your MySQL user
 427  proper permissions. Log in to MySQL as the MySQL root user and issue these
 428  commands:</p>
 429  <code>GRANT ALL PRIVILEGES ON <em>database_name</em> TO <em>user@host</em> IDENTIFIED BY '<em>password</em>';<br>
 430  FLUSH PRIVILEGES;</code>
 431  <p>Replacing the lower-case strings with the actual values, of course.</p>
 432  <p>If you want (or need) to be more restrictive with database permissions:
 433  You will need to at least grant the ALTER, CREATE, DELETE, INSERT, SELECT, and
 434  UPDATE permissions to your database user. ALTER and CREATE permissions are only
 435  needed for installing and upgrading Geeklog, as well as for installing plugins
 436  and other add-ons.</p>
 437  </td></tr></table>
 438  </div>
 439      </td>
 440  </tr>
 441  <tr>
 442      <td valign="top"><br>
 443          <br>
 444          <br>
 445          <br>
 446      </td>
 447  </tr>
 448  <tr>
 449      <td valign="top" bgcolor="#ffa6a6"><b><a name="postinstall">POST-INSTALL PROBLEMS (common problems)</a></b></td>
 450  </tr>
 451  <tr>
 452      <td valign="top" bgcolor="#ffdbd5">
 453          <div align="center">
 454                          <a name="permission-denied"></a>
 455              <table width="95%" border="0" cellspacing="0" cellpadding="4">
 456                  <tr>
 457                      <td bgcolor="#ffedf2">
 458                          <p><b>I've set up my site successfully, but get the following error message on the top:</b></p>
 459  <p><code>
 460  Warning: fopen("/some/path/logs/error.log", "a") - Permission denied in /some/path/public_html/lib-common.php on line 1440
 461  </code></p>
 462                      </td>
 463                  </tr>
 464                  <tr>
 465                      <td>
 466  <p><small>(line number may vary)</small></p>
 467                          <p><strong>Answer:</strong></p>
 468                          <p>Make sure that the logs/ directory AND the files in it have permissions of at least 775. You may need to make the permissions 777 if 775 isn't working for you. For good measure, make sure the public_html/backend directory and the geeklog.rss file have the same 775 or 777 permissions.</p>
 469  
 470  <p><strong>Tip:</strong> Use the script that is located at <b>http://yourgeeklogsite/admin/install/check.php</b> to test if all the permissions have been set up correctly.</p>
 471                      </td>
 472                  </tr>
 473              </table>
 474              <a name="headers-already-sent"><br>
 475              <br></a>
 476              <table width="95%" border="0" cellspacing="0" cellpadding="4">
 477                  <tr>
 478                      <td bgcolor="#ffedf2">
 479                          <p><b>Whenever someone tries to log in or out, the following error is produced:</b></p>
 480                          <p><code>Cannot add header information - headers already sent by (output started at /usr###/home/&lt;userid&gt;/public_html/geeklog/config.php:589) in /usr###/home/&lt;userid&gt;/public_html/geeklog/system/lib-sessions.php on line 133</code></p>
 481                      </td>
 482                  </tr>
 483                  <tr>
 484                      <td>
 485  <p><small>(line numbers may vary)</small></p>
 486                          <p><strong>Answer:</strong></p>
 487                          <p>Make sure that your config.php file does not contain any "whitespace" after the closing <b>?&gt;</b> at the end of the file. I.e. there should not be anything (not even blanks or empty lines) after those two characters.</p>
 488                      </td>
 489                  </tr>
 490              </table>
 491              <br>
 492              <br>
 493              <hr noshade width="95%">
 494              <table width="95%" border="0" cellspacing="0" cellpadding="4">
 495                  <tr>
 496                      <td>
 497                          <div align="left">
 498                              <p>If you still have problems, please do one or more of the following:</p>
 499                              <p>1) Go to <a href="http://www.geeklog.net">http://www.geeklog.net</a> and check out the Support section. The Support section includes a <a href="http://www.geeklog.net/faqman/">FAQ</a> and a <a href="http://www.geeklog.net/search.php">search system</a> (try searching for the error message, if you get one).</p>
 500                              <p>2) Visit the mailing list archives at <a href="http://lists.geeklog.net/pipermail/geeklog-users/">http://lists.geeklog.net/pipermail/geeklog-users/</a>. You can also <a href="http://lists.geeklog.net/listinfo/geeklog-users">subscribe to the mailing list</a> and post your question to the Geeklog community.</p>
 501                              <p>3) Try the chat room at <b>irc.freenode.net, channel #geeklog</b>. Please have all your path information in config.php and lib-common.php readily available.</p>
 502                              <p>4) Try entering the text of the error message on Google. Chances are you will find someone else who had the same problem and fixed it.  And sometimes searching for a specific error will cause Google to bring up broken pages that have the same error.</p>
 503                          </div>
 504                      </td>
 505                  </tr>
 506              </table>
 507              <br>
 508              <br>
 509              Extended version of this document created by Jason C. Levine, <br>
 510              layout by Simon Lord, reviewed by Dirk Haun and Jeffrey Schoolcraft.</div>
 511      </td>
 512  </tr>
 513  </table>
 514   
 515  <br><br>
 516  
 517  <table border="0" width="100%" class="footer">
 518  <tr valign="top">
 519    <td colspan="2"><a href="http://wiki.geeklog.net/">The Geeklog Documentation Project</a><br>
 520      All trademarks and copyrights on this page are owned by their respective owners. GeekLog is copyleft.</td>
 521  </tr>
 522  </table>
 523   
 524  </body>
 525  </html>