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. 🙂
WAY #1 – cPanel I assume your host is using cPanel managing your Server. Browse domainname.com/cpanel, login their with cPanel credential: Change the values according the following image: Don’t forget to check the “Wildcard Redirect” to redirect all the subfolder/subpages also (Thanks to @RobertHue). Add the redirection and you are done. WAY #2 – .htaccess … Read more
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 by design and intentional. WordPress rewrites have become increasingly complex over the years, and many plugins utilise the page endpoint for a page (usually with a template and custom query) – redirecting introduces a potential world of pain. Long story short, it doesn’t matter anyway. WordPress adds <link rel=”canonical /> for pages, so … Read more
To ensure your content isn’t crawled from the hidden admin DOMAIN you could include something like this in your .htaccess file. RewriteEngine On #Force traffic to production URL RewriteCond %{HTTP_HOST} !xxxx.com$ [NC] RewriteRule (.*) http://www.xxxx.com/guides/%{REQEUST_URI} [R=301,L] There is more than one way to handle this first redirect so your code may work too (didn’t test … 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