There are so many for internal server error. The main reasons for internal server errors are. Corrupt .htaccess file PHP Memory limit Corrupted plugin Incompatible PHP version Corrupted core files In oder to fix this issue, you need to investigate in step by step order. To solve this issue first of all you need to … Read more
An update & resolution: I asked the web host for help and they found that I had a piece of code in .htaccess limiting the access to wp-config.php. Once the code was removed, all worked as it should.
This ended up being an error I had in the .htaccess file. I replaced that with a default WP one and everything is good!
Is $posts a reserved variable Yes, it is, $posts is the global variable which holds the array of posts from the main query. This is how it is set: $GLOBALS[‘posts’] = & $wp_query->posts; Just remember, $posts === $GLOBALS[‘posts’]
For the sake of clarity, this should be your .htaccess RewriteEngine On RewriteBase /zingery/wordpress/ RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /zingery/wordpress/index.php [L]
If you want to check one Plugin’s Function / Class etc. from another Plugin, then it’s best to use a hook like plugins_loaded. Based on this, your Plugin CODE will look like: <?php /* Plugin Name: YOUR PLUGIN NAME */ defined( ‘ABSPATH’ ) or exit; add_action( ‘plugins_loaded’, ‘plugin_prefix_woocommerce_check’ ); function plugin_prefix_woocommerce_check() { if( function_exists( ‘is_woocommerce’ … Read more
Assuming you’re on Linux, if you go to your wp-content/plugins folder and run grep -R ‘htaccess’ * it should let you know if any plugins are addressing that file by name
I had the same issue and did not find any information in my debug output. It worked out, that DOING_AJAX was not defined (I don’t know why). Changing the beginning of async-upload.php from if ( isset( $_REQUEST[‘action’] ) && ‘upload-attachment’ === $_REQUEST[‘action’] ) { define( ‘DOING_AJAX’, true ); } to define( ‘DOING_AJAX’, true ); worked … Read more
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 … Read more
Error pages are served up via .HTACCESS, if you are using Apache you would use the ErrorDocument directive and add the status and URL to it. So it would look like this in your .htaccess file: ErrorDocument 401 http://yourwebsite.com/error-401 ErrorDocument 403 http://yourwebsite.com/error-403 ErrorDocument 500 http://yourwebsite.com/error-500 You could use the following function below. This will dynamically … Read more