ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

500 internal server error after renaming template group

October 27, 2010 12:36am

Subscribe [2]
  • #1 / Oct 27, 2010 12:36am

    Tyssen

    756 posts

    These are the steps I took that led to the error:

    1. Mounted account as a disk in Transmit.
    2. Dragged assets folder to Textmate to edit templates.
    3. Logged into CP and then deleted /admin/ template group.
    4. Renamed /site_admin/ to /admin/.
    5. Renamed /admin/ in the templates folder on the server to /old_admin/ and then /site_admin/ to /admin/ (and then eventually deleted /old_admin/).
    6. Tried to access the control panel and got the 500 error. Same thing happened for the EE front end.

    Everything else on the site which isn’t related to EE works OK. First thing I thought of was the .htaccess but deleting it didn’t fix it.

    Checked the error logs, the one in root doesn’t have any recent enries, the one in the system folder has Unable to parse XML data but the error was reported from before I made the changes and there’s also an entry for the same error from the previous day so I don’t think it’s that.

    Not sure what else to look at.  :grrr:

  • #2 / Oct 27, 2010 3:30pm

    Ingmar

    29245 posts

    Where are you getting this error, when accessing the template group? What version and build are you using? Also, if this is a real 500 error there certainly should be more info in the server log, perhaps consider asking your host for assistance.

  • #3 / Oct 27, 2010 5:21pm

    Tyssen

    756 posts

    No getting the error on everything - system and front end. No pages linked to EE work. I’ll get on to the hosts to see if I can get more info.

  • #4 / Oct 28, 2010 4:33pm

    Ingmar

    29245 posts

    Sounds good. Please let us know what you find out.

  • #5 / Oct 28, 2010 5:15pm

    Tyssen

    756 posts

    I jumped the gun a bit it in instantly thinking there was something wrong with EE because the rest of the site was working. It turns out it was PHP that had failed on the server and it needed to be restarted.

  • #6 / Oct 28, 2010 5:17pm

    Ingmar

    29245 posts

    So, that solves it?

  • #7 / Oct 28, 2010 5:25pm

    Tyssen

    756 posts

    Yep. 😊

  • #8 / Oct 28, 2010 5:42pm

    Ingmar

    29245 posts

    Excellent 😊

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases