EditRail 1.0.4

Keyboard users can now insert a tool's block. Nothing about saved content changes.

New in 1.0.4

• Insert with the keyboard. Arm a tool with Enter, then press Ctrl+Enter (Cmd+Enter on a Mac), on the toolbar or in the canvas. The block goes after the selected block, or at the end of the post when no block is selected. Before, only a click in the canvas inserted the block, so an armed tool was a dead end for keyboard and screen-reader users.
• A selected empty paragraph is replaced, the same as with the block inserter.
• Ctrl+Shift+Enter keeps the tool armed for more inserts. Enter on the armed tool still disarms it, and Escape still returns the toolbar to Select.
• The new block is selected, and screen readers announce the insert. When no block around the selection accepts the block, a notice says so and the tool stays armed.
• The help panel and the readme describe the keyboard insert.

Fixed in 1.0.4

• After you arm a tool in a flyout with the keyboard, focus goes back to the toolbar button that opened the flyout. Before, focus moved to the page body.
• A press on that button now disarms the tool. Before, the press armed the button's own tool instead, with no announcement, and the button stayed pressed.

For developers

• Tools that use insertBlock or createBlock get the keyboard insert with no change to the extension API.
• The test suites save the test account's toolbar settings in one file per account and site. A second test run on the same account stops at login instead of overwriting the first run's saved settings. Run one suite at a time on one account. See docs/releasing.md.

Install

From WordPress.org: search for "EditRail" under Plugins, Add New. Or download editrail.zip from this release and upload it under Plugins, Add New, Upload Plugin.

Requires WordPress 6.5 or later and PHP 7.4 or later. Tested up to WordPress 7.1.

EditRail 1.0.3

Fixes from a follow-up QA pass. No new features for authors, and nothing about saved content changes.

Fixed in 1.0.3

• Section overview: when a section's box is too narrow to hold the reorder controls, the controls now sit beside or above the box instead of over the next section. On a theme that sizes a short paragraph to its text, the controls covered the next section and you could not click it.
• Section overview: in a group selection, the reorder controls stay on top of the other selected sections. Before, a selected section lower on the page could cover the arrows, and a click picked that section and cleared the group.
• After you click a tool, Tab leaves the toolbar. Before, Tab could stop on another toolbar button, such as Toolbar settings. The toolbar's one Tab stop now follows focus, for a mouse click and for a screen reader that moves focus to a tool.

For developers

• window.toolrail.refresh() repaints the pressed state of every tool. Call it when your tool's isActive() result changes for a reason the editor's data stores do not see, such as a pick mode you cancel yourself. Before, such a tool stayed pressed until an unrelated edit repainted the toolbar.
• The e2e and screen-reader test suites save the test account's own toolbar settings when they log in, and restore them when the run ends. Before, a run could leave the account with no pinned tools.
• Test and screenshot logins default to the local wp-env site, http://localhost:8888. A .env file sets your own site. A plain http:// URL for a site that is not local stops the login before the password is sent. See docs/releasing.md.
• The repository has issue and pull request templates.

Install

From WordPress.org: search for "EditRail" under Plugins, Add New. Or download editrail.zip from this release and upload it under Plugins, Add New, Upload Plugin.

Requires WordPress 6.5 or later and PHP 7.4 or later. Tested up to WordPress 7.1.

EditRail 1.0.2

Fixes from a keyboard and screen-reader QA pass with NVDA. No new features, and nothing about saved content changes.

Fixed in 1.0.2

• Escape returns the toolbar to Select from anywhere in the editor, not only from inside the canvas, and the change is announced. A second press on an armed tool also disarms it.
• Toolbar settings: Pinned tools and the Add a block or pattern search now come first. From the search field, Tab reaches the Toolbar position, Tool names and Appearance groups before it leaves the dialog. A click into the canvas closes the dialog, the help panel and the flyouts.
• Pin, Unpin, Move up, Move down, Save set and Delete announce their outcome to screen readers. Enter in the set name field saves the set, and an empty name says so.
• An armed click on the post title inserts at the top of the document. An armed click inside an empty Group inserts inside it.
• A tool's tooltip is its name, or its name and your description. Screen readers no longer hear a how-to sentence on every tool; the help panel explains inserting.
• Section overview: Tab stays inside the overview while it is open, instead of leaving the page.

For developers

• npm run test:sr runs NVDA screen-reader journeys through the toolbar, Toolbar settings, the Section overview and the help panel with Guidepup in a headed Firefox. Windows only, not part of npm test. See docs/releasing.md.

Install

From WordPress.org: search for "EditRail" under Plugins, Add New. Or download editrail.zip from this release and upload it under Plugins, Add New, Upload Plugin.

Requires WordPress 6.5 or later and PHP 7.4 or later. Tested up to WordPress 7.1.1.

EditRail 1.0.1

The first release of EditRail on WordPress.org, and the first GitHub Release of this repository.

EditRail is a graphics-editor-style toolbar for the WordPress block editor. Select a tool, then click or drag in the canvas where the block should go. Pin any block or pattern to the toolbar: core blocks, theme blocks, plugin blocks, your own patterns. Everything it inserts is saved the way that block is always saved, so a post never depends on the plugin.

New in 1.0.1

• The plugin is renamed to EditRail. The slug, the main file and the text domain are now editrail. The toolrail_ prefix, the window.toolrail API, the toolrail_tool_providers filter and the stored preferences keep their names, so pinned tools, saved sets and extensions are not affected.
• Edit a pinned tool's name, description and icon. An Edit button beside each tool in Toolbar settings opens an inline form. The icon is up to three characters, or any Dashicon from a searchable list. Saved sets keep these labels and carry them in set files.
• Extensions can store their own data on a pinned tool with window.toolrail.setPinData() and getPinData(). The data is removed with the tool when it is unpinned, and travels in saved sets.
• A WordPress Playground blueprint for the WordPress.org Live Preview. It installs Typography Stylist, pins its block with a custom name, and opens a demo post set in EB Garamond.

Upgrading from a 1.0.0 zip

The plugin folder and main file changed from toolrail/toolrail.php to editrail/editrail.php. A zip upgrade installs a second folder. Activate EditRail, then delete the old toolrail folder so two copies do not load. Pinned tools and saved sets are kept.

Install

From WordPress.org: search for "EditRail" under Plugins, Add New. Or download editrail.zip from this release and upload it under Plugins, Add New, Upload Plugin.

Requires WordPress 6.5 or later and PHP 7.4 or later.