I suspect REQUEST_URI is actually resolving to something like index.php?page=xxx Yes, it would seem that mod_rewrite is processed before the Apache Expression is evaluated. So, the URL has already been rewritten to index.php (the WordPress front-controller) before we get to evaluate the requested URL in the expression. However, we can get around this by setting … Read more
Here is an example of adding custom rewrite rule to WordPress. For instance, you have a link http://website.com/1/ that would like WordPress interprets internally as http://website.com?tl=1 But for tl you have mentioned, I am not sure what is your settings. So I assume tl is working in your system. Because WP default parameter is p … Read more
As @JacobPeattie suggested in comments: If you just add index.html to the root of your WordPress installation that should become the homepage. This does, however, require that the DirectoryIndex is set appropriately. For example: DirectoryIndex index.html The DirectoryIndex is the document that Apache tries to serve when you request a directory. In this case, the … Read more
Just switch the theme, then delete the theme you bought and after edited the .htaccess reinstall it. This should work without problems. If you have access to cpanel, set the values from the php settings section instead of rely on the .htaccess file.
I found that by removing the WordPress section from the .htaccess in the main website root, both main website custom 404 and WordPress custom 404 functionality appear to work correctly. Is there any reason why I shouldn’t do this? Yes, this is what I was going to suggest. If WordPress is installed in the subdirectory … Read more
editing the .htaccess file on wp.com with : Header add Access-Control-Allow-Origin: “https://js.com” Header add Access-Control-Allow-Methods: “GET” Header add Access-Control-Allow-Headers: “Upgrade-Insecure-Requests” works
I think the directive in .htaccess is inherited by subfolder The mod_rewrite directives in the root .htaccess file are not inherited by the /blog/.htaccess file (by default). You would need to specifically enable mod_rewrite inheritance, however, this probably adds unnecessary complexity. I try to modify the .htaccess under /blogs/ by adding the above directive again. … Read more
It doesn’t work with add_rewrite_rule() because of the ?view= part in the URL (it’s the first parameter for the function) — i.e. WordPress strips that query string part, hence it’s not included when WordPress finds a matching rewrite rule. how I can remove ?view=12a34b56 after set post name You can’t (not on the same page), … Read more
Yes, basically debug.log, but without deny, with 404 Yes, that directive will serve a “404 Not Found” when attempting to request debug.log. |log? However, because of the ? in the above regex, it will also block debug.lo. Is that intentional? In fact, if that is intentional then you could simply remove the g? part – … Read more
The nginx equivalent of RewriteCond %{REQUEST_URI} ^.*wp-content/uploads/restricted/.* RewriteRule ^wp-content/uploads/(restricted/.*)$ dl.php?file=$1 [QSA,L] will be the location ~ ^/wp-content/uploads/(?<file>restricted/.*) { rewrite ^ /dl.php?file=$file last; } If you want to apply this to several folders under /wp-content/uploads, use location ~ ^/wp-content/uploads/(?<file>(?:restricted1|restricted2|restricted3)/.*) { rewrite ^ /dl.php?file=$file last; } I don’t think there can be any other solution for nginx … Read more