PageScale
| 开发者 | shahzeb2u |
|---|---|
| 更新时间 | 2026年9月5日 02:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
PageScale replaces the default WordPress list screen with an admin interface built to stay fast on sites that have tens of thousands (or millions) of entries. 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.
As of 1.6.0, PageScale is no longer limited to Pages. You choose which post types it manages from a settings screen. Hierarchical types (like Pages) keep the lazy parent/child tree; non-hierarchical types (like Posts or a Products CPT) get the fast flat list. Pages behaviour is unchanged by default, so existing sites are unaffected until you opt additional types in.
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, keyed per post type.
- Choose which post types to manage from Settings > PageScale.
- Each managed type gets its own Scalable Manager screen under its menu, with a switcher to move between types.
- Hierarchical types show the parent/child tree and a parents panel; non-hierarchical types show a flat list without a Parent column.
- Search, quick edit, bulk actions, duplicate and CSV export all work per type.
- 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.
安装:
- 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.
- To manage other post types, go to Settings > PageScale and tick the types you want.
- 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.
屏幕截图:
常见问题:
Which post types can PageScale manage?
Any public post type shown in the admin. Pages is enabled by default; add others from Settings > PageScale. Internal or configuration post types are rarely worth managing this way, so the choice is left to you rather than enabling everything automatically.
What is the difference between hierarchical and flat types?
Hierarchical types (like Pages) have parent/child relationships and show a tree with a parents panel. Non-hierarchical types (like Posts) show a fast flat list without a Parent column.
Will 1.6.0 change my existing Pages setup?
No. Only Pages is managed by default, exactly as before. Additional post types appear only after you enable them in settings.
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?
Each managed post type is checked against its own edit capability on every REST route (for pages that is edit_pages). Private entries are only shown to users who can read them, and per-item 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-item capabilities.
更新日志:
1.6.0
- New: custom post type support. Choose which post types PageScale manages from a new Settings > PageScale screen.
- New: each managed post type gets its own Scalable Manager screen, with a post-type switcher when more than one type is managed.
- New: automatic tree-vs-flat view. Hierarchical types keep the parent/child tree; non-hierarchical types get the fast flat list.
- Improved: duplicate now inherits the source item's post type and copies that type's taxonomies.
- Improved: total and parents caches are keyed per post type to avoid cross-type stale counts.
- Improved: permission checks validate against each post type's own capabilities.
- Fix: duplicating an Elementor page no longer corrupts its layout (meta is now copied with correct slashing, and per-post builder CSS caches are regenerated for the copy).
- Fix: a duplicated page now gets a unique slug (e.g. privacy-policy-2) while the original page keeps its slug unchanged.
- Fix: quick edit saves are slashed correctly and report a clear error if a page builder hook fails, instead of silently not saving.
- Fix: permanently deleting from trash now verifies the result and recovers when a corrupted builder payload blocks deletion.
- Fix: quick edit and drag-and-drop reparenting now save over POST instead of PATCH, which some hosting stacks (LiteSpeed/ModSecurity) block at the server level, making saves silently fail.
- Fix: the virtual-scroll repaint no longer resets an open quick edit form, which silently discarded typed changes (title, status, terms) before saving.
- Fix: taxonomy term changes in quick edit now save (the capability check used a non-existent capability name and always failed).
- Fix: the Scalable Manager submenu now attaches correctly under the built-in Posts menu.
- Pages behaviour is unchanged by default; existing installs see no difference until additional types are enabled.
- 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.
- 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.