Trivial update: noted compatibility through WP 5.8+ and minor reorganization and tweaks to unit tests<\/p>","2.5.1":"
Trivial update: noted compatibility through WP 5.7+ and updated copyright date (2021).<\/p>","2.5":"
Minor update: Minor compatibility updates, restructured unit test file structure, expanded unit test coverage, and noted compatibility through WP 5.5+.<\/p>","2.4.2":"
Trivial update: Updated a few URLs to be HTTPS and noted compatibility through WP 5.4+<\/p>","2.4.1":"
Recommended bugfix release: prevented interfering with permalinks for non-category taxonomies<\/p>","2.4":"
Minor update: modernized unit tests, noted compatibility through WP 5.3+, added TODO.md, and updated copyright date (2020)<\/p>","2.3":"
Minor update: tweaked plugin initialization process, created CHANGELOG.md to store historical changelog outside of readme.txt, noted compatibility through WP 5.1+, updated copyright date (2019)<\/p>","2.2.1":"
Trivial update: minor documentation and code formatting tweaks, noted compatibility through WP 4.9+, and updated copyright date (2018)<\/p>","2.2":"
Recommended update: changed default HTTP redirect status code to 301 (permanent), fixed PHP warning in WP 4.7 due to function deprecation, restructured code, compatibility is now WP 4.6-4.7+, added more unit tests, updated copyright date, more<\/p>","2.1.2":"
Trivial update: verified compatibility through WP 4.5; updated copyright date (2016).<\/p>","2.1.1":"
Trivial update: noted compatibility through WP 4.1+; updated copyright date (2015); added plugin icon<\/p>","2.1":"
Minor update: added unit tests; noted compatibility through WP 3.8+<\/p>","2.0.4":"
Trivial update: noted compatibility through WP 3.5+<\/p>","2.0.3":"
Trivial update: noted compatibility through WP 3.4+; explicitly stated license<\/p>","2.0.2":"
Trivial update: noted compatibility through WP 3.3+<\/p>","2.0.1":"
Bugfix release: fixed bug triggered when creating new post (especially recommended if using %category% in custom permalink structure)<\/p>","2.0":"
Recommended update. No functional changes, but many changes to formatting and documentation; noted compatibility through WP 3.2.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":"5"},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":1092767,"resolution":"128x128","location":"assets","locale":""}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":845064,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.0","2.0.1","2.0.2","2.0.3","2.0.4","2.1","2.1.1","2.2","2.3","2.4","2.4.1","2.4.2","2.5","2.5.1","2.5.2"],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[89,2758,537,2662,8712],"plugin_category":[],"plugin_contributors":[78189],"plugin_business_model":[],"class_list":["post-5705","plugin","type-plugin","status-publish","hentry","plugin_tags-category","plugin_tags-coffee2code","plugin_tags-link","plugin_tags-permalink","plugin_tags-structure","plugin_contributors-coffee2code","plugin_committers-coffee2code"],"banners":{"banner":"https:\/\/ps.w.org\/single-category-permalink\/assets\/banner-772x250.png?rev=845064","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/single-category-permalink\/assets\/icon-128x128.png?rev=1092767","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n
Reduce permalinks (category or post) that include entire hierarchy of categories to just having the lowest category in the hierarchy.<\/p>\n\n
By default, WordPress replaces the %category% permalink tag in a custom permalink structure with the entire hierarchy of categories for the post's first matching category. For example, assuming your site has a hierarchical category structure like so:<\/p>\n\n
Applications\n |_ Desktop\n |_ Web\n |_ WordPress\n<\/code><\/pre>\n\nBy default, if you have a permalink structure defined as %category%\/%year%\/%monthnum%\/%day%\/%postname%<\/code>, your post titled \"Best Plugins\" assigned to the \"WordPress\" category would have a permalink of:<\/p>\n\nhttps:\/\/www.example.com\/applications\/web\/wordpress\/2008\/01\/15\/best-plugins\n<\/code><\/pre>\n\nIf you activate the Single Category Permalink plugin, this would be the permalink generated for the post (and recognized by the blog):<\/p>\n\n
https:\/\/www.example.com\/wordpress\/2008\/01\/15\/best-plugins\n<\/code><\/pre>\n\nIn order for a category to be used as part of a post's permalink structure, %category%<\/code> must be explicitly defined in the Settings -> Permalinks admin page as part of a custom structure, i.e. \/%category%\/%postname%<\/code>.<\/p>\n\nFor category links, %category%<\/code> is implied to follow the value set as the \"Category base\" (or the default category base if none is specified). So if your category base is 'category', the above example would list posts in the 'WordPress' category on this category listing page:<\/p>\n\nhttps:\/\/www.example.com\/category\/applications\/web\/wordpress\/\n<\/code><\/pre>\n\nWith this plugin activated, that link would become:<\/p>\n\n
https:\/\/www.example.com\/category\/wordpress\/\n<\/code><\/pre>\n\nNOTE: The fully hierarchical category and post permalinks will continue to work. The plugin issues a 302 redirect to browsers and search engines pointing them to the shorter URL.<\/p>\n\n
Links: Plugin Homepage<\/a> | Plugin Directory Page<\/a> | GitHub<\/a> | Author Homepage<\/a><\/p>\n\nHooks<\/h3>\n\n
The plugin exposes one filter for hooking. Code using this filter should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain). Less ideally, you could put them in your active theme's functions.php file.<\/p>\n\n
c2c_single_category_redirect_status (filter)<\/strong><\/p>\n\nThe 'c2c_single_category_redirect_status' hook allows you to specify an HTTP status code used for the redirect. By default this is 302.<\/p>\n\n
Arguments:<\/p>\n\n
\n- $status (integer) : The default HTTP status code<\/li>\n<\/ul>\n\n
Example:<\/p>\n\n
\/**\n * Change the redirection HTTP status to a 302.\n *\n * @param int $code The HTTP status code. By default 301.\n * @return int\n *\/\nfunction scp_change_redirect_status( $code ) {\n return 302;\n}\nadd_filter( 'c2c_single_category_redirect_status', 'scp_change_redirect_status' );\n<\/code><\/pre>\n\n\n\n- Install via the built-in WordPress plugin installer. Or download and unzip
single-category-permalinks.zip<\/code> inside the plugins directory for your site (typically wp-content\/plugins\/<\/code>)<\/li>\n- Activate the plugin through the 'Plugins' admin menu in WordPress<\/li>\n
- Use
%category%<\/code> as a permalink tag in the Settings<\/code> -> Permalinks<\/code> admin options page when defining a custom permalink structure<\/li>\n<\/ol>\n\n\n\nWill existing links to my site that used the full category hierarchy still work?<\/h3><\/dt>\nYes, WordPress will still serve the category listings and posts regardless of whether it is of the full category hierarchy format or just the single category format. But do note that WordPress doesn't perform any sort of redirects; it responds directly to the category\/post URL requested.<\/p><\/dd>\n
Could this give the appearance that I have duplicate content on my site if pages are accessible via the full category hierarchy permalink format and the single category permalink format?<\/h3><\/dt>\nWhether this plugin is active or not, WordPress treats both types of category links the same. This plugin will however issue redirects for all of the non-canonical category and post permalink pages to point to the single category link version.<\/p><\/dd>\n
What can this plugin do for me if I don't use `%category%` in my custom permalink structure?<\/h3><\/dt>\nIn addition to handling custom permalink structures (used to generate permalinks for posts) that contain %category%<\/code>, the plugin also shortens category archive links. WordPress by default generates those links in a fully hierarchical fashion which this plugin will reduce to a single category. See the Description section for an example.<\/p><\/dd>\nDoes this plugin include unit tests?<\/h3><\/dt>\nYes.<\/p><\/dd>\n\n<\/dl>\n\n\n
2.5.2 (2021-09-28)<\/h4>\n\n\n- Change: Note compatibility through WP 5.8+<\/li>\n
- Unit tests:\n\n
\n- Change: Restructure unit test directories\n\n
\n- Change: Move
phpunit\/bin\/<\/code> into tests\/<\/code><\/li>\n- Change: Move
phpunit\/<\/code> into tests\/<\/code><\/li>\n<\/ul><\/li>\n- Change: Remove 'test-' prefix from unit test file<\/li>\n
- Change: In bootstrap, store path to plugin file constant<\/li>\n
- Change: In bootstrap, add backcompat for PHPUnit pre-v6.0<\/li>\n<\/ul><\/li>\n<\/ul>\n\n
2.5.1 (2021-04-30)<\/h4>\n\n\n- Change: Note compatibility through WP 5.7+<\/li>\n
- Change: Update copyright date (2021)<\/li>\n<\/ul>\n\n
2.5 (2020-09-23)<\/h4>\n\n\n- Fix: Default the
$taxonomy<\/code> argument of category_link()<\/code> to 'category' to avoid a PHP warning\/error<\/li>\n- Fix: Handle the possibility that
get_category()<\/code> could return null<\/code> for an invalid category ID<\/li>\n- New: Add a TODO item about removing deprecated functions (which is not something I want to do just yet, hence the TODO)<\/li>\n
- Change: Update docs for return value of
category_link()<\/code> to reflect that WP_Error<\/code> or null<\/code> are also possible values<\/li>\n- Change: Note compatibility through WP 5.5+<\/li>\n
- Change: Restructure unit test file structure\n\n
\n- New: Create new subdirectory
phpunit\/<\/code> to house all files related to unit testing<\/li>\n- Change: Move
bin\/<\/code> to phpunit\/bin\/<\/code><\/li>\n- Change: Move
tests\/bootstrap.php<\/code> to phpunit\/<\/code><\/li>\n- Change: Move
tests\/<\/code> to phpunit\/tests\/<\/code><\/li>\n- Change: Rename
phpunit.xml<\/code> to phpunit.xml.dist<\/code> per best practices<\/li>\n<\/ul><\/li>\n- Unit tests:\n\n
\n- New: Add tests for
category_link()<\/code>, post_link()<\/code><\/li>\n- New: Add
unset_permalink_structures()<\/code> to unset configured permalink structures<\/li>\n<\/ul><\/li>\n<\/ul>\n\n