Mambo 2.6 question...

[PA-Scott]

I have two sites running Mambo... each was running 2.5.4 and I ugprade the one to 2.6. It's on nitrogen and everything is working perfectly fine.

I have another site, but it's on chamaeleon and I attempted the same upgrade and I got 500 Internal Server Error. The .htaccess is empty, and I made sure no directories were 777. So I'm sure I'm missing something 'stupid', but I can't figure out what.

Does anyone have any ideas, suggestions, or experience with Mambo 2.6 upgrade? I know there are reports of problems, but my other site is working perfectly fine so far with the 2.6 version.

I "DID" make backups of the home directory and database, so I'm in the middle of restoring that to at least get the site back up and running again.

Any guidance would be greatly appreciated.

Thanks,
Scott

[Ron]

"Ideas and suggestions" is my middle name, but I have no experience with Mambo.

Did you look at your server's error log through CPanel? Sometime that can be quite helpful in tracking down the error.

I am curious about having an "empty" .htaccess file; perhaps you should just remove it from the directories, and any above it (since they are inherited from above).

Good luck!

[sehh]

Apparently you'll get a 500 internal server error even if a single file is group writable (not just world writable)!.

I had to do something like: chmod -R g-w *

[PA-Scott]

"Ideas and suggestions" is my middle name, but I have no experience with Mambo.

Did you look at your server's error log through CPanel? Sometime that can be quite helpful in tracking down the error.

I am curious about having an "empty" .htaccess file; perhaps you should just remove it from the directories, and any above it (since they are inherited from above).

Good luck!

I did re-name the .htaccess to htaccess.txt just to see if that had an effect, but it didn't. I did not check my error logs in CPanel though...

But I just checked and it is empty.

[PA-Scott]

Apparently you'll get a 500 internal server error even if a single file is group writable (not just world writable)!.

I had to do something like: chmod -R g-w *

Huh, I didn't check that. I did do a mass change to 755 to make sure any files weren't 777 - but I didn't check the group writeable aspect.

I did a restore and did get everything working again using 2.5.4