500 internal server error when module manager accessed...

Help with getting the CMS CORE package up and running. This does not include 3rd party modules, PHP scripts, anything downloaded via module manager or from any external source.
lxne
New Member
New Member
Posts: 6
Joined: Wed May 14, 2008 8:10 pm

Re: 500 internal server error when module manager accessed...

Post by lxne »

session.save_path /tmp /tmp
User avatar
Nullig
Power Poster
Power Poster
Posts: 2380
Joined: Fri Feb 02, 2007 4:31 pm

Re: 500 internal server error when module manager accessed...

Post by Nullig »

Use a custom php.ini file:

session.save_path = path/to/temp/directory

The path has to be the path to your account / the directory you want to use for sessions.

Or, have your hosting company enable FASTCGI mode.

Nulli
Last edited by Nullig on Thu May 15, 2008 12:01 am, edited 1 time in total.
lxne
New Member
New Member
Posts: 6
Joined: Wed May 14, 2008 8:10 pm

Re: 500 internal server error when module manager accessed...

Post by lxne »

OK, I made this .ini file and first copied it to the modulefolder (modules/ModuleManager). Nothing changed.
Then I moved the php.ini file into the admin-folder and voilà no more 500 error.
But the modulemanager diplays no modules and I can't switch to settings either!?
:(

Just found out, that I got the same problem (no content in the tabs of module-page) with the PageBlocks-Module if the php.ini resides in the admin folder.

After some more testing I head to realize that it's irrelevant if the php.ini file has any content. An empty php.ini file in the admin folder has the same effect as one with the session.save_path line. No 500 error but no content in the tabs of modulemanager and pageblocks.
Last edited by lxne on Thu May 15, 2008 7:42 am, edited 1 time in total.
Locked

Return to “[locked] Installation, Setup and Upgrade”