Welcome to Geeklog, Anonymous Sunday, October 13 2024 @ 03:32 am EDT
Geeklog Forums
Some short tips
mick
Anonymous
Hello,
I have been having a very hard time installing geeklog and did not know where the problem was. At first was not sure if it was a programming error or a users error. It actually happened to be a users error and a simple error. My paths all seemed correct or so I thought. From my experience if you run linux, my distro you need to be sure your doing things correctly.
1. Make sure to update lib-common.php if you happen to move your geeklog install folder again. If you move and forget to do so again despite even if your mysql geeklog database is fine. You will get an error that something is wrong with your database. In a white screen 1 line webpage.
2. Make sure that if your using apache you have the paths correct. In my case I had to at first move public_html contents on the outside. Which was a potential danger even though secured the work around.
find:
DocumentRoot /var/www/yoursite/yourfolderifyouhave/public_html
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/common/yoursite>
This is more correct otherwise you will need to have two instances of contents inside public_html and outside. Not secure at all this is really simple but was overlooked. Perhaps a word of mention inside the documentation?
I have been having a very hard time installing geeklog and did not know where the problem was. At first was not sure if it was a programming error or a users error. It actually happened to be a users error and a simple error. My paths all seemed correct or so I thought. From my experience if you run linux, my distro you need to be sure your doing things correctly.
1. Make sure to update lib-common.php if you happen to move your geeklog install folder again. If you move and forget to do so again despite even if your mysql geeklog database is fine. You will get an error that something is wrong with your database. In a white screen 1 line webpage.
2. Make sure that if your using apache you have the paths correct. In my case I had to at first move public_html contents on the outside. Which was a potential danger even though secured the work around.
find:
DocumentRoot /var/www/yoursite/yourfolderifyouhave/public_html
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/common/yoursite>
This is more correct otherwise you will need to have two instances of contents inside public_html and outside. Not secure at all this is really simple but was overlooked. Perhaps a word of mention inside the documentation?
7
7
Quote
All times are EDT. The time is now 03:32 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content