WP-PAGENAVI

WP-PageNavi compatibility with REEID Translate

WP-PageNavi compatibility with REEID Translate is being evaluated from available plugin evidence. Generates pagination links through the `wp_pagenavi()` template tag. No specific visitor-facing translation surface is currently confirmed.

Visit WP-PageNavi ↗

AWAITING VERIFICATION

What the available evidence establishes for WP-PageNavi.

Official plugin information supports the compatibility context documented for this category.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
WP-PageNavi is documented in the Navigation category with 8 concrete capabilities identified in the current evidence.

EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.

COMPATIBILITY REVIEW

How WP-PageNavi compatibility is evaluated

01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.

02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.

03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.

04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.

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.

CONTENT BOUNDARY

WP-PageNavi capabilities and translation scope are documented separately.

The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.

Functional capability alone is not treated as evidence that a value should be translated.

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.

COMMON QUESTIONS

WP-PageNavi and REEID Translate FAQ.

What does WP-PageNavi do according to the available plugin evidence?

WP-PageNavi has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.

Is a REEID translation surface currently confirmed for WP-PageNavi?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for WP-PageNavi?

The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.

RELATED GUIDES

Continue through the compatibility library.

  • Navigation Integrations — Browse documented Navigation integrations and compatibility guides.
  • Menus & UI Strings — Understand multilingual handling for WordPress navigation and interface content.
  • Architecture — Understand how multilingual content is separated from WordPress presentation and functionality.
  • WP-Paginate — Review WP-Paginate compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • WP Widget in Navigation — Review WP Widget in Navigation compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • WP-REST-API V2 Menus — Review WP-REST-API V2 Menus compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • WP Term Order — Review WP Term Order compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • WPB Accordion Menu – Collapsible Vertical Sidebar Responsive Mobile Menu – WooCommerce Category Accordion — Review WPB Accordion Menu compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • WP Store Locator — Review WP Store Locator compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.

INTEGRATION EVIDENCE

Evaluate WP-PageNavi in a multilingual WordPress workflow.

REEID documents WP-PageNavi functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.

Translation scope will be published when concrete visitor-facing content is established by evidence.

Explore REEID Translate
View integrations
Shopping Cart
Scroll to Top