Take the 2-minute tour ×
WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

I'm using the "default" setting for permalinks, at least I just switched back to that, and I'm still getting a 500 response code when trying to get to any post page like mysite.com/?p=4536

I can see how that could happen with permalinks on, with the .htaccess file causing some strange things, but why would it possibly ever happen with a blank .htaccess file, and no permalinks on? Any thoughts?

Update 1

  • I checked the error logs, nothing helpful there except a mention of the errors.
  • I purposefully cleared the .htaccess in order to see if it was a problem, and the server error is still occurring.
  • The front page of the site is up and running fine, but when you click to a post, with permalinks turned on or without, it returns the 500 error.
share|improve this question
    
I think problem in cache plugin or memory limit (php.ini) –  user15194 Apr 14 '12 at 17:52
    
I deactivated all plugins one by one and there is no change. I'm not sure why memory limit would make a post have a 500 error when the home page works fine? –  Jason Rhodes Apr 14 '12 at 17:57
    
Try add to wp-config.php this line define('WP_MEMORY_LIMIT', '128M'); or more.. –  user15194 Apr 14 '12 at 18:04
    
I don't think it's helpful to suggest doing that without any reason why it would fix this problem. I wouldn't want my clients to start arbitrarily increasing their memory limits because of a 500 server error. Especially when the error is specific to a certain set of pages and not across the entire site. –  Jason Rhodes Apr 15 '12 at 17:12

1 Answer 1

  • Error 500 ISE is very generic and can be caused by numerous underlying issues. Your first step should be locating error log for your hosting account or asking support to help with that.
  • It may indicate .htaccess issue. Regenerate .htaccess, and be sure the encoding in your text editor is Unicode No BOM

  • It may also indicate a problem with the configuration on the server. Usually your hosting company tech support can help.

share|improve this answer
    
Thanks, so I think we can rule out all these things, at least under the conditions I listed in "Update 1" above. Let me know if that makes anything clearer. –  Jason Rhodes Apr 14 '12 at 17:42

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.