This is a subcomponent of the Permalinks component.
Recent posts on the make/core blog
View all posts tagged rewrite-rules.
83 open tickets in the Rewrite Rules component
83 open tickets. Last 7 days: +2 tickets
20 tickets that have no replies
View list on Trac
-
#20520 Author Page Pagination Broken When Removing /author/ Slug
-
#30907 Rewrite Rules collision
-
#34385 Missing site_url path results in array to string conversion
-
#38518 Rewrite Rules rebuilding on parse_request
-
#39442 Custom rewrite endpoints and wp_old_slug_redirect
-
#40322 WordPress Network htaccess rewrite causes internal loop multisite
-
#40395 New action: pre_generate_rewrite_rules
-
#41211 When the /category/category-name portion is repeated in the URL, it serves content instead of 404
-
#41680 Added rewrite tags using add_rewrite_tag() not working on static front-page
-
#41891 Bug when changing $(comments_)pagination_base of WP_Rewite instance to string with non-ASCII characters
-
#41946 Option to delete_with_markers
-
#42120 htpasswd protection not working due to .htaccess rewrite rules
-
#42478 Add_permastruct ignores EP_NONE and other args if %post_id% is present in struct
-
#43676 .htaccess rules don't work with Plain
-
#43678 Add indents to default .htaccess rules
-
#45337 Strange pagination issue
-
#45970 in IIS if web.confing <configuration has xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0" attribute the WordPress creates new <configuration> section and the site craches with wrong web.config administration
-
#46000 non empty post object in case of error 404
-
#46087 Short-circuit `page_on_front` check during site creation multisite
-
#47087 flush_rewrite_rules() should check $wp_rewrite->flush_rules() is callable before calling it
2 tickets slated for 5.3
View list in Trac
-
#47087 flush_rewrite_rules() should check $wp_rewrite->flush_rules() is callable before calling it
-
#47466 Add a comment to .htaccess markers, labelling inserted strings as read-only/ dynamic docs
83 open tickets
Open bugs: 55. View list on Trac
Help maintain this component
Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.
Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.
Contributors following this component:
