I recognize that rule. It’s the unusual rule I wrote to deal with the permalink uncertainty issue. 🙂 First, you’ll only get that weird rule if you have your custom permalinks set to start with a non-numeric value. Like, if you have your custom permalink string as just %postname% instead of something like %year%/%postname%. Next, … Read more
Your setup is all over the place. Lets refer to the visual overview here: http://codex.wordpress.org/Template_Hierarchy#Visual_Overview Your page is going to use the page.php template. Your custom post type weine will use single-weine.php Your custom taxonomy sorte ( probably not the best name as it might clash ) will use the template taxonomy-sorte.php So we can … Read more
The undesirable answer I alluded to in my question is to intercept WordPress’ routing and URL generation. Manipulate the URLs with: add_filter(‘post_type_link’, ‘my_post_link’, 10, 3); function my_post_link($permalink, $post, $leavename) { if ($post->post_type == ‘publication’) { $year = date(‘Y’, strtotime($post->post_date)); return site_url(“/publications/$year/$post->post_name”); } return $permalink; } Then intercept the routing: add_action(‘template_redirect’, ‘my_template_redirect’); function my_template_redirect() { if … Read more
example.com/event/london-2012/speakers/john-doe You need an “event” post type and a “speaker post type. The event post type should be hierarchical and should have a sub-page called “speakers” which should use a custom template that displays all the “speaker” post types assigned to that event (see the Posts 2 Posts plugin). Then you can create other sub-pages … Read more
If you don’t want WordPress to overwrite your changes in .htaccess file, then make sure that you write your changes outside of the WordPress comment block, that is, either before or after this: # BEGIN WordPress … # END WordPress Think of this area as WordPress’ territory. Anything within this block, will be overwritten by … Read more
As the question was modified, I modify my answer. This task is relatively easy, doable just with a single rewrite rule, which converts everything after /mypage/ string into a variable – I call it var. As this is added to query_vars via hook, is reachable via global $wp_query; echo $wp_query->var;. add_filter( ‘query_vars’, ‘binda_query_vars’ ); function … Read more
I had the same issue and found a solution. From what I learned so far, there might be two causes to this problem: WP doesn’t recognize your rewrite rules because they are not cached yet. You can check this by dumping get_option( ‘rewrite_rules’ ); and if your rules did get cached, then they’ll be in … Read more
one way you could do this with an internal WordPress rewrite, which would then set a query var you could check when enqueueing your javascript, and pass that data via localize script. so first, rewrite rule to intercept requests to gallery/ with something appended, load the page named gallery, and set the query var gallery_id … Read more
I changed: add_rewrite_rule(‘^brand-list/([^/]*)/([^/]*)/page/([0-9]+)?’,’index.php?pagename=brand-list&brand=$matches[1]§ion=$matches[2]&paged=$matches[3]’,’top’); to: add_rewrite_rule(‘^brand-list/([^/]*)/([^/]*)/page/?([0-9]{1,})/?$’,’index.php?pagename=brand-list&brand=$matches[1]§ion=$matches[2]&paged=$matches[3]’,’top’); Note the difference is /page/([0-9]+)? is now /page/?([0-9]{1,})/?$ seems to be working now.
In the tags of your answer there is <plugins> so I think you are trying to add custom rewrite rules from a plugin. In your question you say something about page template that is (generally) a theme-related matter. Of course you can create rewrite rules from a plugin and use them for a page template … Read more