Hot answers tagged 500-internal-error
2
Sometimes I have a 500 error ( from NGinx ) just because I have a "character" getting outputted before the first header gets written ( or in-between ).
Activate WP_DEBUG = true and see what happens. 99% of the case I could spot the error from there. ( and it was nearly all the time the above error ).
Post back if that doesn't solve your debug difficulty ...
2
Internal Server errors are usually thrown when there's an error somewhere in the code. You did the right thing searching the logs, but depending on your hosting configuration not all errors can be written there.
I like using WordPress's own logging facility. Here's what you need to do:
Stick the following lines in your wp-config.php file
...
2
The transient is in place just fine, see get_dir_size() source.
Note that if you have enough files for this to cause major performance issues you are probably better disabling upload limit or it might mess up other related functionality like uploads.
1
The correct line number for this variable in the most recent WordPress version are 207 and 209. So I guess something has mangled your files.
It is impossible to answer what exactly happened without seeing that code.
Look for new user accounts, and re-upload all WordPress files from the source.
1
I solved the problem by using this code.
if ( ! function_exists( 'theme_post_meta_data' ) ) :
/**
* This function prints post meta data.
*/
function theme_post_meta_data() {
printf( __( '<span class="%1$s">Posted on </span>%2$s<span class="%3$s"> by </span>%4$s', 'theme' ),
'meta-prep meta-prep-author posted',
sprintf( '<a ...
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 ...
1
In phpmyadmin search :
SELECT *
FROM wp_options
WHERE option_name = 'template'
OR option_name = 'stylesheet'
OR option_name = 'current_theme';
then :
UPDATE wp_options SET option_value = 'yourthemename' WHERE option_name = 'template';
UPDATE wp_options SET option_value = 'yourthemename' WHERE option_name = 'stylesheet';
UPDATE wp_options SET option_value ...
1
I had the same issues, after some time of not touching the site it suddenly started producing "500 Internal Server Error" on various pages. After a week of pulling my hair it turned out that my "/wp-content/debug.log" (which I enabled a long time ago and then forgot about) was over 128 MB, and therefor could not be written to for some reasons, hence all ...
1
You can't really debug server errors without having really good access to the server itself. This would entail looking at the internal working of this particular host which I'm certain they would not allow nor spend any actual time trying to fix. Move to a better host if they cannot give you more details as to what the problem is or ask for access to the ...
1
Your site codereflect.com is not that heavy. Could be the Suffusion theme and its options making lots of DB calls. I'd use http://wordpress.org/extend/plugins/debug-queries/ to see what queries are being called and how many. And it also could be you're on a shared box at softlayer that is "too" shared with others.
1
Raising apc.shm_size from default value 32M to 256M in php.ini seems to do the trick for us.
edit: raising that value is not a bad idea, however it does not solve the issue in the long term. We are now considering removing either APC or Super Cache...
Only top voted, non community-wiki answers of a minimum length are eligible
