After trying many things with permissions, I found my problem. I uses a plugin called Duplicator to move WordPress installs around from server to server, it handles changing URLS’s and Paths. So in settings => Media => Store uploads in this folder it was setting the Full Filepath to my Uploads folder. I changed it … Read more
Look at your .htaccess file in your public_html folder for your WordPress installation. It seems that when with GoDaddy hosted on the windows package, you need the following inheritance set for rewrite in your .htaccess file: RewriteOptions inherit RewriteEngine on That solved my problem on index.php.
Your problem is that you’re using Reserved Terms. error is a reserved term, you can’t use it. To get around this, you could intercept the request early, and do a redirect, changing the query parameters in the process. For example, handling a link get parameter: add_action( ‘wp’ , ‘reserved_term_intercept’ ); function reserved_term_intercept(){ global $wp_query; if( … Read more
Yes, a plugin that does not properly clean up after itself can continue to affect your site even after deletion. It can leave stuff behind in the database, or make alterations to your .htaccess file, which is probably the case in your scenario. You might need to restore your .htaccess file – look here for … Read more
You can use var_dump() instead of print_r() – you get the type and the value of the variable and it will also work when your variable holds FALSE or NULL. print_r( false ); # doesn’t output anything var_dump( false ); # output: bool(false) print_r( NULL ); # doesn’t output anything var_dump( NULL ); # output: … Read more
1) Looks like you are using the Visual Composer Plugin which is a legacy version which has a deprecated function. If you are using old version upgrade your Visual Composer plugin to the latest version which is 5.0.1. 2) Another case might be your are using a theme which might be using Visual Composer as … Read more
The theme check plugin checks your theme also for any default class that is generated by WordPress itself. Take a look into codex for some more info. All you have to do, is to cover these classes in your CSS file, for example: .alignleft { text-align:left } This will remove the errors from theme checker … Read more
Seems a duplicate. https://stackoverflow.com/questions/11916987/uncaught-syntaxerror-unexpected-token-illegal-load-scripts-php1, Try to find that error with Google as there are a lot of results You can also try editing your wp-config.php file ( it is located on the root folder of your installation ) and right before the lines that say: /* That’s all, stop editing! Happy blogging. */ and add … Read more
I see a few errors in your code: Your first line: <html lang=”<?php language_attributes(); ?>” dir=”ltr”> should actually be: <html <?php language_attributes();?> dir=”ltr”> (notice that you dont need to add lang=. The function does that by itself. That will likely fix the problem) You didn’t add the ; to 2 of your lines in the … Read more
You can use the wp_php_error_message filter to customise this message: add_filter( ‘wp_php_error_message’, function( $message, $error ) { return ‘My custom message.’; }, 10, 2 ); I haven’t tested to be sure, but I would assume that if the critical error that causes this message happens to be in the code of same theme or plugin … Read more