Trivial update:minor tweaks that should go unnoticed, restructured unit test file structure, added a TODO.md file, and noted compatibility through WP 5.5+.<\/p>","3.0.1":"
Trivial update: Updated a few URLs to be HTTPS and noted compatibility through WP 5.4+.<\/p>","3.0":"
Revival update: added functions for getting URL of previous\/next post, modernized unit tests, added CHANGELOG.md, changed plugin initialization, updated compatibility to be WP 4.9-5.3+ updated copyright date (2020), and much more. See changelog for potential breaking change to a filter.<\/p>","2.6.1":"
Trivial update: improved support for localization, minor unit test tweaks, verified compatibility through WP 4.4+, and updated copyright date (2016)<\/p>","2.6":"
Recommended minor update: Added new template tags for getting the adjacent or looped post object; minor bug fixes; noted compatibility through WP 4.3+<\/p>","2.5.2":"
Trivial update: noted compatibility through WP 4.1+ and updated copyright date (2015)<\/p>","2.5.1":"
Trivial update: noted compatibility through WP 4.0+; added plugin icon.<\/p>","2.5":"
Major update: added support for navigating by taxonomy; added non-echoing versions of functions, and more filters; added unit tests; noted compatibility through WP 3.8+; dropped compatibility with WP older than 3.6<\/p>","2.0":"
Recommended major update: synced with changes made to WP; added filters; changed arguments to existing filters; renamed and deprecated all existing functions and filters; noted compatibility through WP 3.5+; and more. (All your old usage will still work, though)<\/p>","1.6.3":"
Trivial update: noted compatibility through WP 3.4+; explicitly stated license<\/p>","1.6.2":"
Trivial update: noted compatibility through WP 3.3+ and updated copyright date<\/p>","1.6.1":"
Trivial update: noted compatibility through WP 3.2+ and updated copyright date<\/p>","1.6":"
Minor update. Highlights: adds 'rel=' attribute to links; minor tweaks; verified WP 3.0 compatibility.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":"12"},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":972962,"resolution":"128x128","location":"assets","locale":""}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":831764,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0","1.5","1.6","1.6.1","1.6.2","1.6.3","2.0","2.5","2.5.1","2.5.2","2.6","2.6.1","3.0","3.0.1","3.0.2"],"block_files":[],"assets_screenshots":[],"screenshots":[],"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[175,1753,3980,166,3981],"plugin_category":[43],"plugin_contributors":[78189],"plugin_business_model":[],"class_list":["post-5693","plugin","type-plugin","status-publish","hentry","plugin_tags-links","plugin_tags-navigation","plugin_tags-next","plugin_tags-posts","plugin_tags-previous","plugin_category-customization","plugin_contributors-coffee2code","plugin_committers-coffee2code"],"banners":{"banner":"https:\/\/ps.w.org\/loop-post-navigation-links\/assets\/banner-772x250.png?rev=831764","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/loop-post-navigation-links\/assets\/icon-128x128.png?rev=972962","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n
This plugin provides two template tags for use in single.php to create a post navigation loop, whereby previous to the first post is the last post, and after the last post is first post. Basically, when you're on the last post and you click to go to the next post, the link takes you to the first post. Likewise, if you're on the first post and click to go to the previous post, the link takes you to the last post.<\/p>\n\n
The function The function Useful for providing a looping link of posts, such as for a portfolio, or to continually present pertinent posts for visitors to continue reading.<\/p>\n\n If you are interested in getting the post itself and not just a link to the post, you can use the Links: Plugin Homepage<\/a> | Plugin Directory Page<\/a> | GitHub<\/a> | Author Homepage<\/a><\/p>\n\n The plugin provides four template tags for use in your single-post theme templates.<\/p>\n\n The plugin is further customizable via eleven hooks. Typically, code making use of hooks should ideally be put into a mu-plugin, a site-specific plugin (which is beyond the scope of this readme to explain), or in theme template files. Many of these filters are likely only of interest to advanced users able to code.<\/p>\n\n c2c_previous_or_loop_post_link_output, c2c_next_or_loop_post_link_output (filters)<\/strong><\/p>\n\n The 'c2c_previous_or_loop_post_link_output' and 'c2c_next_or_loop_post_link_output' filters allow you to customize the link markup generated for previous and next looping links, respectively.<\/p>\n\n Arguments:<\/p>\n\n Example:<\/p>\n\n c2c_previous_or_loop_post_link_get, c2c_next_or_loop_post_link_get (filters)<\/strong><\/p>\n\n The 'c2c_previous_or_loop_post_link_get' and 'c2c_next_or_loop_post_link_get' filters allow you to customize the link markups generated for previous and next looping links, respectively, but in the non-echoing functions.<\/p>\n\n Arguments:<\/p>\n\n c2c_previous_or_loop_post_link, c2c_next_or_loop_post_link, c2c_get_previous_or_loop_post_link, c2c_get_next_or_loop_post_link, c2c_get_adjacent_or_loop_post, c2c_get_previous_or_loop_post, c2c_get_previous_or_loop_post (actions)<\/strong><\/p>\n\n The 'c2c_previous_or_loop_post_link' and 'c2c_next_or_loop_post_link' actions allow you to use an alternative approach to safely invoke Arguments:<\/p>\n\n Example:<\/p>\n\n Instead of:<\/p>\n\n Do:<\/p>\n\n Highlights:<\/p>\n\n This minor update has some minor tweaks that should go unnoticed, restructures unit test file structure, adds a TODO.md file, and notes compatibility through WP 5.5+.<\/p>\n\n Details:<\/p>\n\n Highlights:<\/p>\n\n Details:<\/p>\n\nc2c_next_or_loop_post_link()<\/code> is identical to WordPress's next_post_link()<\/code> in every way except when called on the last post in the navigation sequence, in which case it links back to the first post in the navigation sequence.<\/p>\n\nc2c_previous_or_loop_post_link()<\/code> is identical to WordPress's previous_post_link()<\/code> in every way except when called on the first post in the navigation sequence, in which case it links back to the last post in the navigation sequence.<\/p>\n\nc2c_get_next_or_loop_post()<\/code> and c2c_get_previous_or_loop_post()<\/code> functions. If you just want the URL to the post, you can use c2c_get_next_or_loop_post_url()<\/code> and c2c_get_previous_or_loop_post_url()<\/code>.<\/p>\n\nTemplate Tags<\/h3>\n\n
Functions<\/h4>\n\n
\n
function c2c_next_or_loop_post_link( $format='%link »', $link='%title', $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nLike WordPress's next_post_link()<\/code>, this function displays a link to the next chronological post (among all published posts, those in the same category, or those not in certain categories). Unlink next_post_link()<\/code>, when on the last post in the sequence this function will link back to the first post in the sequence, creating a circular loop.<\/p><\/li>\nfunction c2c_get_next_or_loop_post_link( $format='%link »', $link='%title', $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nLike `c2c_next_or_loop_post_link(), but returns the value without echoing it.<\/p><\/li>\nfunction c2c_previous_or_loop_post_link( $format='« %link', $link='%title', $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nLike WordPress's previous_post_link()<\/code>, this function displays a link to the previous chronological post (among all published posts, those in the same category, or those not in certain categories). Unlink previous_post_link()<\/code>, when on the first post in the sequence this function will link to the last post in the sequence, creating a circular loop.<\/p><\/li>\nfunction c2c_get_previous_or_loop_post_link( $format='« %link', $link='%title', $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nLike `c2c_get_previous_or_loop_post_link(), but returns the value without echoing it.<\/p><\/li>\nfunction c2c_get_next_or_loop_post( $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nLike WordPress's get_adjacent_post()<\/code> when used to find the next post, except when on the last post in the sequence this function will return the first post in the sequence, creating a circular loop.<\/p><\/li>\nfunction c2c_get_previous_or_loop_post( $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nLike WordPress's get_adjacent_post()<\/code> when used to find the previous post, except when on the first post in the sequence this function will return the last post in the sequence, creating a circular loop.<\/p><\/li>\nfunction c2c_get_next_or_loop_post_url( $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nReturns the URL for the next post or the post at the beginning of the series.<\/p><\/li>\nfunction c2c_get_previous_or_loop_post_url( $in_same_term = false, $excluded_terms = '', $taxonomy = 'category' )<\/code>\nReturns the URL for the previous post or the post at the end of the series.<\/p><\/li>\n<\/ul>\n\nArguments<\/h4>\n\n
\n
$format<\/code>\n(optional) A percent-substitution string indicating the format of the entire output string. Use %link<\/code> to represent the next\/previous post being linked, or %title<\/code> to represent the title of the next\/previous post.<\/p><\/li>\n$link<\/code>\n(optional) A percent-substitution string indicating the format of the link itself that gets created for the next\/previous post. Use %link<\/code> to represent the next\/previous post being linked, or %title<\/code> to represent the title of the next\/previous post.<\/p><\/li>\n$in_same_term<\/code>\n(optional) A boolean value (either true or false) indicating if the next\/previous post should be in the current post's same taxonomy term.<\/p><\/li>\n$excluded_terms<\/code>\n(optional) An array or comma-separated string of category or term IDs to which posts cannot belong.<\/p><\/li>\n$taxonomy<\/code>\n(optional) Taxonomy, if $in_same_term is true. Default 'category'.<\/p><\/li>\n<\/ul>\n\nExamples<\/h3>\n\n
<div class=\"loop-navigation\">\n <div class=\"alignleft\"><?php c2c_previous_or_loop_post_link(); ?><\/div>\n <div class=\"alignright\"><?php c2c_next_or_loop_post_link(); ?><\/div>\n<\/div><h3>Hooks<\/h3>\n<\/code><\/pre>\n\n\n
<?php\n \/\/ Prepend \"Prev:\" to previous link markup.\n function my_custom_previous_or_loop_link_output( $output, $format, $link, $post, $in_same_term, $excluded_terms, $taxonomy ) {\n return 'Prev: ' . $output;\n }\n add_filter( 'c2c_previous_or_loop_post_link_output', 'my_custom_previous_or_loop_link_output', 10, 4 );\n ?>\n<\/code><\/pre>\n\n\n
c2c_previous_or_loop_post_link()<\/code> and c2c_next_or_loop_post_link()<\/code>, respectively, in such a way that if the plugin were deactivated or deleted, then your calls to the functions won't cause errors in your site. The 'c2c_get_previous_or_loop_post_link' and 'c2c_get_next_or_loop_post_link' filters do the same for the non-echoing c2c_previous_or_loop_post_link()<\/code> and c2c_next_or_loop_post_link()<\/code>.<\/p>\n\n\n
c2c_previous_or_loop_post_link()<\/code> and c2c_next_or_loop_post_link()<\/code><\/li>\n<\/ul>\n\n<?php c2c_previous_or_loop_post_link( '<span class=\"prev-or-loop-link\">« %link<\/span>' ); ?>\n<\/code><\/pre>\n\n<?php do_action( 'c2c_previous_or_loop_post_link', '<span class=\"prev-or-loop-link\">« %link<\/span>' ); ?>\n<\/code><\/pre>\n\n\n\n
wp-content\/plugins\/<\/code>).<\/li>\nc2c_next_or_loop_post_link()<\/code> template tag instead of next_post_link()<\/code>, and\/or c2c_previous_or_loop_post_link()<\/code> template tag instead of previous_post_link()<\/code>, in your single-post template (e.g. single.php).<\/li>\n<\/ol>\n\n\n3.0.2 (2020-08-26)<\/h4>\n\n
\n
\n
phpunit\/<\/code> to house all files related to unit testing<\/li>\nbin\/<\/code> to phpunit\/bin\/<\/code><\/li>\ntests\/bootstrap.php<\/code> to phpunit\/<\/code><\/li>\ntests\/<\/code> to phpunit\/tests\/<\/code><\/li>\nphpunit.xml<\/code> to phpunit.xml.dist<\/code> per best practices<\/li>\n<\/ul><\/li>\n\n
modify_nextprevious_post_where()<\/code><\/li>\n<\/ul><\/li>\n<\/ul>\n\n3.0.1 (2020-05-10)<\/h4>\n\n
\n
3.0 (2020-01-28)<\/h4>\n\n
\n
c2c_{$adjacent}_or_loop_post_link_output<\/code> filter. This change won't affect you unless you have custom code making use of the filter, which is unlikely for almost all users.<\/li>\n<\/ul>\n\n\n
c2c_get_next_or_loop_post_url()<\/code> and c2c_get_previous_or_loop_post_url()<\/code> to get URL of adjacent\/looped post<\/li>\n$previous<\/code> and remove argument $post<\/code> from c2c_{$adjacent}_or_loop_post_link_output<\/code> hook invocation<\/li>\n$adjacent<\/code> argument to a number of filters, to sync with WP core\n\n\n
{$adjacent}_post_link<\/code>, {$adjacent}_or_loop_post_link<\/code>, c2c_{$adjacent}_or_loop_post_link_get<\/code>, and c2c_{$adjacent}_or_loop_post_link_output<\/code><\/li>\n<\/ul><\/li>\nc2c_get_adjacent_or_loop_post()<\/code> to obtain post, rather than duplicating its functionality in c2c_get_adjacent_or_loop_post_link()<\/code><\/li>\nc2c_adjacent_or_loop_post_link()<\/code><\/li>\napply_filters_deprecated()<\/code> to formally deprecate the {$adjacent}_or_loop_post_link<\/code> filter<\/li>\nload_textdomain()<\/code> and just load the textdomain within init()<\/code><\/li>\n\n
expected()<\/code> to optionally not include arrow quotes<\/li>\n$posts<\/code> as being static since it's never referenced as if it was<\/li>\nmodify_nextprevious_post_where()<\/code><\/li>\necho<\/code> in code example<\/li>\n