JPKCom DB
View on GitHub (opens in a new tab)

JPKCom Enable Block Editor — Guide & Tips

Enable the Block Editor specifically for the admin (user ID 1) — JPKCom Enable Block Editor as a Blockstudio companion: installation, requirements and tips.

JPKCom Enable Block Editor enables the Block Editor (Gutenberg) specifically for the admin with user ID 1. The plugin complements Blockstudio and uses its users filter.

Guide

Requirements

  • WordPress 6.9 or newer (tested up to WordPress 7.1)
  • PHP 8.3 or newer
  • Blockstudio (opens in a new tab) must be installed and active (Requires Plugins: blockstudio)

Installation

  1. In your admin panel, go to Plugins → Add New and click Upload Plugin.
  2. Choose the plugin's ZIP file and click Install Now.
  3. Make sure the Blockstudio plugin is active.
  4. Click Activate.

How it works

Once active, the plugin enables the Block Editor for the admin with user ID 1. It does so via the Blockstudio users filter — see the Blockstudio documentation on users settings (opens in a new tab) for details.

Tips & Tricks

  • Targeted at a single account: The plugin specifically addresses user ID 1 (the first admin account). This lets you enable the Block Editor for that account while Blockstudio governs the rest of the editor experience.
  • Mind the order: Blockstudio must be active for the plugin to take effect (hence Requires Plugins: blockstudio).
  • Reproducible updates: Since version 2.0.3 the plugin uses secure self-hosted updates via GitHub with SHA256 checksums and runs with declare(strict_types=1). Since 2.0.9 it also carries the Update URI header: the wordpress.org update API then no longer returns updates for this plugin, so a plugin published there under the same slug cannot pose as an update. Since 2.0.10 Dashboard → Updates shows the JPKCom logo as the plugin icon. Since 2.0.11 (updater 1.5.0) the plugin gets updates with icon, "View details" and the same SHA-256 check even while it is deactivated — provided another JPKCom plugin with updater 1.5.0 or later is active (on multisite network-active or on the main site), because WordPress never runs a deactivated plugin's code. JPKCom download URLs are no longer kept in the stored update list, the checksum also covers packages another plugin supplies and every GitHub address of the release file; the updater fetches update info only for accounts that may update plugins, in the update cron and in WP-CLI, never for anonymous visitors. If the plugin sits in a Git checkout or a renamed folder, WordPress reports the new version but does not update it; in a renamed folder this only holds while the plugin is active — deactivated, it gets no notice there at all.

Further reading