Can’t access htaccess [closed]
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
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
On a Mac this is pretty easy to do, I believe it should be the same on a PC (more or less). Note: Since Chrome no longer plays with domains ending .dev I tend to set up all my local sites on a subdomain, eg: if the public site is www.example.com I would use dev.example.com. … Read more
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()
Try adding the following to a manually generated .htaccess file # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress Without knowing more about the version of WordPress used & the setup of your web-server that’s the ebst … Read more
It looks like your localhost site had WordPress installed in the root directory but your production site is in a sub-directory. You should review the instructions in the the WordPress Codex for Moving WordPress to see if you missed any steps. It describes both moving a WordPress installation from one server to another, and moving … Read more
You can try something like the following at the very top of your .htaccess file in the document root (before the WordPress front-controller, ie. before the # BEGIN WordPress block): RewriteRule ^([\w-]+/)wp-admin /$1 [R,L] This will redirect /<site>/wp-admin to /<site>/ – where the site name can consist of any of the characters a-z, A-Z, 0-9, … Read more
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