WP-PAGENAVI
WP-PageNavi translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WP-PageNavi does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Generates pagination links through the `wp_pagenavi()` template tag.
- Replaces the default `next_posts_link()` and `previous_posts_link()` navigation in themes.
- Supports multipart page navigation with `wp_pagenavi( array( 'type' => 'multipart' ) )`.
- Provides a settings page under WordPress admin for changing wording and the number of page links.
- Allows copying the plugin stylesheet into a theme for custom styling, or disabling the plugin CSS and styling in the theme directly.
- Exposes filters for changing the default class names assigned to page navigation elements.
- Supports secondary `WP_Query` instances.
- Allows navigation text settings to include inline SVG elements and other content permitted by `wp_kses_post()`.
Distinctive features
Pagination-focused navigation replacement with configurable page-link wording and counts, multipart page navigation support, theme-level styling control, and filterable class names for navigation elements.
Dynamic content
Dynamic pagination content is supported through generated page links and multipart page navigation. Support is explicitly shown for secondary `WP_Query` instances. No broader runtime content behavior is established by the supplied evidence.
SEO and metadata
The supplied evidence does not establish SEO metadata generation or metadata management behavior. It does show use of WordPress core aria-label strings for navigation labels.
URLs and navigation
The plugin outputs pagination URLs with `esc_url()` and provides navigation links through `wp_pagenavi()`. It is described as replacing default next/previous posts navigation in themes. No broader URL routing or page discovery behavior is established.
Forms and commerce
No forms or commerce behavior is established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WP-PageNavi does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- Works with pagination/navigation output exposed through the plugin’s template tag and related theme navigation hooks. The supplied evidence does not establish support for other content types, translation behavior, or broader site features. Styling can be handled by copying the plugin stylesheet into a theme or by disabling the plugin CSS and styling in the theme directly.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.