Geeklog Forums

Template Error: set_root: /home/myweb/public_html/test//home/myweb/public_html/test/layout/XSilver/ is not a directory. Halted. This is the error I get now when I reach the success page. I am assuming ther eis an issue with the "//" between test and home. how do I remove it? I think this is the only thing holding me back from having a geeked site.

No, the error is not with the two slashes. I'm beginning to sound like a broken record, but those two slashes are displayed by the template engine Geeklog uses and are not the problem here. Look at the path again. Don't you notice anything? Parts of it are duplicated - it contains "/home/myweb/public_html/test" twice. Check your settings for $_CONF['path'] and $_CONF['path_html']. Also, should you have done any changes to $_CONF['path_themes'] or $_CONF['path_layout'] then please revert them - the default settings for those will work fine. bye, Dirk

OK this is what I have as I understand the instructions that are given in the config.php $_CONF['path'] = '/home/myweb/public_html/test/'; // C:/inetpub/wwwroot/geeklog/ // You only need to change this if you moved or renamed the public_html // directory. In that case, you should specify the complete path to the // directory like this: $_CONF['path_html'] = '/path/to/your/public_html/'; $_CONF['path_html'] = $_CONF['path'] . '/home/myweb/public_html/test/'; Now I have everything uploaded to a test dir in pub_html folder so i can test this CMS out before converting. According to my understnading, what is above should be correct.

Your $_CONF['path_html'] is not correct. You either need to define $_CONF['path_html'] relative to $_CONF['path_html'] (as is the default): $_CONF['path_html'] = $_CONF['path'] . 'public_html/'; or as an absolute path: $_CONF['path_html'] = '/path/to/your/public_html/'; I must have explained this more than a hundred times by now and still people keep making the same mistakes over and over again. If anyone can come up with a clear explanation that we can put in the installation instructions, I would be really grateful. It does get a bit tiresome over time ... bye, Dirk

Well everything that pertains to geeklog is residing in my test dir. Nothing for geeklog is in my pub_html. The path is the absolute path to everything that geeklog needs to run. I still fail to see how this is incorrect and I do apologize that you have to repeat things over and over but maybe, just maybe, it's a hint to clear up confusion because your last reply really made no sense to me at all. I have worked with other CMS and have never experienced such issues with installing them.

Geeklog is easy to set up. In my experience, many people just make their lives too hard by changing too much in config.php when things don't work out as expected. I've tried to explain the minimal changes which are necessary to get Geeklog up and running in another thread.

My problem is that I really can't think of other ways to explain the setup process. Maybe it's the fact that English is not my native language, maybe it's the medium (i.e. posting stories and comments on the web). Would we do this face to face, I swear you would have Geeklog up and running in less than five minutes - even without me touching the keyboard.

Okay, one last attempt: $_CONF['path'] should point to where your config.php is. $_CONF['path_html'] should point to where lib-common.php and index.php are. If you left Geeklog's public_html directory as it was, then you don't even need to change $_CONF['path_html']. If you moved it away from its original place, then make sure you set $_CONF['path_html'] up with an absolute path, as explained above, i.e. take out the "$_CONF['path'] ." bit.

And if you still can't figure out what I'm talking about, then I'm going to quit software development and start a new career as a baker tomorrow ;-)

bye, Dirk

Ok well don't start baking cookies yet.. I did manage to get things up BUT I have this error in the page Warning: fopen("/home/myweb/public_html/test/logs/error.log", "a" - Permission denied in /home/myweb/public_html/test/lib-common.php on line 1425 Which is referring to this line: if( !$file = fopen( $logfile, a )) Now what lol BTW how well can ya make double chocolate chip? lol

Looks like the "error.log" file isn't writeable by your web server program. Check its permissions and make the file writeable by the web server program. Try chmod 775 on error.log or if that doesn't work, try chmod 777 on it.

Well, that is explained in the installation instructions (#3 in that list). Twice, actually.

Not understanding the subtleties of the paths is one thing, not reading the instructions properly another one ...

bye, Dirk

Actually last night I did chmod both files and folder to 775 and to 777 withoout any luck. This morning the chmod 777 finally stuck. 775 wouldn't work for me. Now to start working on the site and see how things go.