[SOLVED] Problem w/upgrade from 1.2 to 1.2.x
[SOLVED] Problem w/upgrade from 1.2 to 1.2.x
CMS is great software. I've been using it for several months after searching for over a year for a replacement for phpwebsite. When I found CMS and started playing around with it I knew right away that this was exactly what I was looking for. Kudos to the developers. I have one website fully converted and online, another that is converted and will be online soon, and 2 others that I plan to convert as time allows. The one website that is currently online is giving me problems with upgrading from 1.2 to any of the 1.2.x upgrades. I've tried about every possible combination that I could think of and nothing works. The other website that isn't (officially) online is with the same webhost and on the same machine and it has been upgraded from 1.2 -> 1.2.1 diff -> 1.2.2 diff -> 1.2.3 diff without any problems so that tells me the software is compatible with my webhost. It is a MUCH smaller website but I don't think that should make a difference. For the record this is on a linux box with Apache 1.3.39, MySQL 4.1.22, and PHP 4.4.7. When attempting to upgrade the end result is the same, I cannot access the site nor can I login as admin regardless if I try to apply the diff files in order or if I use the full version and upgrade. I've also tried using the full version, doing a regular install but choosing to not install the tables without any success. Every time I restore back to 1.2, everything works great. This particular website has at least 1000 pages (probably closer to 2000, I haven't counted recently) and is much larger than the other website that has taken the upgrades without any problem. Nothing is showing up in my apache error log although that may be a problem with the webhost, I have them looking into it. Any suggestions?
Last edited by uagrad92 on Fri Jan 04, 2008 7:37 pm, edited 1 time in total.
-
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Problem w/upgrade from 1.2 to 1.2.x
it shouldn't be, but could be a module problem.... have you checked your php error log?
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: Problem w/upgrade from 1.2 to 1.2.x
Thanks for the quick reply. How would I go about checking my php error log? My webhost provides DirectAdmin which limits me to what I can see and can't see. I've never seen a php log file and nothing is showing up in the Apache error log file. Thanks!
-
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Problem w/upgrade from 1.2 to 1.2.x
the php error log is the apache error log (sorry for the way I phrased it).
Uhm... with ~2000 pages, I'd bet that you're running into a memory error. What's the php memory_limit set to?
Uhm... with ~2000 pages, I'd bet that you're running into a memory error. What's the php memory_limit set to?
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: Problem w/upgrade from 1.2 to 1.2.x
If the rowcount of the content_props table is the accurate number of pages for a website then I have 1,669 pages.
Re: Problem w/upgrade from 1.2 to 1.2.x
I finally was able to upgrade the site by deleting all the existing files except for config.php, uploading and extracting the 1.2.3 full bundle, and chmod the correct directories to 777. Then I was able to login as admin and verify the database was in sync with the php files. After that I removed the install directory and the Site Down file and I was back online with the 1.2.3 release. I'm fairly certain that I did this yesterday but I could not login as admin after doing so. Hopefully this will help others that may have similar problems.