PHP download

Download the PHP package danlapteacru/wp-patterns-debug without Composer

On this page you can find all versions of the php package danlapteacru/wp-patterns-debug. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download danlapteacru/wp-patterns-debug
More information about danlapteacru/wp-patterns-debug
Files in danlapteacru/wp-patterns-debug

Vendor danlapteacru
Package wp-patterns-debug
Short Description Pattern registry browser and block/pattern debug panel for the WordPress block editor.
License GPL-2.0-or-later
Homepage https://github.com/danlapteacru/wp-patterns-debug

Keywords debug wordpress blocks patterns wordpress-plugin gutenberg block-editor

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.

Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
To use Composer is sometimes complicated. Especially for beginners.
Composer needs much resources. Sometimes they are not available on a simple webspace.
If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.

Please rate this library. Is it a good library?

Example code of danlapteacru/wp-patterns-debug

Informations about the package wp-patterns-debug

Patterns Debug

Adds two debugging surfaces to the WordPress block editor (post editor and site editor):

Pattern browser

A pinnable Patterns Debug sidebar with a Selected block debug panel on top, followed by a browser listing every pattern the editor knows about:

Registered patterns from the client stores (core, theme, plugin, pattern directory), plus user patterns (wp_block posts) with their sync status.
Search plus source and category filters.
Per pattern: metadata (source, categories, block types, sync status, inserter visibility), a recursive block-usage count, copy name/content, a JSON dump, and a live BlockPreview.
A Server registry section backed by a REST endpoint (wp-patterns-debug/v1/registry) that dumps the raw server-side WP_Block_Patterns_Registry and category registry — including patterns hidden from the inserter — exactly as PHP registered them.

Block debug panel

A Debug panel in the block inspector for the selected block, and the same panel as Selected block in the plugin sidebar. The sidebar copy matters: the block inspector renders no panels at all for synced pattern instances (core/block), so the sidebar is the only place they can be debugged.

Overview (name, client ID) with copy actions.
Dumps: block instance, block type, the wrapper element's rendered DOM attributes, serialized block HTML.
Attributes editor: the block's attributes as raw, validated JSON. Apply/reset; deleting a key removes the attribute; keys outside the block type's attribute schema are flagged but allowed.
Pattern provenance: shows when the selected block is a synced pattern instance (core/block ref, wp_block record, per-instance overrides) or was inserted from a pattern (metadata.patternName), with dumps of the source pattern.

Screenshots

Debug panel in the block inspector — overview, dumps, serialized HTML, and the raw JSON attributes editor:

Debug panel in the block inspector

Dump modals — pretty-printed, copyable dumps of the block instance, block type, or wrapper element:

Dump modal showing the block instance

Pattern browser — search and filter every registered and user pattern, with metadata, block counts, and live previews:

Pattern browser with search and live preview

Synced pattern provenance — the sidebar's Selected block panel debugging a core/block instance (the block inspector renders no panels for these):

Selected block panel showing synced pattern provenance

Server registry — the raw server-side pattern registry, dumped over REST, including patterns hidden from the inserter:

Server registry dump modal

Installation

Via Composer:

Or clone/download into wp-content/plugins/wp-patterns-debug — built assets are committed, so no build step is needed.

Requirements

WordPress 6.6+ (unified @wordpress/editor plugin APIs, react-jsx-runtime).
PHP 8.1+.

Access control

All debug surfaces (assets and the REST endpoint) require the view_patterns_debug capability, mapped to edit_posts by default. Remap it by filtering map_meta_cap at a priority above 0:

Development

The plugin loads vendor/autoload.php when present but does not require Composer; a minimal PSR-4 autoloader covers src/.

License

GPL-2.0-or-later

All versions of wp-patterns-debug with dependencies

PHP Build Version

Package Version

Version v0.1.1 Release 29. Jul 2026
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of wp-patterns-debug from vendor danlapteacru

Requires php Version >=8.1
composer/installers Version ^1.0 || ^2.0

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package danlapteacru/wp-patterns-debug contains the following files

Loading the files please wait ...