PAGESCALE
PageScale compatibility with REEID Translate
PageScale compatibility with REEID Translate is being reviewed using official plugin documentation. Replaces the default WordPress list screen with a custom admin interface for managing large numbers of pages/CPT entries. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What PageScale does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
PageScale is documented in the Performance category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How PageScale compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Replaces the default WordPress list screen with a custom admin interface for managing large numbers of pages/CPT entries.
- Uses keyset (cursor) pagination instead of OFFSET pagination to keep result-page loading cost constant at large row counts.
- Implements lazy hierarchy loading for hierarchical post types (only queries children of expanded nodes; tree does not load the whole site at once).
- Implements tiered search: numeric input routes to primary key; slugs use indexed equality/prefix lookup; title/content/custom-field search uses MySQL InnoDB FULLTEXT (MATCH …
- AGAINST) rather than leading-wildcard LIKE.
- Uses virtual scrolling to keep the DOM bounded (about 50 rows) regardless of dataset size.
- Caches aggregates (totals, parents list, duplicate reports) using the WordPress Transients API, keyed per post type.
- Builds/creates required database indexes lazily (records pending indexes on activation; builds them one-at-a-time on later admin loads or via WP-CLI), and falls back to a basic bounded search mode until FULLTEXT indexes exist.
TRANSLATION BOUNDARY
PageScale capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
PageScale and REEID Translate FAQ.
What does PageScale do?
PageScale has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does PageScale have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from PageScale?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate PageScale in a multilingual WordPress workflow.
REEID documents PageScale functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.