Ok managed to figure this out, instead of adding action for a rewrite. Because what I was wanting to rewrite was a taxonomy i should have been using something like this : ‘rewrite’ => array(‘slug’ => ‘listings/make’, ‘product_make_model’ => false) When registering the taxonomy, which basically rewrites the slug as the taxomomy is created/registered. Works … Read more
You can prevent access to the file in question by modifying your .htaccess file or creating one, should you have none, with content as follow: # BEGIN Prevent access to README <Files “README”> order allow, deny deny from all </Files> # END Prevent access to README Please note: your .htaccess file should be located in … Read more
The following .htaccess will only work if the subdomain is assigned in your DNS setting using either a single DNS record or a wildcard DNS record. If your DNS setting doesn’t have that record, request to your subdomain will not reach to your server. So the .htaccess will not work. If you don’t know how … Read more
I know you are asking about htaccess and rewrite rules, but, you are trying to hide your hacked condition from google, rather than finding the backdoor that’s been installed, and the hacker is just going to change his method of putting spam pages on your site, you will get the “may have been” warning again, … Read more
I found the problem. A hacker placed a backdoor (wp-admin/29) and forced to rewrite the htaccess with it! Thank you for the hint @WebElaine
They aren’t really connected. It’s just a redirect after all. The error means that some code in your website wrongly passes a WP_Error object to wp_kses_no_null(). In your position I’d put something like this into this function for debugging: if ( is_wp_error( $string ) ) { var_dump( $string ); debug_print_backtrace(); } This way you can … Read more
You don’t appear to have a valid SSL cert installed on your server that covers the hostname www.subdomain.example.com, ie. the www sub-subdomain`. The only way to resolve this and not get the browser warning is to install a valid certificate on your server that covers the required hostname. Otherwise, unless the user accepts this invalid … Read more
Access your site via ftp or cPanel/plesk, making sure that hidden-files are visible. Find your .htaccess file. Make a backup on the server by copying & renaming (uploading a .htaccess file with the wrong encoding could break it and make things even worse) Find the lines which start with / look like the following (or … Read more
Enqueue the script or style using wp_enqueue_script() or wp_enqueue_style()
According to the Codex instructions: https://codex.wordpress.org/Changing_The_Site_URL If you add these defines to your wp-config.php define( ‘WP_HOME’, ‘http://example.com’ ); define( ‘WP_SITEURL’, ‘http://example.com’ ); These will override the options saved in your wp_options table, you should then remove the /NewSite suffix from your General Settings page. (Or if wp-admin is accessible now you may be able to … Read more