Quote by: Roger
Talked to others and found out the issue.
You cannot install it within public root. Meaning it cannot be installed as ...public_html/
It has to be ...public_html/some_directory_name/
This makes absolutely no sense. Lots of folks do that. The trick is to copy the CONTENTS of /path/to/geeklog/public_html/ into your /public_html/.
Perhaps your host doesn't recommend doing that. But there's not reason you can't do it.
Apparently The script that geeklog uses for Fantastico
Geeklog doesn't use any script for Fantastico. Fantasico wrote their own script without consulting the Geeklog developers. Any errors caused by Fantastico are their own fault. I don't speak for Geeklog but my presumption is that Geeklog would prefer that users do installs manually so users know what is inside Geeklog and so that users will have some knowledge of how to upgrade Geeklog when there are security issues.
Perhaps Geeklog could contact Fantastico and provide them with the revised information or install script to avoid this.
Or your host could contact Geeklog and ask for help making the install clean on their system.
They suggested many people will start entering /home/some_name/public_html/ because they saw "/path/to/your/public_html/" and that the install.php script in the browser window also started with /home/...
This all sounds correct. I don't understand why it is "wrong".
Geeklog assumes that you will put Geeklog in the root of your html path so that your site url is "http://www.example.com/index.ph" and not "http://www.example.com/geeklog/index.php" Your host wants to put the /geeklog/ in there because using Fantasico, users can install dozens of scripts and all of them start with index.php. But for a "real" website, you are only going to install one CMS and that CMS should be in your root html path.
In my case the provider suggested changing the name of the admin folder right away (security! - everyone knows about admin).
That is not security. Look up "security through obscurity" on the web. It is not real security. Geeklog provides the ability to rename /admin/ because some host providers map the interface into their administration console (like cpanel) to http://www.example.com/admin and if geeklog were to use /admin there would be a conflict. If your host doesn't use /admin for anything, then you don't need to change the geeklog setting.
When you install using the install.php through the browser you do see it looking for the config.php script via the full /home/some_name/public_html/ - So, I can see where the confusion comes from.
Actually the confusion is that your host doesn't use the Apache default "htdocs" for your root, instead it uses "public_html" which is just a directory name Geeklog uses to hold the public half of its files.
As a side note, I manually installed the old Geeklog and there was no where near this pathing confusion - It was smooth. I've also installed tons of others manually; Wordpress, Joomla!, Bitweaver, Serendipity, DotProject, osCommerce, Moodle, and on and on... But no where the issue I had with the new Geeklog version yesterday.
How old? The install really has not changed in several versions.
I've installed several Open Source web apps that auto-create/discover the pathing and write that to the config file themselves (as long as we chmod 777 that file). That coding is available all over as GPL; so maybe so savvy developer knows how to integrate it into Geeklog.[/p]
Geeklog has a rep for security and thus writing to config.php is not wise. Only the admin should make changes to config.php.