beaudierman

This plugin adds the rel next and previous meta tags for your paginated pages. Using rel next and previous meta tags will help Google understand your pagination and remove the need for you to noindex anything after the first page.

Pagination Rel Meta

Add rel next and previous tags to paginated pages.

strix-bubol5

This plugin’s page-list has an input box that allows you to directly specify the page number you wish to display.
This plugin has a setting to display page-list in reverse order
You can specify style-sheet and some options at each page.
This plugin has several sample stylesheets by default.
By passing an array of options to the function as arguments on each page, it is possible to change the appearance of multiple linked listings within the same page, except for the style.
It is common to have two linked lists, one at the top of the page and one at the bottom. In such cases, when the function is called a second time, the list created the first time is reused from memory to avoid having the same process performed twice.
This plugin has a custom block for Gutenberg Block Editor.
Even if you don’t know much html or php, this plugin has the ability to insert linked list at the beginning and end of an html element using Javascript by specifying the ID of the html element where you want to display it. 
Furthermore, if you have no idea about the ID of html elements, etc., go into the plugin’s options settings page and try typing “search” in the “Page-lists outputted by javascript” field. When the page is displayed, the plugin uses javascript to find the html elements of the main content, and if it is lucky enough to find it, it will use Javascript to insert a page-lists at the beginning and end of that HTML element. Perhaps it might work.
<h3>Arbitrary section 1</h3>
Explanation of errors detected by the plugin “Plugin Check (PCP)” 
*file： \simplistic-page-navi\simplistic_pagenavi.php
1:881行 ERROR WordPress.Security.EscapeOutput.OutputNotEscaped All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found ‘$ret’.
＞This variable $ret contains the assembled pagination and is pointed out as not being escaped in the final output. The option values ​​set by the user are sanitized when saved and are also sanitized individually when actually used. The tags that are incorporated into the pagination are only pre-defined ones, and I understand that there is no need to escape the final assembly..
2:410行 WARNING WordPress.Security.NonceVerification.Recommended Processing form data without nonce verification.
＞This is a function that gets the parameters (query) of the accessed URL. Because it only gets values ​​that exist in public_query_vars set by WordPress, I think that nonce verification is not necessary.
3:860行 ERROR WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: “$simplistic_page_navi_start”.
4:888行 ERROR WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedFunctionFound Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: “direct_splcpn_style”.
＞The plugin is encapsulated in a class, but these variables and functions are outside of that class. I could add a prefix as instructed, but I’ve left it as it is because it might already be in use.。
5:The plugin is encapsulated by a class, and for most of the variables in the files included by the methods in that class, an error occurs saying “Because it is a global variable, you must add a prefix.”。
＞However, since these variables are used within methods inside a class, they cannot possibly be global. I believe this is a false positive that undermines reliability. It’s annoying, so I’m handling it with “// phpcs:ignoreFile”.。

Simplistic page navi

This plugin displays a linked list by page number. It is simple but has several features.

Pagination Rel Meta vs Simplistic page navi