My VBSEO died after Hostgator updated SQL and PHP

I just upgraded my board from 3.7.0 RC2 to 3.7.0 GOLD tonight. It seemed to work great for about an hour and then died.

I noticed after accessing cPanel that the PHP and SQL were just upgraded - I think about the same time that the board died. I know it was just upgraded because I checked the versions prior to performing the vb3.7g upgrade to see that they met minimum system reqs.

Now, if I activate vbseo in vbseocp, I get 404 errors on all rewritting urls.

AT first I thought it was a permissions error as the error log in cpanel said "no execute permissions for vbseo.php"
Permissions were set to 644 - I changed them to 755.

PHP: 5.2.5
MySQL 5.0.45-community
PERL 5.8.8
vBSEO 3.1.0

Any ideas?

Make sure you uploaded vBSEO .htaccess file to your forum root

Dodge, could you let me know when this is resolved. The server i am on, hasn't got upgraded yet. I'm on the gold version right now. This was worring me when HG upgrades. Also please see the repy above.

update from hostgator:

The issue should be corrected now. The problem looks to have been caused by a .htaccess file in the forum directory.
There is a file in there called, .htaccess.offline, which has the default rewrite rules for vbseo to work. I've checked other sites using this same script and the same code in your .offline file was in their .htaccess file. Since you did not have a .htaccess file in your forum directory, I copied the .offline one over and enabled the module. I am now able to navigate through your forums without any 404 errors. Josh

But I didn't do it. Seems this was caused by their upgrade.

I'm glad the issue is solved

Strange thing is.. I never created a file called .hataccess.offline, so I am not sure how my vbseo settings were moved to that file. I suspect that my host, or the upgrade of SQL or PHP did that. It wasn't me and it's not in my backups. I did have the .htaccess file with all the rewrites in it prior to their upgrades and it has been running fine for two years.

I suspect that they (hostgator support) simply corrected a mistake/oversight/error made by another Hostgator support person.

I wonder if the original .htaccess file was causing issues with their upgrades and they had to temporarily disable it, and then forgot to rename it back...?

In any case, I wish they'd send out an automated notice when they do major upgrades to our box. I was chasing ghosts, thinking I had caused the issue with the upgrade of vbulletin, which occurred an hour earlier. I was moments away from restoring an old backup.

And I wish the (first level) tech support staff would have a way of checking that (recent upgrade) when you report an issue so as to not send us webmasters on a wild goose-chase.

My experience with Hostgator has been, for the most part, good. But they do seriously lack in the area of proactive communication (with each other, and with their customers). I think all the problems I have had with them relate to one hand not knowing what the other hand is doing. They seem to be their own worse enemy. Upon talking to the 1st support person , Bobbie, she should have been able to say "I see that the server your domains reside on was just upgraded or is being upgraded right now- that may be the issue." It would have saved me hours of stress and work, not to mention downtime.