GeeklogWiki - User contributions [en]

Installation Instructions

2004-07-16T08:52:32Z

Robert: Re-formatted

{|
|- valign=top bgcolor=#aec7e8
|'''INSTALLATION INSTRUCTIONS (new installation)'''
|- 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 <nowiki>www:www</nowiki> or <nowiki>nobody:nobody</nowiki> 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 bgcolor=white>
<td>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 [http://www.phpmyadmin.net phpMyAdmin] 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.
|}

Talk:Geeklog 1.3x Documentation

2004-07-09T10:38:23Z

Robert: =New Layout Of 1.3x Index Page=

[[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!

== Adding pages so they're visible ==
[[User:Robert|Robert]]
Netbuster, if you want to add a subpage to any page in the wiki you do the following:
#Go to this page e.g. [[Installation_Instructions|Installation Instructions]]
#You read it and want to add some thoughts of yours and call it '''CHECK.PHP GOTCHA'''. OK
#So you clik on Edit this page.
#In the editor you go to the bottom of the text and enter e.g. this <nowiki>[[CHECK.PHP GOTCHA]]</nowiki>
#You save the page
#After saving there will be a new link at the bottom of Installation Instructions page, called '''CHECK.PHP GOTCHA''' leading to a new page you gotta fill with the content
#When you click on the link you will see an editor field waiting for you insights on any subject

Hope that helps.

PS
I've started with wiki thing a year ago and I quit because couldn't understand how it works. Now after Tom has set this up I started slowly to read the wiki docs and found it very simple to use. Really after adding two or more pages you'll get there.

== New Layout Of 1.3x Index Page ==

[[User:Robert|Robert]]
I was just wondering whether we could collapse the index page a little bit, and hide all subthings under the appropriate main sections. Something like I did for Introduction.

That would make the navigation easier I guess. Any comments?

Also I would like the list of plugins ordered alphabetically.

Talk:Geeklog 1.3x Documentation

2004-07-09T10:37:48Z

Robert:

[[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!

== Adding pages so they're visible ==
[[User:Robert|Robert]]
Netbuster, if you want to add a subpage to any page in the wiki you do the following:
#Go to this page e.g. [[Installation_Instructions|Installation Instructions]]
#You read it and want to add some thoughts of yours and call it '''CHECK.PHP GOTCHA'''. OK
#So you clik on Edit this page.
#In the editor you go to the bottom of the text and enter e.g. this <nowiki>[[CHECK.PHP GOTCHA]]</nowiki>
#You save the page
#After saving there will be a new link at the bottom of Installation Instructions page, called '''CHECK.PHP GOTCHA''' leading to a new page you gotta fill with the content
#When you click on the link you will see an editor field waiting for you insights on any subject

Hope that helps.

PS
I've started with wiki thing a year ago and I quit because couldn't understand how it works. Now after Tom has set this up I started slowly to read the wiki docs and found it very simple to use. Really after adding two or more pages you'll get there.

== New Layout Of 1.3x Index Page ==

[[User:Robert]]
I was just wondering whether we could collapse the index page a little bit, and hide all subthings under the appropriate main sections. Something like I did for Introduction.

That would make the navigation easier I guess. Any comments?

Also I would like the list of plugins ordered alphabetically.

Talk:Geeklog 1.3x Documentation

2004-07-09T10:36:33Z

Robert: ==New Layout Of 1.3x Index Page

[[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!

== Adding pages so they're visible ==
[[User:Robert|Robert]]
Netbuster, if you want to add a subpage to any page in the wiki you do the following:
#Go to this page e.g. [[Installation_Instructions|Installation Instructions]]
#You read it and want to add some thoughts of yours and call it '''CHECK.PHP GOTCHA'''. OK
#So you clik on Edit this page.
#In the editor you go to the bottom of the text and enter e.g. this <nowiki>[[CHECK.PHP GOTCHA]]</nowiki>
#You save the page
#After saving there will be a new link at the bottom of Installation Instructions page, called '''CHECK.PHP GOTCHA''' leading to a new page you gotta fill with the content
#When you click on the link you will see an editor field waiting for you insights on any subject

Hope that helps.

PS
I've started with wiki thing a year ago and I quit because couldn't understand how it works. Now after Tom has set this up I started slowly to read the wiki docs and found it very simple to use. Really after adding two or more pages you'll get there.

== ==New Layout Of 1.3x Index Page ==

[[User:Robert]]
I was just wondering whether we could collapse the index page a little bit, and hide all subthings under the appropriate main sections. Something like I did for Introduction.

That would make the navigation easier I guess. Any comments?

Also I would like the list of plugins ordered alphabetically.

Talk:Geeklog 1.3x Documentation

2004-07-09T09:44:30Z

Robert: =Adding pages so they're visible=

Talk:Geeklog 1.3x Documentation

2004-07-09T09:36:59Z

Robert: Adding pages so they're visible

[[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!

== Adding pages so they're visible ==

Netbuster, if you want to add a subpage to any page in the wiki you do the following:
#Go to this page e.g. [[Installation_Instructions|Installation Instructions]]
#You read it and want to add some thoughts of yours and call it '''CHECK.PHP GOTCHA'''. OK
#So you clik on Edit this page.
#In the editor you go to the bottom of the text and enter e.g. this <nowiki>[[CHECK.PHP GOTCHA]]</nowiki>
#You save the page
#After saving there will be a new link at the bottom of Installation Instructions page, called '''CHECK.PHP GOTCHA''' leading to a new page you gotta fill with the content
#When you click on the link you will see an editor field waiting for you insights on any subject

Hope that helps.

PS
I've started with wiki thing a year ago and I quit because couldn't understand how it works. Now after Tom has set this up I started slowly to read the wiki docs and found it very simple to use. Really after adding two or more pages you'll get there.

Faqman New Installation

2004-07-08T14:43:21Z

Robert:

'''Note:''' You need to manually create the plugin program directories and copy the program files into their appropriate directories.

Step 0. '''Database backup'''

Make a backup of your current geeklog database using the built-in admin feature. Verify your backup feature is configured correctly and backup file is not 0 bytes (This is worth a check)

Step 1. '''Copy plugin files into their required directories'''

Uncompress the archive files into your <geeklog_dir>/plugins directory. It will create a ''faqman'' directory and associated subdirectories for the files. You will need to move the files in the admin and public subdirectories to their appropriate directory as indicated below.

1.1 public_html/ - Main program files

The files in the public directory under your new plugins/faqman folder need to be copied to <geeklog_dir>/public_html/faqman directory

You will need to first create the:

<geeklog_dir>/public_html/faqman directory

1.2 admin/ - Plugin Install and Main admin program files

The files in the admin directory under your new plugins/faqman folder need to be copied to <geeklog_dir>/public_html/admin/plugins/faqman directory.

You will need to first create the:

<geeklog_dir>/public_html/admin/plugins/faqman directory

1.3 '''Directory and File Permissions'''

Directory and File owner should be same as webserver

All the files and directories should have Read permissions and directories need execute. Setting all plugin files and directories to have read + execute should not be a security issue but PHP files only need read access to execute. The directories need execute rights in order for them to be searched or accessed

Step 2. '''Run the install program'''

2.1 '''Logged in as admin'''

As of Geeklog 1.3.7 - Plugins can now be installed directly from the Plugins Editor.

Geeklog will list all installed plugins and show those that are not installed with a link.

All plugin files must be in place first

OR: In your browser, go to http://your_geeklog_url/admin/plugins/faqman/install.php

Note: The installer is designed to back out any database changes if there should be an error. You can monitor the installer by viewing the error.log, file <geeklog_dir>/logs/error.log

2.2 '''Verify successful operation'''

*Did you get a successful completion message that your database tables have been created
*There should now be a faqman link in your top header.
*As admin, you should see the "faqman" menu item in the "Admin Block"

2.3 Check the install logging in the <geeklog_dir>/logs/error.log file

FAQ Manager Plugin

2004-07-08T14:35:57Z

Robert:

{| border=1 cellspacing=0 width=100%
|Author
|Blaine Lang - Based on the FAQ Application by Stephen Ball
|-
|Latest Version
|0.8 Beta 1
|-
|Geeklog Version
|1.3.7
|-
|Release Date
|Mar 9, 2003
|-
|Description
|The FAQ Manager allows you to create categories and topics for Frequently Asked Questions (FAQ's).
|-
|Features
|The FAQ editor:
*allows you to enter full HTML
*it supports embedded PHP
*it ncludes the integrated install, de-install, administration, security, search all wrapped inside the Geeklog portal
|}

Stephen Ball has granted me (Blaine Lang) permission to distribute his application and remove his copy write notices and restrictions that the original application is distributed with. This now provides a nicely integrated plugin.

In completing the integration, I added the logic to support magic_quotes being ON or OFF in the hosted PHP environment. The original 2.0 release of the application required magic_quotes to be on.

The FAQ Manager uses it's own and different template method then Geeklog. I have not looked at changing this or allowing the plugin to support different templates per theme. I have done considerable customization of the templates to provide a tighter integration with Geeklog

This is a BETA Release so please report any problems or feedback on my site's forum. [[http://www.portalparts.com/forum/index.php?forum=9 Forum]]

[[License]]
;[[New Installation]]

Faqman New Installation

2004-07-08T09:13:47Z

Robert:

Note: You need to manually create the plugin program directories and copy the program files into their appropriate directories.

Step 0. Database backup

Make a backup of your current geeklog database using the built-in admin feature. Verify your backup feature is configured correctly and backup file is not 0 bytes (This is worth a check)

Step 1. Copy plugin files into their required directories

Uncompress the archive files into your <geeklog_dir>/plugins directory. It will create a faqman directory and associated subdirectories for the files. You will need to move the files in the admin and public subdirectories to their appropriate directory as indicated below.

1.1 public_html/ - Main program files

The files in the public directory under your new plugins/faqman folder need to be copied to <geeklog_dir>/public_html/faqman directory

You will need to first create the:

<geeklog_dir>/public_html/faqman directory

1.2 admin/ - Plugin Install and Main admin program files

The files in the admin directory under your new plugins/faqman folder need to be copied to <geeklog_dir>/public_html/admin/plugins/faqman directory.

You will need to first create the:

<geeklog_dir>/public_html/admin/plugins/faqman directory

1.3 Directory and File Permissions

Directory and File owner should be same as webserver

All the files and directories should have Read permissions and directories need execute. Setting all plugin files and directories to have read + execute should not be a security issue but PHP files only need read access to execute. The directories need execute rights in order for them to be searched or accessed

{Return to index}

Step 2. Run the install program

2.1 Logged in as admin

As of Geeklog 1.3.7 - Plugins can now be installed directly from the Plugins Editor.

Geeklog will list all installed plugins and show those that are not installed with a link.

All plugin files must be in place first

OR: In your browser, go to http://your_geeklog_url/admin/plugins/faqman/install.php

Note: The installer is designed to back out any database changes if there should be an error. You can monitor the installer by viewing the error.log, file <geeklog_dir>/logs/error.log

2.2 Verify successful operation

o Did you get a successful completion message that your database tables have been created

o There should now be a faqman link in your top header.

o As admin, you should see the "faqman" menu item in the "Admin Block"

2.3 Check the install logging in the <geeklog_dir>/logs/error.log file

FAQ Manager Plugin

2004-07-08T09:13:00Z

Robert:

{| border=1 cellspacing=0 width=100%
|Author
|Blaine Lang - Based on the FAQ Application by Stephen Ball
|-
|Latest Version
|0.8 Beta 1
|-
|Geeklog Version
|1.3.7
|-
|Release Date
|Mar 9, 2003
|-
|Description
|The FAQ Manager allows you to create categories and topics for Frequently Asked Questions (FAQ's).
|-
|Features
|The FAQ editor:
*allows you to enter full HTML
*it supports embedded PHP
*it ncludes the integrated install, de-install, administration, security, search all wrapped inside the Geeklog portal
|}

Stephen Ball has granted me (Blaine Lang) permission to distribute his application and remove his copy write notices and restrictions that the original application is distributed with. This now provides a nicely integrated plugin.

In completing the integration, I added the logic to support magic_quotes being ON or OFF in the hosted PHP environment. The original 2.0 release of the application required magic_quotes to be on.

The FAQ Manager uses it's own and different template method then Geeklog. I have not looked at changing this or allowing the plugin to support different templates per theme. I have done considerable customization of the templates to provide a tighter integration with Geeklog

This is a BETA Release so please report any problems or feedback on my site's forum. {http://www.langfamily.ca/forum/index.php?forum=9}

[[License]]
;[[New Installation]]

FAQ Manager Plugin

2004-07-08T09:12:21Z

Robert:

{| border=1 cellspacing=0 width=100%
|Author
|Blaine Lang - Based on the FAQ Application by Stephen Ball
|-
|Latest Version
|0.8 Beta 1
|-
|Geeklog Version
|1.3.7
|-
|Release Date
|Mar 9, 2003
|-
|Description
|The FAQ Manager allows you to create categories and topics for Frequently Asked Questions (FAQ's).
|-
|Features
|The FAQ editor:
*allows you to enter full HTML
*it supports embedded PHP
*it ncludes the integrated install, de-install, administration, security, search all wrapped inside the Geeklog portal
|}

Stephen Ball has granted me permission to distribute his application and remove his copy write notices and restrictions that the original application is distributed with. This now provides a nicely integrated plugin.

In completing the integration, I added the logic to support magic_quotes being ON or OFF in the hosted PHP environment. The original 2.0 release of the application required magic_quotes to be on.

The FAQ Manager uses it's own and different template method then Geeklog. I have not looked at changing this or allowing the plugin to support different templates per theme. I have done considerable customization of the templates to provide a tighter integration with Geeklog

This is a BETA Release so please report any problems or feedback on my site's forum. {http://www.langfamily.ca/forum/index.php?forum=9}

[[License]]
;[[New Installation]]

FAQ Manager Plugin

2004-07-08T08:38:03Z

Robert:

{| border=1 cellspacing=0 width=100%
|Author
|Blaine Lang - Based on the FAQ Application by Stephen Ball
|-
|Latest Version
|0.8 Beta 1
|-
|Geeklog Version
|1.3.7
|-
|Release Date
|Mar 9, 2003
|-
|Description
|The FAQ Manager allows you to create categories and topics for Frequently Asked Questions (FAQ's).
|-
|Features
|*The FAQ editor allows you to enter full HTML
*supports embedded PHP
|}

The FAQ editor allows you to enter full HTML and supports imbedded PHP. The Plugin includes the integrated install, de-install, administration, security, search all wrapped inside the Geeklog portal.

Stephen Ball has granted me permission to distribute his application and remove his copy write notices and restrictions that the original application is distributed with. This now provides a nicely integrated plugin.

In completing the integration, I added the logic to support magic_quotes being ON or OFF in the hosted PHP environment. The original 2.0 release of the application required magic_quotes to be on.

The FAQ Manager uses it's own and different template method then Geeklog. I have not looked at changing this or allowing the plugin to support different templates per theme. I have done considerable customization of the templates to provide a tighter integration with Geeklog

This is a BETA Release so please report any problems or feedback on my site's forum. {http://www.langfamily.ca/forum/index.php?forum=9}

[[License]]
;[[New Installation]]

Faqman License

2004-07-08T08:07:13Z

Robert:

This Geeklog Plug-in, like Geeklog is released under the GNU General Public License. It is a bona fide Open Source / Free Software project.

Like all good open source projects, Geeklog and this Plug-in both depend on the community. Thanks for your continued support, and let us know what we can do to make Geeklog and the Plug-in even better.

Stephen Ball has granted me permission to distribute his application and remove his copy write notices and restrictions that the original application is distributed with. This now provides a nicely integrated plugin.

[[FAQ_Manager_Plugin|Back]]

Faqman License

2004-07-08T08:06:03Z

Robert:

Faqman License

2004-07-08T08:05:13Z

Robert:

This Geeklog Plug-in, like Geeklog is released under the GNU General Public License. It is a bona fide Open Source / Free Software project.
;Like all good open source projects, Geeklog and this Plug-in both depend on the community. Thanks for your continued support, and let us know what we can do to make Geeklog and the Plug-in even better.
;Stephen Ball has granted me permission to distribute his application and remove his copy write notices and restrictions that the original application is distributed with. This now provides a nicely integrated plugin.

FAQ Manager Plugin

2004-07-08T08:04:01Z

Robert:

Author: Blaine Lang - Based on the FAQ Application by Stephen Ball
;Latest Version: 0.8 Beta 1
;Geeklog Version: 1.3.7
;Release Date: Mar 9, 2003

;Description:

;The FAQ Manager is a Geeklog Plugin that allows you to create categories and topics for Frequently Asked Questions (FAQ's). The FAQ editor allows you to enter full HTML and supports imbedded PHP. The Plugin includes the integrated install, de-install, administration, security, search all wrapped inside the Geeklog portal.

;Stephen Ball has granted me permission to distribute his application and remove his copy write notices and restrictions that the original application is distributed with. This now provides a nicely integrated plugin.

;In completing the integration, I added the logic to support magic_quotes being ON or OFF in the hosted PHP environment. The original 2.0 release of the application required magic_quotes to be on.

;The FAQ Manager uses it's own and different template method then Geeklog. I have not looked at changing this or allowing the plugin to support different templates per theme. I have done considerable customization of the templates to provide a tighter integration with Geeklog

;This is a BETA Release so please report any problems or feedback on my site's forum. {http://www.langfamily.ca/forum/index.php?forum=9}

[[License]]
[[New Installation]]

Comment Settings

2004-07-07T09:04:53Z

Robert:

{| border=1 cellspacing=0 width=100%
!Variable
!Default Value
!Description
|-
|commentspeedlimit
|45
|Number of seconds between posting a comment for the user
|-
|comment_limit
|100
|Most number of comments to show at any one time
|-
|comment_mode
|threaded
|How to display comments (threaded, nested, flat or nocomments)
|-
|comment_code
|0
|Default value for new stories: Comments enabled (0) or disabled (-1)
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

URL Rewriting

2004-07-07T09:03:39Z

Robert:

Geeklog includes a simple but useful URL rewriting feature which can help make your site more crawler friendly (i.e. the URLs of your site are more likely to be picked up by the search engine's indexing bots). Currently, this feature is only supported for URLs to stories and by the Static Pages plugin.
;URL rewriting means that your URLs will look like this
;<center>http<nowiki>:</nowiki>//www.geeklog.net/article.php/20021022234959146</center>
;instead of like this
;<center>http<nowiki>:</nowiki>//www.geeklog.net/article.php?story=20021022234959146</center>
;While some search engines will pick up the second form, Google seems to prefer the first format and completely ignores the second format.
;Note: This feature may not work with all web servers. It is known to work with Apache (all versions) and known not to work with IIS (at least some versions). Please try it out before you go public with your site.

{| border=1 cellspacing=0 width=100%
!Variable
!Default Value
!Description
|-
|url_rewrite
|false
|Enable (true) or disable (false) URL rewriting.
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

URL Rewriting

2004-07-07T09:02:45Z

Robert:

Geeklog includes a simple but useful URL rewriting feature which can help make your site more crawler friendly (i.e. the URLs of your site are more likely to be picked up by the search engine's indexing bots). Currently, this feature is only supported for URLs to stories and by the Static Pages plugin.
;URL rewriting means that your URLs will look like this
;<center>http<nowiki>:</nowiki>//www.geeklog.net/article.php/20021022234959146</center>
;instead of like this
;<center>http<nowiki>:</nowiki>//www.geeklog.net/article.php?story=20021022234959146</center>
;While some search engines will pick up the second form, Google seems to prefer the first format and completely ignores the second format.
;Note: This feature may not work with all web servers. It is known to work with Apache (all versions) and known not to work with IIS (at least some versions). Please try it out before you go public with your site.

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|url_rewrite
|false
|Enable (true) or disable (false) URL rewriting.
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Content Control Settings

2004-07-07T08:49:19Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|user_html
|, , , <a>, , , <tt>, <hr>, <ol>, <ul>, <li>, <code>, <pre>
|HTML tags and attributes that normal users are allowed to use in story submissions and comments.
|-
|admin_html
|additional HTML tags, e.g. for tables
|HTML tags and attributes that admin users are allowed to use (in addition to those from user_html). Redefining a tag with additional attributes will overwrite the definition from user_html.
|-
|allowed_protocols
|array ('http:', 'https:', 'ftp:');
|Defines which protocols are allowed in links (i.e. HTML <code><a></code> tags). Note: The kses class used to filter these protocols has a hard-coded list of allowed protocols to which the above will be added. It is currently not possible to remove any of the default protocols (which include, for example, 'mailto:', 'gopher:', and 'news:').
|-
|censormode
|1
|Censor submissions and comments (0=no, 1=yes)
|-
|censorreplace
|*censored*
|Text to replace a censored word with
|-
|censorlist
|array("fuck", "cunt", "fucker", "fucking", "pussy", "cock", "c0ck", "cum", "twat", "clit", "bitch", "fuk", "fuking", "motherfucker")
|An array of censored words
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

RSS/RDF Feed Settings

2004-07-07T08:46:12Z

Robert:

Geeklog can export its headlines to a so-called RSS feed (also known as an RDF feed). This will let you share your news with other sites (Hint: Create a Portal block from Geeklog's Block menu to import RSS/RDF news feeds from other sites).
;Starting with Geeklog 1.3.9, RSS feeds can be created and configured from Geeklog's Admin menu ("Content Syndication"). The following settings will only be used as the default settings for any new feeds that you create from the admin panel.

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|backend
|1
|Create an RSS/RDF file for the stories in rdf_file (0=no, 1=yes)
|-
|rdf_file
|HTML path with "/backend/geeklog.rdf" suffix
|File system path for the RDF file. This file allows you to share your site's headlines with others
|-
|rdf_language
|en-gb
|Value for the feed's language tag. Depending on your site's language and operating system, this may differ from the language setting in the locale (see above). Example: The PHP locale setting for German is 'de_DE' while the correct language setting for a German RSS feed would be 'de-DE' (note the dash instead of the underscore).
|-
|rdf_limit
|10
|Limit the number of stories in the RSS feed. If the value for this setting is a number, the feed will hold this many stories. If the number is followed by a lower-case 'h' (e.g. 24h) it denotes the number of hours from which to chose the stories.
|-
|rdf_storytext
|0
|If this value is 1, then the entire introtext of the stories will be included in the RSS feed. Any number greater than one limits the introtext to that many characters (e.g. a value of 80 would only include the first 80 characters from the introtext in the feed). If set to 0, the introtext is not included in the feed.
|}

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Links Settings

2004-07-07T08:37:19Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|linkcols
|3
|Number of columns to use when listing the categories in the links section. Set to 0 if you don't want categories listed.
|-
|linksperpage
|10
|Number of links to show per page. Set to 0 to show all links at once.
|}
;Note: When setting both 'linkcols' and 'linksperpage' to 0 you get back the old-style (pre-1.3.6) layout of the links section.

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Topic, What's New & E-mail Settings

2004-07-07T08:35:09Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|sortmethod
|sortnum
|alpha = Sort topics in topic list alphabetically sortnum = Sort topics in topic list by sort number
|-
|showstorycount
|1
|Show the number of stories in a topic in the Sections block (0=no, 1=yes)
|-
| showsubmissioncount showsubmissioncount
|1
|Show the number of story submissions for a topic in the Sections block (0=no, 1=yes)
|-
|hide_home_link
|0
|Hide the "Home" link from the Sections block (0=no, 1=yes)
|-
|showemptysearchresults
|0
|Show empty result blocks even when search returned no hits for stories, events, links, etc. (0=no, 1=yes)
|-
|whosonline_threshold
|300
|How long, in seconds, users can be idle before removing them from the whosonline block
|-
|emailstories
|0
|Let users get stories e-mailed to them (0=no, 1=yes), aka Daily Digest. Please note that this requires cron and the use of PHP as a shell script.
|-
|emailstorieslength
|1
|When emailstories (above) is enabled, send only the title and the link to the new stories (0), or send the entire introtext (1) or send the first n characters from the introtext (where n = any other number)
|-
|emailstoriesperdefault
|0
|When set to 1, new users will be subscribed to the daily digest automatically when they register with the site.
|-
|newstoriesinterval
|86400
|Stories are "new" if they are this many seconds old.
|-
|newcommentsinterval
|172800
|Comments are "new" if they are this many seconds old.
|-
|newlinksinterval
|1209600
|Links are "new" if they are this many seconds old.
|-
|hidenewstories
|0
|Set to 1 to hide new stories from What's New block.
|-
|hidenewcomments
|0
|Set to 1 to hide new comments from What's New block.
|-
|hidenewlinks
|0
|Set to 1 to hide new links from What's New block.
|-
|hidenewplugins
|0
|Set to 1 to hide new entries by plugins from the What's New block.
|-
|copyrightyear
|(commented out)
|Set this to the year you want to appear in the copyright notice of your site's footer. If not set, Geeklog will use the current year.
|-
|allow_username_change
|0
|If set to 1, users will be allowed to change their username (login name). Stories and comments posted under the old username will automatically show the new username.
|-
|allow_account_delete
|0
|If set to 1, users will be allowed to delete their accounts. Stories and comments posted under that account will be kept and show up as being posted by "Anonymous".
|-
|passwordspeedlimit
|300
|Minimum delay between two requests for a new password, in seconds.
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Submission Settings

2004-07-07T08:25:47Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|storysubmission
|1
|Enable (1) or disable (0) the story submission queue
|-
|linksubmission
|1
|Enable (1) or disable (0) the link submission queue
|-
|eventsubmission
|1
|Enable (1) or disable (0) the event submission queue
|-
|usersubmission
|1
|Enable (1) or disable (0) the user submission queue (i.e. new users must be approved before they receive their password)
|-
|allow_domains
|''
|When user submission is enabled this can contain a comma-separated list of domain names from which user submissions will not be queued (but approved automatically). Example: 'mycompany.com,myothercompany.com'
|-
|notification
|array()
|Send an email notification to <tt>$_CONF['site_email']</tt> when a new story, link, or event has been submitted or a new user has registered with the site. The <tt>array()</tt> can hold any combination of the strings <tt>'story'</tt>, <tt>'link'</tt>, <tt>'event'</tt>, and <tt>'user'</tt> (separated by commas), depending on which notification(s) you want. Example: <code>array('story','user');</code> would send notifications when a new story has been submitted or a new user has registered. No notifications would be sent for new links or events.
|-
|listdraftstories
|0
|When set to 1, this will display an additional block on the submissions page (<tt>moderation.php</tt>) that lists all the stories that have the 'draft' flag set.
|-
|postmode
|plaintext
|Sets the default submission mode to 'html' or 'plaintext'
|-
|speedlimit
|45
|Minimum delay between submissions in seconds. This helps prevent Denial of Service (DOS) attacks
|-
|skip_preview
|0
|If 1, allows submission of stories and comments without previewing (i.e. the submission form will always have a Preview and a Submit button).
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

E-Mail settings

2004-07-07T08:18:29Z

Robert:

Starting with Geeklog 1.3.9, Geeklog uses the PEAR::Mail class to send all
emails. You can then select whether emails should be sent through SMTP,
sendmail, or PHP's <code>mail()</code> function.
;Within <code>$_CONF['mail_settings']</code> you have the following options:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|backend
|mail
|Used to select how to send email. Can be one of 'smtp', 'sendmail', or 'mail'.
|-
|sendmail_path
|<tt>/usr/bin/sendmail</tt>
|If you chose 'sendmail' for the backend setting, this specifies the complete path to the sendmail binary.
|-
|sendmail_args
|<tt>''</tt> (empty)
| If you chose 'sendmail' for the backend setting, this variable can be used to pass additional parameters to the sendmail binary.
|-
|host
|smtp.example.com
|If you chose 'smtp' for the backend setting, this is the SMTP server to use.
|-
|port
|25
|If you chose 'smtp' for the backend setting, this is the port number to talk to on the SMTP server.
|-
|auth
|false
|If you chose 'smtp' for the backend setting, set this to <code>true</code> if your SMTP server requires authorization, and <code>false</code> if it doesn't.
|-
|username
|smtp-username
| If you chose 'smtp' for the backend setting, this is the name of your SMTP account.
|-
|password
|smtp-password
|If you chose 'smtp' for the backend setting, this is the password for your SMTP account.
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

RSS/RDF Feed Settings

2004-07-06T08:43:33Z

Robert:

;Geeklog can export its headlines to a so-called RSS feed (also known as an RDF feed). This will let you share your news with other sites (Hint&col:; Create a Portal block from Geeklog's Block menu to import RSS/RDF news feeds from other sites).
;Starting with Geeklog 1.3.9, RSS feeds can be created and configured from
Geeklog's Admin menu ("Content Syndication"). The following settings will only
be used as the default settings for any new feeds that you create from the
admin panel.

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Image Settings

2004-07-06T08:39:59Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|image_lib
|'' (empty string)
|Set this to either 'imagemagick', 'netpbm', or 'gdlib' if images should be resized during upload. Leave as '' if you don't want images to be resized or if you don't have those packages available.
|-
|path_to_mogrify
|''(commented out)''
|If you chose 'imagemagick' for $_CONF['image_lib'] above, then this should hold the complete path to the mogrify binary (from the ImageMagick package), e.g. '/usr/bin/mogrify'. 
You will need a fairly recent version of [http://www.imagemagick.org/ ImageMagick] for this to work (version 5.4.9 or newer is recommended).
|-
|path_to_netpbm
|''(commented out)''
|If you chose 'netpbm' for $_CONF['image_lib'] above, then this should hold the complete path to the directory where the binaries from the netpbm package are kept, e.g. '/usr/bin/netpbm/'. Note that the path must end in a slash. 
Precompiled binaries of the netpbm package for various platforms can be downloaded from the [http://sourceforge.net/projects/gallery/ Homepage of the Gallery] project.
|-
|keep_unscaled_image
|0
|Set this to 1 if you want Geeklog to keep the original, unscaled images after upload. The smaller image will then be used as a thumbnail and will link to the original image. Note that this may use a lot of disk space (depending on the size of your images).
|-
|max_image_width
|300
|Max. width of an image in pixels. If it exceeds this, it is either rejected or resized (depending on the setting of $_CONF['image_lib'] above).
|-
|max_image_height
|300
|Max. height of an image in pixels. If it exceeds this, it is either rejected or resized (depending on the setting of $_CONF['image_lib'] above).
|-
|max_image_size
|1048576 ''(equals 1 MB)''
|Max. size of an image in bytes. If it exceeds this, it is either rejected or resized (depending on the setting of $_CONF['image_lib'] above).
|-
|max_photo_width
|96
|Max. width of a user photo in pixels. If it exceeds this, it is either rejected or resized (depending on the setting of $_CONF['image_lib'] above).
|-
|max_photo_height
|96
|Max. height of a user photo in pixels. If it exceeds this, it is either rejected or resized (depending on the setting of $_CONF['image_lib'] above).
|-
|max_photo_size
|65536 ''(equals 64 KB)''
|Max. size of a user photo in bytes. If it exceeds this, it is either rejected or resized (depending on the setting of $_CONF['image_lib'] above).
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Links Settings

2004-07-06T08:33:09Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|linkcols
|3
|Number of columns to use when listing the categories in the links section. Set to 0 if you don't want categories listed.
|-
|linksperpage
|10
|Number of links to show per page. Set to 0 to show all links at once.
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Poll Settings

2004-07-06T08:29:29Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|maxanswers
|10
|Maximum number of possible answers for the poll editor
|-
|answerorder
|submitorder
|Sort answers by the number of results ('voteorder') or keep the order in which they were entered ('submitorder')
|-
|pollcookietime
|86400
|Number of seconds to set a poll answer cookie to time out on
|-
|polladdresstime
|604800
|Number of seconds to set a poll answer IP address to time out on
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Comment Settings

2004-07-06T08:27:37Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|commentspeedlimit
|45
|Number of seconds between posting a comment for the user
|-
|comment_limit
|100
|Most number of comments to show at any one time
|-
|comment_mode
|threaded
|How to display comments (threaded, nested, flat or nocomments)
|-
|comment_code
|0
|Default value for new stories: Comments enabled (0) or disabled (-1)
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Story Settings

2004-07-06T08:25:32Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|maximagesperarticle
|5
|max. number of images you can have in a story
|-
|limitnews
|10
|Number of stories to limit the index page to, this same number will appear in the older stuff block
|-
|minnews
|1
|Minimum numbers of stories than can appear on a topic page
|-
|contributedbyline
|1
|Show author username to public, and enable search by username (0=no, 1=yes)
|-
|article_image_align
|right
|Which side of article the topic image should be shown (right or left)
|-
|hideemailicon
|0
|When set to 1, this will disable the ability to send a story by email. It will also hide the email icon from stories and the "Email Article To a Friend" from the Story Options block.
|-
|hideprintericon
|0
|When set to 1, this will disable display of a story in a "printer friendly" format. It will also hide the printer icon from stories and the "View Printable Version" from the Story Options block.
|-
|showfirstasfeatured
|0
|When set to 1, this will render the first story on ''any'' page using the templates for a featured story, even if that story is not featured. This will even be applied to the first story on page 2 of a topic page, for example.
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Calendar Settings

2004-07-06T08:22:19Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|personalcalendars
|0
|Allow account holders to have a personal calendar
|-
|showupcomingevents
|1
|Show up-coming events (0=no, 1=yes)
|-
|upcomingeventsrange
|14
|Number of days that "Upcoming Events" will look ahead.
|-
|event_types
|Anniversary, Appointment, Birthday, Business, Education, Holiday, Meeting, Miscellaneous, Personal, Phone Call, Special Occasion, Travel, Vacation
|The set of event types that are used both on the public calendar and the user's personal calendars
|}
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

URL Rewriting

2004-07-06T08:17:21Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Topic, What's New & E-mail Settings

2004-07-06T08:17:07Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Submission Settings

2004-07-06T08:16:54Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Story Settings

2004-07-06T08:16:40Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Site Settings

2004-07-06T08:16:25Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|site_name
|GeekLog Site
|Name of your site
|-
|site_slogan
|Another Nifty GeekLog Site
|Slogan for your site. This is added to the HTML title field.
|-
|site_mail
|admin@example.com
|E-mail address for all admin mail
|-
|site_url
|http://www.yourdomain.com
|Base URL for your site (no trailing slash)
|-
|theme
|XSilver
|Default theme to use on the site
|-
|layout_url
|Site URL path, with layout dir and default layout
|Location of the default layout
|-
|path_themes
|/path/to/geeklog/public_html/layout/
|Directory where all themes reside
|-
|path_layout
|/path/to/geeklog/public_html/layout/XSilver/
|Path to current theme directory
|-
|allow_user_themes
|Can be 1 or 0
|If set to 1, users can set their own theme that the site uses
|-
|allow_user_language
|Can be 1 or 0
|If set to 1, users can select the language for the site navigation
|-
|allow_user_photo
|Can be 1 or 0
|If set to 1, users can upload a photo to their profile
|-
|hide_author_exclusion
|Can be 1 or 0
|If set to 1, the option to to exclude certain authors from being seen is hidden from the user's preferences.
|-
|site_enabled
|true
|A Geeklog site can be disabled quickly (e.g. for maintenance) by setting this to 'false'.
|-
|site_disabled_msg
|'Geeklog Site is down. Please come back soon.'
|This contains the message to display when a Geeklog site is disabled. If the text begins with "http:" then visitors are redirected to that URL.
|}

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Server Settings

2004-07-06T08:15:36Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
|path
|/path/to/geeklog/
|Base file system path for your site (trailing slash necessary)
|-
|path_system
|/path/to/geeklog/system/
|Path to your system directory for your site (trailing slash necessary). This directory holds the code libraries used throughout Geeklog
|-
|path_html
|/path/to/geeklog/public_html/
|Path to your web tree directory for your site (trailing slash necessary). This directory holds all the web pages used by Geeklog.
|-
|path_images
|/path/to/geeklog//public_html/images/
|Path where Geeklog expects to find its images, including user photos and images for stories.
|-
|path_log
|/path/to/geeklog/logs/
|File system path for the log files
|-
|path_language
|/path/to/geeklog/language/
|location of the Geeklog language files
|-
|backup_path
|Base path with "/backups/" suffix
|location where mysqldump (see above) will store database backups
|}

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

RSS/RDF Feed Settings

2004-07-06T08:15:14Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Poll Settings

2004-07-06T08:15:00Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Login settings

2004-07-06T08:14:43Z

Robert:

{| border=1 cellspacing=0
!Variable</th>
!Default Value</th>
!Description</th>
|-
| loginrequired
| 0
| Login is required to access ''any'' part of the site. When set to 1, this overrides the following settings. When you only want to block access to certain parts of the site, set this to 0 and select from the following settings.
|-
| submitloginrequired
| 0
| When set to 1, only registered users can submit stories, links, and events
|-
| commentsloginrequired
| 0
| When set to 1, only registered users can submit comments
|-
| linksloginrequired
| 0
| When set to 1, only registered users can access the links area
|-
| pollsloginrequired
| 0
| When set to 1, only registered users can access the list of recent polls
|-
| calendarloginrequired
| 0
| When set to 1, only registered users can access the calendar
|-
| statsloginrequired
| 0
| When set to 1, only registered users can access the site stats
|-
| searchloginrequired
| 0
| When set to 1, only registered users can use the advanced search. When set to 2, the simple search is blocked for anonymous users, too.
|-
| profileloginrequired
| 0
| When set to 1, only registered users can view another user's profile
|-
| emailuserloginrequired
| 0
| When set to 1, only registered users can use the email submission form to send an email to another user
|-
| emailstoryloginrequired
| 0
| When set to 1, only registered users can email stories
|-
|}

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Locale Settings

2004-07-06T08:13:52Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Links Settings

2004-07-06T08:13:42Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Image Settings

2004-07-06T08:13:29Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

E-Mail settings

2004-07-06T08:13:14Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Content Control Settings

2004-07-06T08:12:49Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Comment Settings

2004-07-06T08:12:38Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Calendar Settings

2004-07-06T08:12:22Z

Robert:

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Locale and Date Formats

2004-07-06T08:11:15Z

Robert:

{| border=1 cellspacing=0
!Variable
!Default Value
!Description
|-
| language
| english
|Name of your language file. Additional language files may be available for download at [http://www.geeklog.net/ www.geeklog.net ]. If you translate a language file, please send it to us. Also see [[Localization]].
|-
| locale
| en-gb
| Locale for the system
|-
| date
| %A, %B %d %Y @ %I:%M %p %Z
| Date format used for most of the site, including story displays. See [[Date_Format_Syntax|Date formats]].
|-
| daytime
| %m/%d %I:%M%p
| Date format used when a shorter date is needed. See [[Date_Format_Syntax|Date formats]].
|-
| shortdate
| %x
| Date format this is the shortest date. See [[Date_Format_Syntax|Date formats]].
|-
| dateonly
| %d-%b
| Short date format (day and month only), to be used e.g. in the Upcoming Events and Older Stories blocks. See [[Date_Format_Syntax|Date formats]].
|-
| timeonly
|%I:%M %p %Z
|Format string for the time only, to be used e.g. on the Event Details page. See [[Date_Format_Syntax|Date formats]].
|-
| default_charset
| iso-8859-1
| Character encoding used by Geeklog when serving HTML pages or sending email. Only used if the language file did not already set another character encoding.
|-
|}

;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

Locale and Date Formats

2004-07-06T08:08:36Z

Robert: