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 error when viewing rendered templates

March 24, 2010 1:38pm

Subscribe [2]
  • #1 / Mar 24, 2010 1:38pm

    MarqueDigital

    33 posts

    I’m having a strange problem. My ExpressionEngine works fine. I can edit and publish entries , create templates etc both locally and on the live server. However the problem that arises is on the live server. When I try and view rendered templates I get a blank white page and my browser tells me it’s received a 500 error.

    Hoping anyone has and ideas on this or have experienced it themselves in the past. Really strange. All my paths etc are correct. I used deeploy helper to move the site from my local test server to the live server.

  • #2 / Mar 24, 2010 1:43pm

    MarqueDigital

    33 posts

    The only plugins I’m using is the FieldFrame and File, oh, and deeploy helper.

  • #3 / Mar 24, 2010 5:45pm

    Ingmar

    29245 posts

    Can you take a look at your server error logs, or ask your host for more information? A 500 error is always the servers fault, it’s either mis-configured, running out of resources or been instructed to show that error.

    Are you running mod_security, by any chance?

  • #4 / Mar 25, 2010 7:10am

    MarqueDigital

    33 posts

    The hosting is Mosso Rackspace. I’m not sure if they use mod_security or not but will find out.

  • #5 / Mar 25, 2010 7:28am

    MarqueDigital

    33 posts

    The strange thing is on my first dev site which is on Mosso also, works perfectly.

  • #6 / Mar 25, 2010 8:05am

    MarqueDigital

    33 posts

    Two quotes from the Mosso tech support

    “Thanks for holding. A blank page usually means an error is being generated within the site’s code, can you try enabling detailed errors in ee?”

    and

    ” Thanks for holding. I apologize however I was not able to enable detailed errors for EE. I recommend inquiring with EE in regard to what their SEF features require. Alternately I also recommend trying to enable SEF with mod_rewrite, perhaps that may work.  Search Engine Friendly links. Basically EE is rewriting the urls internally. So instead of http://phase2.nolitan.com.php5-16.websitetestlink.com/index.php?path.to.actual.content.Q23 it’s rewritten as http://phase2.nolitan.com.php5-16.websitetestlink.com/index.php/site/site_content/”

  • #7 / Mar 25, 2010 8:38am

    MarqueDigital

    33 posts

    Ok, it seems as though the path.php file was missing on the server. It’s working now.

  • #8 / Mar 25, 2010 9:41am

    Sue Crocker

    26054 posts

    Glad you were able to find out what the problem was. Don’t hesitate to post again as needed.

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

ExpressionEngine News!

#eecms, #events, #releases