You could try changing the permissions on the .htaccess file itself. 755 7 – owner – read/write/execute 5 – group – read/execute 5 – everyone else – read/execute Neither WP or a plugin can edit/overwrite it; but then you would need to manually change it from there on out. Maybe that will help you narrow … Read more
Enable debugging in wp-config.php and check for errors. define( ‘WP_DEBUG’, true ); If you see blank white screen then it means.. Either you renamed your theme folder name. Some plugin is blocking access. Enable debigging and post errors here. EDIT You will have to try uploading files manually. Download no content WordPress from here. https://downloads.wordpress.org/release/wordpress-4.0-no-content.zip … Read more
Use the File Manager from cPanel or use a FTP account, and easily create your folder wherever you want and then direct the user with its real path something like: http://example.com/code/somepath/index.html It should work. 🙂
If your second subfolder installation is successful, you may likely run into an issue when WordPress writes its Permalink (within the subfolder). The issue apparently has to do with the subfolder installation and how it sees the site root path. WordPress will normally write a .htaccess file in the installation directory, and that folder is … Read more
manual modifications of .htaccess must be done after “# END WordPress” to not be overwrited
The RewriteEngine On line (as you have indicated) isn’t necessary, and pertains to a different module, mod_rewrite. You should remove it from the mod_headers block. It’s possible that you don’t have the Headers Apache module installed or activated on your host. If it is possible to run the test with some breakage, you could try … Read more
This is a pointless question. you either do a sitewide HTTPS or just don’t do it at all. Doing HTTPS for only some pages is just lying to yourself about the security of the site. You can decide to have HTTPS for only some of your users, but you can never do it just on … Read more
As far as I can see, it is not possible to use a custom 404 ErrorDocument directive in your htaccess file because WordPress’ index.php will always be found when processing the htaccess content. (unless ofcourse index.php got deleted for some reason) Because index.php is found, it will not trigger the ‘404 not found’ ErrorDocument directive. … Read more
Managed to figure it out and want to share it with others in case they’re having the same issue. When protecting wp-admin, protect it using wp-admin/.htaccess file, but that only works for the wp-admin directory, and won’t affect the wp-login.php file which is outside that directory. Add protection to the wp-login.php file using the <files></files> … Read more
As I’m running my WordPress on Nginx, so I can’t help on the .htaccess one. But I can comment on the padlock issues. There are a few things need to be done at WordPress: Login into WordPress Admin Dashboard, and go to WordPress Settings and change the WordPress Address (URL) and the Site Address (URL) … Read more