[SOLVED] No site after update

[tgnc.org.uk]

I just updated from 1.6.7 to 1.7.

I checked PHP version, met minimum.

I have 2 versions on different URLs, the one is the public server, the other url is where I play with the code and what not.

The public URL stops at a blank screen

The test URL works fine and I assume that's because I haven't updated the code yet.

How do I roll back the update as it is obviously some problem with it.

[tgnc.org.uk]

Seems that the CMSMS is crashing

Code: Select all

 [Mon Apr 05 23:30:45 2010] [error] [client **.***.***.***] Premature end of script headers: index.php
 [Mon Apr 05 23:30:50 2010] [error] [client **.***.***.***] Premature end of script headers: index.php
 [Mon Apr 05 23:31:21 2010] [error] [client **.***.***.***] Premature end of script headers: index.php
 [Mon Apr 05 23:31:49 2010] [error] [client **.***.***.***] Premature end of script headers: index.php
 [Mon Apr 05 23:32:27 2010] [error] [client **.***.***.***] Premature end of script headers: login.php

The web host pointed me to the server logs for the domain in question. They're confirming that the issue is with CMSMS and not the server or PHP.

[Nullig]

Have you tried re-uploading the files - it looks like your FTP may not have completely copied everything over.

Nullig

[tgnc.org.uk]

Yep, done it twice.

Since the upgrade, I have not been able to log in to the sql server (phpMyAdmin) as it is reporting maximum connections has been exceeded, so I can not even back up the database.

I am scratching my head as I have looked at all sorts of possible answers.

[replytomk3]

I have not been able to log in to the sql server (phpMyAdmin) as it is reporting maximum connections has been exceeded

That is something that your hosting provider should find out for you.

Also, if you PM me hosting, ftp, admin info I can take a look.

[tgnc.org.uk]

This only happened AFTER the update as it was working fine up to that point, I was in phpMyAdmin minutes before I logged out and began the update.

[Peciura]

I agree with replytomk3. If you want you can rename "/index.php" to "/_index.php" this way CMSms will not work as source creating new connections to DB. To restart MySQL servers is just matter of 30s. Hosting company can spare you this time, can't it ? Have you tried to upload compressed data and then unpack it on server ? IMO some ftp client(i am having issues with FileZilla) have broken resume function, so i prefer overwriting existing files if they are smaller.

[tgnc.org.uk]

OK, well the DB issue is resolved, however...

I went to the trouble of going to the web host, performing the one click install of 1.6.6 and confirmed it works.
I then uploaded the 1.6.6 to 1.6.7 full diff upgrade and same for the 1.6.7 to 1.7

The site alternative site shows up as 1.6.7 AFTER the upgrade.

As for uploading compressed files, the server has no way of unzipping them. All administraion is done through the eXtend control panel which limits what can be done.

[tgnc.org.uk]

Where do I find the database connection information? I have looked through the admin console and do not see where these settings are kept.

[tgnc.org.uk]

I installed a new CMSMS to another URL and restored the database to it, added the plugins and other stuff and the site show one page, the "home" page, no other menu items are listed.

I checked in the admin side of things and they're all listed.

So questions...

How can an upgrade to 1.7 still show as 1.6.7?
Why does CMSMS not show the menus when the content is visible in the admin side of things?
How can I get a website CMS that has worked fine up until upgrade to 1.7 work again by rolling back the update? Does CMSMS have a "Rollback" option?

[Peciura]

DB connection info is in "/config.php"(file in site root) section "Database Settings".
Also you can upgrade from lets say from CMSms 1.2.5 right to CMSms 1.7 if you upload at least basic CMSms (not diff) to server.

There is no "Rollback" option, because files are being overwritten, you have to overwrite them back to 1.6.7  (download it by yourself from this site). You can run install of CMSms 1.6.7 , but DON'T create tables and default content in step 5. It could fix your issues.

...one click install of 1.6.6...

is that a feature of "eXtend control panel" to be able to install any CMS ? If that is true, still i would install CMSms by my self, because i do not know where do they get package of CMSms from.

Just curious, is  there "/mle" directory on your site? If yes, you probably uploaded "diff" package that is not compatible to original CMSms version you had. Uploading "cmsmadesimple-1.7-base.tar.gz" and running "/install/upgrade.php" should solve incompatibility issues.

[tgnc.org.uk]

The CMSMS is from the downloads page.

DB is almost untouched:
   created permission "Manage All Content"
   deleted permission  'Modify Page Structure'
   changed version from 31 to 32 on DB table "cms_version".

I am not clear on this bit, do I have to go in to the database and manually change these if I am uploading 1.6.7 full install?

[Peciura]

Looks like i was unclear indeed - DB should be ok. Just install "CMSms 1.6.7 full" without default content.

[tgnc.org.uk]

Thanks. I got it up and its now back to 1.6.7.

What I did was to ...

1. rename the index.php file
2. put in place a holding index.php page that simply said we were having problems.
3. uploaded the full install "NOT INCLUDING" the index.php page, that was uploaded last..!

I then visited the CMS url and got the site maintenance message...
I logged in under admin and it told me that certain files need deleting.

Deleted the SITEDOWN message in the /tmp/cache/
Deleted the install folder.
Removed the holding page from the site root and reinstated the .htaccess file

When that was done, the site came back up.

So once again, thanks for your input.

[tgnc.org.uk]

Not content with getting back up, I decided to investigate further and I find what the issue with 1.7 is.

a. config.php file is missing from the tar.
b. requirement for script runtimes for more than 30 seconds (upto 60 seconds) <-- basically where install is failing.

SO CHECK your web host to see if they will allow a longer execution time on the server otherwise you will be needing to see alternative hosting or dedicated hosting AND have a blank config.php file at the ready... You may need it.