Blog crashed after activating the mystique 3.2.9 theme> Error 500

• 

  umang2012 · Member · Feb 16, 2012 at 4:08 am

  • Copy link
  • Add topic to favorites

  I installed the theme Mystique 3.2.9 on my dashboard. As soon as i clicked activate my Blog was wiped off and showed Internal Error 500.
  I cannot access the blog or the dashboard anymore.

  On surfing through forums>
  1.I tried using FTP through Filezilla and deleted the theme file from the directory. > Nothing
  2.I changed the name of the plugins folder > No gain
  3.I created the .htaccess(on notepad and uploaded it) and uploaded index.php file in the root directory > Nothing changed
  4.I deleted the wp-includes files and replaced them with freshly downloaded wp-includes files > Nothing changed

  I Have to fix this problem ASAP and get my blog up and running. Please help me out here forum

  URL: http://www.blog.nmumang.org
  FTP : http://ftp.blog.nmumang.org
  Blog url: http://www.blog.nmumang.org/

• 

  helper-ringostarr · Member · Feb 16, 2012 at 9:07 am

  • Copy link

  http://www.blog.nmumang.org/ is a self-hosted WordPress.org blog, which we really can’t help with.

  To clear up any confusion, WordPress.com and WordPress.org are two different entities.

  WordPress.org has complete support and documentation sites for self-hosted/installed versions of WordPress via their Codex and Support Forums.

  Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins. If that resolves the issue, reactivate each one individually until you find the cause.

  If that does not resolve the issue, try switching to the Twenty Ten theme (WordPress 3.0 and 3.1) or the Twenty Eleven theme (WordPress 3.2 and higher) to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the Twenty Ten theme (WordPress 3.0 and 3.1) or the Twenty Eleven theme (WordPress 3.2 and higher) to activate and hopefully rule-out a theme-specific issue.
  If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

  If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, the folks in the WordPress.org Support Forums may be able to help, but they’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.