GeeklogWiki - User contributions [en]

Talk:Geeklog 1.3x Documentation

2004-07-09T06:21:55Z

Netbuster: Still unclear how to post

[[User:Netbuster]]
I was excited to learn about this Wiki project and decided to add some personal experiences, as i just refreshed my memory by recent upgrade to 1.3.9
But, I started typing all little things I noticed and realized, doc page becomes clogged too much.

I added one note here for obvious thing which happens with me always and under all hostings, and then thought one more note about checking permissions, under installation steps, there is an advise for check.php script. It is currently running not correctly, so first my move was to write it, like this
NOTE: As of 1.3.9sr1 version, running check.php will help you to identify whether permissions are set correctly only till you get an error regarding SQL. Once SQL related error occurs, download error.log and read the error. It will mean that permissions for logs/ folder are set and geeklog writes to it. But errors regarding SQL are not for you to worry at that point, omit it for now and go to the step 4

But then I removed it from there, since I started thinking that at the same spot I have to describe how to correct errors, which error is good and which is not, what to do etc. It may become a 2 page story just describing a current work of one script, while it may all change in the next version
So, having said all of this, my questions are:

# Should we have a version related errors file or how wiki doc will change if 1.3.10 will be released and function differently
# If someone spots a bug or an error, is Documentation is a write space for describing it and if yes, what spot? Should it be under Problems? May be version differencies? I remember from previous installations, there are numerious little but important changes from version to version and automatic updates not always catch them
# Not related, but ... What about security? I registered my account and even without proving an email I was logged on immediately to edit stuff. What if someone will delete or add advertisement entries all over the place?

[[User:Tomw|TomW]] Here are my suggestions for these questions:
# It is very easy to make a new page just refer to it. I would suggest that version specific notes be included on their own page like this <nowiki>[[ModulePageSubjectEtc 1.3.8 note]]</nowiki>
# It doesn't matter on things like this, perhaps we could add a page to each update page for gotcha's like this. Be the first and start the trend.
#Security is not a big issue. I will keep an eye on it, as sysop I have the ability to ban users and ips and I will. The wiki keeps a history and I make a daily backup also, so I can get back to previous versions.

== Still unclear how to post ==

Hi ALL

I went ahead and posted a gotcha for check.php

http://wiki.geeklog.net/wiki/index.php/Talk:Installation_Instructions

I thought, I did it right way, I went first to the page I wanted to add my gotcha, which is this one:

http://www.pigstye.net/wiki/index.php/Installation_Instructions

And pressed "Discuss this page"

where I typed all my text and submitted

But when I went back to the main page, nowhere it states that there is note linked to that page and of course no name mentioned, so it will be a real coinsidence if someone will click to "Discuss..." link to see my note and have a problem discussed there, so my note will be helpful

I see some options used (like linked pages) but how I can link those notes?

or, may be I can make a fresh page and position it under the page it discusses? The How?

Please advise!

Talk:Installation Instructions

2004-07-09T06:13:53Z

Netbuster:

CHECK.PHP GOTCHA (upto ver. 1.3.9-1)

Using check.php before the first installation will lead to errors, because once the script is done checking permissions, it will start checking SQL and next error will stating that gl_sessions table is missing.

Here is how to deal with it.

Run for the first time (or several times) while getting permission errors. Make changes (for example, chmod from 775 to 777) until the kind of error you get from check.php will change.

That will indicate that permissions on error.log are done correctly and now script moved to SQL check-up (about what you can now learn, by reading your error.log)

for you being at stage of pre-installation that will be enough. Stop running this script and proceed to the next step, step 4

NOTE: check.php only checks first folder (logs) for permissions before SQL error, so images/ and inside articles/ and userphotos/ were not checked. You can easily guess, that the kind of permissions worked on log folder will work on those, so just do the same chmod on them

Talk:Installation Instructions

2004-07-09T06:06:21Z

Netbuster: How to get through errors and what to look for

CHECK.PHP GOTCHA (upto ver. 1.3.9-1)

Installation Instructions

2004-07-06T06:26:04Z

Netbuster:

<table>
<tr>
<td valign="top" bgcolor="#aec7e8">INSTALLATION INSTRUCTIONS (new installation)</td>
</tr>
<tr>
<td valign="top" bgcolor="#cdeeff">
Please read this section COMPLETELY before beginning.
<ol>
<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 on the designated server - this can be locally or hosted elsewhere): 
 
<code>tar -zxvf geeklog-1.3.9sr1.tar.gz</code> 
 
FTP, Windows Users: unpack the tarball on your local computer and upload the result to your designated server. Everything uploads as ASCII except the images. 
 
<li>For *nix installations the following may be required: 
 
<code>chown -R webuser:webuser /path/to/geeklog</code> 
 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. 
 
<li>For *nix installations cd into /path/to/geeklog and do the following: 
 
<code>chmod -R 775 logs/ 
chmod -R 775 public_html/backend/ 
chmod -R 775 public_html/images/articles 
chmod -R 775 public_html/images/userphotos</code> 
 
FTP Users: If you're doing the chmod via a FTP client, you must also apply the chmod to the files in 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. 
NOTE: Some hostings do not allow you to write logs to logs folder outside of the webfolder (aka public_html) or they may already have there their own folder logs/ with strict permissions, for those or similar reasons you have to change the path to logs. For example, put it under public_html, within your web root. If so, change $_CONF path_log for your new path, make or move logs folder with both files there and make sure permissions are set at new place. 
 

<table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
<tr>
<td bgcolor="white">
SPECIAL NOTE: 
Not following step #3 correctly is the #1 reason why people receive errors when they first try to use Geeklog. 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.
There is also a script at http://yourgeeklogsite/admin/install/check.php that can test the permissions for you.
</td>
</tr>
</table>
 
<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. 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. 
 
<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. 
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 '\\'. 
Please read the comments in config.php carefully. 
 
<li>Edit lib-common.php and change the require_once() at the top to point to the location of your config.php file. 
 
<li>Open your browser and navigate to http://yourgeeklogsite/admin/install/install.php and follow the directions! 
 
<li>Once you see the success message, you are ready to go. You can now
delete the admin/install directory (and all files within
it). 
<li>Read the first story on your Geeklog site to learn how to log in
as the administrator. Please remember to change the default passwords on all pre-configured accounts right away. 
 

</ol>
</td>
</tr>
</table>