Geeklog Forums

Is it me or is upgrading GL (or any other CMS) a pain in the arss and a risky thing?

Forgive me but being a programmer myself, I totally respect the work put into GL, but there are some things that could be better handled such as config data. Why can't config data be put into its own file that does not exist in the GL package. The Gl config file could reference this other file, but updates/upgrades won't overwrite it. Also, it could be manipulatd by an install process as needed.

In my initial install (1.3.9), I placed GL in two different directories, a geeklog directory outside of my document root and then other files in my document root. The upgrade doc doesn't cover this. Following the upgrade doc would have me putting all files in my documet root. Am I missing something?

Added: Additionally, I just got to the part of the upgrade involving plugins. Ouch man, ouch. I can't just copy the entire directory because staticpages is there. There's got to be a better way. An upgrade should not be this difficult. I switch to GL from PHP-Nuke for these reason thinking that GL didn't have these issues.

I'd like to help make GL2 the best CMS on the planet, so this is why I am voicing my concerns here and now.

---

Mechwars Robot Combat Webmaster
www.tcmechwars.com
Fight Robots Not People

Thanks for posting this. I am having many of the same problems on my sites. I just upgraded from 1.38 to 1.3.11 and so many things are not working. I am affraid I have to roll it back.

Regards,
Rick