After some brainstorming and a lot of trial and error with T5 Rewrite and HM Rewrite, I went for the simplest possible solution. The permalink was actually intercepted by WordPress so I didn’t need the additional rewrite rule (even though it didn’t hurt, other than performance). I left %category%/%post_id%/%postname% as the default custom permalink, and … Read more
You’re missing your WordPress rewrite rules. It’s probably confusing because, in Apache, WordPresss automatically generates the rewrite rules in .htaccess. It does not do the same in nginx environments. Pay special attention to the WordPress documentation on nginx and configuration directives referencing HTTP rewrite rules, the “includes” directives for segmenting configuration and the specific WordPress … Read more
This will do. The slug is saved on the wp_posts while custom fields are on the wp_posts_meta. If you want to make it like that you can use an action hook on save_post that will get the value of the custom fields and saves it as the post slug. Here is the code add_action(‘save_post’, ‘set_slug’); … Read more
The redirect_canonical filter is responsible for this, which you can selectively disable depending on the requested page. This is untested, but should work: function wpa66273_disable_canonical_redirect( $query ) { if( ‘design-jobs’ == $query->query_vars[‘pagename’] ) remove_filter( ‘template_redirect’, ‘redirect_canonical’ ); } add_action( ‘parse_query’, ‘wpa66273_disable_canonical_redirect’ );
The WordPress Template Hierarchy already supports that: // Template Name date.php Then there’s wp_get_archives() where you can set the according args.
I assume you have a custom taxonomy for your CPT, so your CPT should be ‘job’ and your custom taxonomy can then be ‘jobs’ and then you’d have custom terms within that taxonomy for each job type. The Posts then would consist of the individual job with any associated relevant data (rate of pay, hours, … Read more
There is an API for exactly your use case: endpoints. Register an endpoint for EP_PERMALINK and when it is set display your form.
You do not need to re register post type. Symply go in you backend, Settings > Permalinks and set the permalink structure to a custom one: /magazine/news/%postname%/ then save changes. See image below:
This seems to work! ?post_type=directors&name=$matches[1] seems to be the key add_rewrite_rule( ‘directors/([^/]*)/showreels/([^/]*)/video/([^/]*)/?’, ‘index.php?post_type=directors&name=$matches[1]&showreel=$matches[2]&video=$matches[3]’, ‘top’ ); so final code now; function wpse13483_init() { add_rewrite_rule( ‘directors/([^/]*)/showreels/([^/]*)/video/([^/]*)/?’, ‘index.php?post_type=directors&name=$matches[1]&showreel=$matches[2]&video=$matches[3]’, ‘top’ ); } add_action( ‘init’, ‘wpse13483_init’ ); function wpa52794_query_vars( $vars) { $vars[] = ‘video’; $vars[] = ‘showreel’; return $vars; } add_filter( ‘query_vars’, ‘wpa52794_query_vars’ );
The Why Part If we have a page called technical and try to load: example.tld/technical/99999999999999999999 then the 99999999999999999999 part is treated as a page query variable with the value of 2147483647. The reason is this rewrite rule for pages: according to the handy Monkeyman Rewrite Analyzer by Jan Fabry. This part of the WP_Query::get_posts(): if … Read more