No, you are on the right track as far as the add_rewrite_rule function is concerned. The generated rewrite rule doesn’t send a 303 header. The problem, in this case, is with your code which can be fixed easily. On this line: add_rewrite_rule(‘^recommendations\/(.*)\/?’, ‘recommendations/’, ‘top’); you are making WordPress to output a modified, custom .htaccess file … Read more
You could use the parse_request hook. For example: add_action( ‘parse_request’, function ( $wp ) { // Run your actions only if the current request path is exactly ‘image-generator’ // as in https://example.com/image-generator if the site URL is https://example.com if ( ‘image-generator’ === $wp->request ) { $a = $_GET[‘a’]; $b = $_GET[‘b’]; $etc=”etc”; // … your … Read more
I assume that your custom post type windows would map onto /windows/ etc? You can customise the template for individual custom post types via single-posttype.php in your theme, e.g. single-windows.php single-doors.php and single-garages.php WordPress will automatically pick these up You could also use custom page templates, e.g. page-windows.php or custom templates with the right template … Read more
This is the default WordPress .htaccess: # 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 Please add add the following line to it to prevent the default behavior for your custom route. RewriteCond %{REQUEST_URI} !^/my-vue-route/(.+) Like this: … Read more
WordPress has a function to send a different status header: status_header( 200 ); If you send that after WordPress has send its headers and before you print anything you will get a status header 200. You could also filter ‘status_header’ and change the value there. See wp-includes/functions.php for details.
The thing in WP that hits a passable balance of such functionality to not so painful implementation is rewrite endpoint. They are structured a little differently from your example (i.e. /tab/2) but they are easy to implement and order of magnitude less painful than dealing with Rewrite API usually is.
It’s because of how you’ve defined the accepted methods: ‘methods’ => ‘\WP_REST_Server::CREATABLE ‘, You shouldn’t have quotes around it. WP_REST_Server::CREATABLE is a string that equals ‘POST’, but by putting quotes around it you’re literally setting the method as ‘\WP_REST_Server::CREATABLE’, which is not a valid HTTP method. You can see this in the response to the … Read more
Here is what I have in my own .htaccess file that does what you’re looking for: # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On Options +FollowSymLinks RewriteBase / RewriteRule ^index\.php$ – [L] RewriteRule ^example.html$ /wp-content/raw/example.html [L] RewriteRule ^download$ /wp-content/raw/download-ebook.html [L] RewriteRule ^thanks$ /wp-content/raw/book-opt-in-thank-you.html [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # … Read more
You may want to use this resource. You can create own post types links (and probably relational template structure) They said you can create domain.com/{prefix}/{post-type-slug}/{postname} like URLs with their code (Also you create even custom ones).
If you’re willing to create a child theme and put your PHP files in there, this approach is relatively clean. For each file, create a rewrite rule where you specify the path you want to use and the filename that should load. In the example below, /custom-path/ loads custom-file.php from the root of your child … Read more