Your .htaccess and wp-config.php look fine. Error 101 is usually caused by a network, router or proxy issue. It could also be related to your browser cache and or cookies Have you tried connecting with a different browser or computer or clearing your browsers cookies? It can also be caused by your computers antivirus or … Read more
download a copy of wordpress.zip file then unzip it, copy /wp-admin/includes/update-core.php file and overwrite the one on the problem site. that worked for me.
Your .htaccess is not readable (like the error noticed). So make your .htaccess readable using permission 644. Source Now check again, perhaps now your stylesheet will be loaded? If not, check if the stylesheet file is readable. May this not be the cause, check the owner of the files.
If you want to provide restricted access, you should add an additional string with the /wp-login.php URL. For example: http://example.com/wp-login.php?restricted_site_access=key_string If the URL does not have such a string parameter, then you can redirect them to a 404 page; you don’t need to rewrite the .htaccess file for it.
Adding redirect to htaccess in the way that you have done will not work without adjudicating the site url to be https as well. If it is http, you will get endless redirect due to wordpress detecting that you are trying to access a non canonical URL (the https), and will try to redirect you … Read more
This is a dead end approch as the enqueue API do not support such versioning format which means that you will have to avoid using it, which is not a great thing. Your specific problem here is that you added the rule too late, RewriteRule . /index.php [L] “transfers” handling to wordpress and nothing is … Read more
You can give the read-only rights to .htaccess to prevent it from the modifications or removal. $cd <your website directory> $chmod 400 .htaccess
Are you trying to use that function without first initiating it in an action? It should be done like so: add_action( ‘rest_api_init’, ‘add_custom_users_api’); function add_custom_users_api() { register_rest_route( ‘route’, array( ‘methods’ => ‘GET’, ‘callback’ => ‘function’, )); }
Strip the preceeding forward slashes from your rules: Example (incorrect) RewriteRule ^/css/(.*) /wp-content/themes/themename/css/$1 [QSA,L] Example (correct) RewriteRule ^css/(.*) wp-content/themes/themename/css/$1 [QSA,L] All rules (correct) # BEGIN WordPress <IfModule mod_rewrite.c> RewriteRule ^/index\.php$ – [L] RewriteRule ^css/(.*) wp-content/themes/themename/css/$1 [QSA,L] RewriteRule ^js/(.*) wp-content/themes/themename/js/$1 [QSA,L] RewriteRule ^img/(.*) wp-content/themes/themename/img/$1 [QSA,L] RewriteRule ^font/(.*) wp-content/themes/themename/font/$1 [QSA,L] RewriteRule ^plugins/(.*) wp-content/plugins/$1 [QSA,L] RewriteCond %{REQUEST_FILENAME} !-f … Read more
You don’t really need these: Redirect 404 /install.php Redirect 404 readme.html To block readme.html you do this: <files readme.html> order allow,deny deny from all </files> For other kind of files you need do the same just change file name in code.