WordPress has its own system managing redirects and page routes, you don’t need to edit the .htaccess file. You’ll want to start with the function add_rewrite_rule(). It takes 3 arguments: route (as regex) query vars priority So first, you need to find out the query vars of account/customer-bookings/. If it is a page, it can … Read more
You don’t need domain mapping in current versions of WP, it’s built in. You just need to edit the site Settings (under Network Admin, Sites, click on site then Edit). Enter the URL for the site (https://www.example.com or whatever). If you need to, use the Settings tab when editing the site and change all references … Read more
Looks like insert_with_markers() function becomes available during admin_init hook. So in order for your code to work, you should do the following: function do_my_htaccess_stuff_371705() { //function `insert_with_markers()` is working now } add_action(‘admin_init’, ‘do_my_htaccess_stuff_371705’);
Something else is going on here. WordPress does not erase the contents of the .htaccess file when it writes new permalinks; it appends the new permalink structure to the end of the file. Do you have anything other code or plugins that uses .htaccess? Are you on a Windows server that does not natively support … Read more
I’ve been looking for details on why that line is suggested for a multisite install using subdomains as well. I actually question if both of these are relevant for a subdomain install: RewriteRule ^(wp-(content|admin|includes).*) $1 [L] RewriteRule ^(.*\.php)$ $1 [L] In a sub-directory install the rules are setup slightly different to strip the sub-directory name … Read more
Redirect 301 /services /services/service-1 This results in a redirect loop because the mod_alias Redirect directive is prefix matching. So, the source path /services matches the redirected path /services/services-1, etc. etc. However, since you are already using mod_rewrite (as part of WordPress), you should also perform this redirect using mod_rewrite (as opposed to mod_alias). Different modules … Read more
Suggest you move your desired functionality to javascript; you are so badly attempting to overload the purpose of these constructs…even if you get it to work you are going to have a very fragile and difficult to maintain system on your hands. Note that the idea of inlining style may work — but future Content … Read more
You’ve put the code in the wrong place. The HTTP to HTTPS directives must go before the WordPress front-controller, otherwise it’s simply never going to get processed for anything other than direct file requests. Your custom directives should also be outside the # BEGIN WordPress block, otherwise WordPress itself is likely to override your directives … Read more
In short yes… ‘External’ Rewrite Rules If in add_rewrite_rule the rule is isn’t directed to index.php then the rule is treated as an ‘external’ rule (i.e. not to be processed by WordPress’ internal handing of rewrites) and instead written to the .htaccess file. I.e. if: add_rewrite_rule(‘^nutrition/([^/]*)/([^/]*)/?’,’somethingelse.php?p=12&food=$1 &variety=$2′,’top’); is used instead of add_rewrite_rule(‘^nutrition/([^/]*)/([^/]*)/?’,’index.php?p=12&food=$matches[1]&variety=$matches[2]’,’top’); Then the rule … Read more
The protection from .htaccess is for the folder /wp-admin it’s not for the URL Open up your ftp programme (or download WordPress) and look inside /wp-admin By only allowing your IP access this folder you’re blocking a lot of possible exploit issues (as mentioned in comments below). I always prefer to login at mysite.com/wp-admin and … Read more