Repository navigation
FAQ English
No. Activate the plugin and open a content list that an active supported builder can edit. Views, the Builder column and builder submenus are enabled by default.
WordPress 6.7+ and PHP 8.1+. Checked on WordPress 6.7 and 7.1.3 with PHP 8.4.5 using isolated SQLite installations; PHP 8.1.29 workflow checks also passed. MySQL/MariaDB, FTP/SSH and broader real-builder combinations need separate checks.
Yes. GPL v2 or later. Some supported builders require their own paid license.
Elementor, Bricks, Breakdance, Oxygen 6+, Oxygen Classic, Brizy, Beaver Builder, ZionBuilder, Thrive Architect, Pagelayer and Visual Composer. Visual Composer currently uses the free edition’s page/post scope.
The builder must be active, allow the current post type, and provide recognized settings. Your user also needs editing access to that type. Invalid, missing and hidden post types are excluded.
Yes, where an active builder allows them and the post type has an admin interface. Attachments are excluded.
It shows matching metadata for active supported builders allowed on that post type. It is not a full analysis of frontend rendering or template assignments.
Yes. Each matching builder is shown; old metadata can remain after a migration. Builder groups may overlap and their counts cannot simply be added.
No configured condition matched among active supported builders enabled for this post type. It does not prove the page uses Gutenberg.
The default views recognize active builders only. Open Builder tools and personal views → Check inactive builder traces for an explicit read-only audit of known inactive signatures. It does not prove frontend rendering.
No. Recognition is based on the page’s own metadata, not on global templates or theme-builder conditions.
These integrations retain the existing metadata-existence rule. An empty stored value still counts as present; it is not a content-quality check.
Select a builder, then search the list or use its normal filters. The builder ID is carried in the native list form. All or another standard view resets the builder selection.
The badges count readable published, future, draft, pending and private content, according to registered admin statuses. Trash and auto-drafts are excluded. Users unable to edit other authors’ content receive counts for their own content.
Badges describe the complete readable builder group outside trash. Search, date, author and other list constraints can reduce the rows currently shown.
Existing meta query groups are kept and combined with the selected builder using AND. The no-builder filter adds its exclusion separately. Third-party query hooks can still affect results.
Users with manage_options, normally administrators. Content filtering uses each post type’s own editing permissions.
Yes, when they can edit the corresponding post type. They do not need edit_theme_options.
Yes, individually in Screen Options on the list, or site-wide in Settings → Builder List Pages.
Yes, site-wide in Settings → Builder List Pages. Builder views above the list remain available.
The three plugin switches apply to the current site. WordPress Screen Options provide each user’s separate column visibility.
The three display choices are stored separately for each site. Network activation loads the plugin on all sites, including newly created sites. The Library uses its own site and network controls; site administrators cannot manage its network preferences.
The bundled deckerweb GitHub Updater V2 checks public stable releases and integrates with the regular WordPress update screens. No separate updater plugin is required. The updater does not enable automatic updates.
No. The updater offers stable GitHub releases only. Install test packages manually when needed. It does not turn on automatic updates.
An embedded discovery and installation catalog under Plugins → Add New → deckerweb. The standard WordPress tab remains the default. Library visibility and online catalog preferences have their own settings.
No. Installation requires an explicit action, capabilities and nonce checks. The embedded catalog is local; optional online catalog refresh must be enabled separately.
No. A fresh installation never replaces an existing directory. Updates use the separate update action, check the offered version and requirements, and never offer a downgrade.
Builder List Pages contains no usage telemetry. GitHub update checks contact GitHub; optional catalog requests contact the configured approved endpoint. Servers see the requesting IP. Clicking Install downloads the selected release.
Use the installable plugin ZIP. Older releases supplied a separate snippet with a smaller feature set. Do not activate a legacy snippet alongside the plugin; the plugin main file is not a standalone snippet.
No. It reads builder metadata and filters admin lists. No conversion, builder cleanup or frontend assets are included.
The current plugin, its Update URI integration and its embedded Library have not been tested on ClassicPress. Earlier compatibility statements do not establish support for this build.
Include plugin and builder versions, post type, user role, selected filter and expected result. Use a test copy and avoid sharing private page content or credentials.
WP Admin Cleaner 2.0.1 matches hidden menu entries against the end of the URL. Hiding the Bricks Getting Started menu makes its bricks slug also match edit.php?post_type=page&builder=bricks. Builder List Pages automatically appends &blp_view=1 to its list URLs while retaining search and filters. The hidden Bricks screen stays blocked, and Admin Cleaner can remain active.
Deactivation keeps all data. Uninstallation removes this plugin’s temporary update cache while keeping its three site settings, personal views/display preferences and all builder content. Shared Library caches and tasks are removed only when no other installed host needs them, including inactive hosts. Library preferences remain unless its separate cleanup option is enabled. Plugins installed through the Library are never removed.
In your user metadata with a separate key for each site. Other users do not receive your favorites. Deactivation and uninstall retain them; delete a favorite from the tools panel.
Only that a known metadata signature is present. It can be historical or empty and does not prove frontend rendering. The audit never changes content.
Title, status, builder labels and native edit link for the builder/status/search selection, limited to 5,000 readable and editable items. Other list filters are excluded and formulas are neutralized.
Builder List Pages · Documentation / Dokumentation
Wiki home / Wiki-Startseite · Repository · Downloads & Releases
Help & bugs / Hilfe & Fehler · Discussions / Austausch · Security / Sicherheit
© 2019–2026 David Decker – DECKERWEB.
Plugin: GPL v2 or later / GPL v2 oder höher.