Server Error When Editing Stack and Home Page
Permalink
Hi, i've trawled the forums and Google trying to find the answer but nothing i've found has helped. So hopefully someone out there may have some insight.
I'm receiving a 500 internal server error when I try to edit the homepage using Concrete5 but only when logged in as admin. I can still access the page on another account i've got set up on the site which only allows users to view the pages (not modify).
This occurred straight after assigning a stack to an area on the homepage, I also get the 500 error when i try and edit this stack. Everything else on the site (frontend+backend) works fine apart from the homepage and the stack.
Does anyone have any suggestions? I haven't edited the .htaccess file or config.php file.
I do have access to the server log but i've no idea what i need to be looking for in there.
Thanks for your time.
Matt
I'm receiving a 500 internal server error when I try to edit the homepage using Concrete5 but only when logged in as admin. I can still access the page on another account i've got set up on the site which only allows users to view the pages (not modify).
This occurred straight after assigning a stack to an area on the homepage, I also get the 500 error when i try and edit this stack. Everything else on the site (frontend+backend) works fine apart from the homepage and the stack.
Does anyone have any suggestions? I haven't edited the .htaccess file or config.php file.
I do have access to the server log but i've no idea what i need to be looking for in there.
Thanks for your time.
Matt
500 server errors are logged to the apache/php log, if you could cause the 500 internal error and post the last 10 lines that would help.
Hi Mnkras, thanks a lot for getting back to me.
I've literally just managed to fix it.
As far as I could tell, the error messages occurred after assigning a stack to an area on the homepage.
So after trying everything I could think of, I modified the name of the CORE_STACK_DISPLAY folder located in the Concrete folder. This allowed me to go into the page and delete the area and also delete the stack that i'd previously created, both pages that gave me the 500 error.
Hopefully this might help someone in this position in the future. Though i've got no idea why this worked, so if you've got any idea why it did it might prevent it from happening again.
Thanks.
I've literally just managed to fix it.
As far as I could tell, the error messages occurred after assigning a stack to an area on the homepage.
So after trying everything I could think of, I modified the name of the CORE_STACK_DISPLAY folder located in the Concrete folder. This allowed me to go into the page and delete the area and also delete the stack that i'd previously created, both pages that gave me the 500 error.
Hopefully this might help someone in this position in the future. Though i've got no idea why this worked, so if you've got any idea why it did it might prevent it from happening again.
Thanks.
