Description
PageScale replaces the default WordPress Pages screen with an admin interface built to stay fast on sites that have tens of thousands (or millions) of pages. The stock list table slows down at that scale because it relies on OFFSET pagination and unindexed queries. PageScale takes a different approach at every layer.
How it stays fast
- Keyset (cursor) pagination instead of OFFSET, so the cost of loading any page of results is constant whether you have 10,000 rows or 1,000,000.
- Lazy hierarchy: only the children of a node you actually expand are queried. The tree never loads the whole site at once.
- Tiered search: numeric input goes straight to the primary key, slugs use an indexed equality/prefix lookup, and title/content/custom-field search uses InnoDB FULLTEXT (MATCH … AGAINST) rather than a leading-wildcard LIKE. Content and custom-field search is optional via a UI toggle and runs entirely in MySQL, so post content is never loaded into PHP memory.
- Virtual scrolling keeps the DOM bounded (about 50 rows) at any dataset size.
- Cached aggregates: totals, the parents list and duplicate reports are cached with the Transients API.
Other features
- Elementor-aware quick actions.
- Bulk actions, chunked client-side so large operations don’t time out.
- Duplicate finder for titles, exact slugs and similar slugs.
- CSV export of the current view or a selection.
- WP-CLI command to build the search indexes on demand.
Indexing is safe on large tables
PageScale never runs a long ALTER TABLE during activation. Instead it records that indexes are pending and builds them lazily, one at a time, on later admin loads (or immediately via WP-CLI). The plugin is fully usable while indexing is in progress, and search simply runs in a basic mode until the FULLTEXT indexes exist.
Screenshots
Installation
- Upload the
pagescalefolder to/wp-content/plugins/, or install the plugin through the Plugins screen in WordPress. - Activate the plugin through the Plugins screen.
- Open Pages > Scalable Manager in the admin menu.
- On large sites, optionally run
wp pgscl build-indexesvia WP-CLI to build the search indexes immediately instead of waiting for them to build in the background.
FAQ
-
Does this add database indexes to my site?
-
Yes. It adds a small number of composite and FULLTEXT indexes to wp_posts and wp_postmeta to make search and sorting fast. They are created lazily, one per request, so activation is instant and no request runs long enough to time out.
-
Does it work without the indexes?
-
Yes. Until the indexes finish building, search falls back to a bounded, basic mode. Everything else works normally.
-
Which capability is required?
-
Managing pages requires the edit_pages capability, checked on every REST route. Private pages are only shown to users who can read them, and per-page edit and delete actions are checked individually.
-
Does it modify my content?
-
No. Read operations never load post content into PHP. Edit and bulk actions use standard WordPress functions and respect per-page capabilities.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“PageScale” is open source software. The following people have contributed to this plugin.
Contributors
Translate “PageScale” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.5.1
- Security: apply private-page readability filtering to the /parents, /export and /default-view REST endpoints so private pages a user cannot read are never exposed, including by direct ID.
- Cache the parents list per user to avoid serving one user’s readable set to another.
1.5.0
- Initial public release: keyset pagination, lazy tree, tiered FULLTEXT search, virtual scrolling.
- Duplicate finder for titles, exact slugs and similar slugs.
- CSV export with formula-injection guarding.
- Lazy, timeout-safe index building with a WP-CLI command.