Frontpen – Front-End Editor
| 开发者 | gopalbogati |
|---|---|
| 更新时间 | 2026年7月14日 21:56 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Editable blocks are marked up as they render, using a post-order index that the server reproduces exactly. This means editing works even for blocks nested inside Group, Columns or Cover blocks.
- Classic (non-block) posts work too: each rendered paragraph, heading, list item, table cell or caption is matched back to the identical element in the stored content, and only that element's text is replaced on save. Text nested inside wrappers (such as a paragraph inside a list item, common in exported or AI-generated HTML) is found as well. Elements the server cannot verifiably match — theme or shortcode output, anything containing an image — are left alone rather than risk changing the design.
- Saves go through a dedicated REST endpoint that re-parses and re-serialises the post's blocks server-side, so nothing about the block structure is lost.
- Every save is a standard WordPress revision, so you get a full history and can roll back at any time.
- Inline editing of paragraphs, headings and list items on the live page.
- Classic content support — posts written as plain HTML (classic editor, imported or programmatic content) are just as editable as block posts.
- Block markup preserved — attributes, classes and layout survive every save.
- Native revisions — each edit is a WordPress revision, plus a one-click "Undo last save".
- Autosave a moment after typing stops (configurable, or turn it off).
- Unsaved-changes guard warns before you navigate away with pending edits.
- Edit-mode toolbar — a small floating bar toggles editing on and off, so normal browsing is never disrupted.
- Reliable front-page control — authorized editors get an edit option on normal posts/pages; pages without supported blocks link to the standard WordPress editor instead of failing silently.
- Safe rapid editing — saves are queued to prevent simultaneous block updates from overwriting one another.
- Role and per-user controls — choose which roles may edit, always-allow specific users regardless of role, or block specific users entirely.
- Locking — lock a whole post from the editor screen, or exclude a single block by adding the
frontpen-no-editCSS class. - Security first — every capability, lock and block type is re-checked on the server; the browser is never trusted.
- No build step, no page builder — plain PHP, CSS and JavaScript.
安装:
- Upload the
frontpenfolder to/wp-content/plugins/, or install it from the Plugins screen. - Activate the plugin.
- Go to Settings → Front-End Editor to choose editable block types and allowed roles.
- Visit any post or page you can edit and click Edit page in the floating toolbar.
屏幕截图:
常见问题:
Which blocks can be edited?
Text blocks: paragraphs, headings and list items — both as Gutenberg blocks and as plain HTML elements in classic (non-block) content. In classic content, table cells, figure captions and definition lists are editable too. Layout and media blocks are intentionally left alone so the page structure stays intact.
Can I format text while editing?
Yes — the standard shortcuts work inside an editable region: Ctrl/Cmd+B for bold, Ctrl/Cmd+I for italic, Shift+Enter for a line break. Anything outside the safe inline tag set is stripped on save.
Can visitors see the editor?
No. The editing UI and its markup are only added for logged-in users who are allowed to edit the post.
Why does the button say "Open editor" instead of "Edit page"?
Inline editing works on Gutenberg text blocks and on plain HTML elements in classic content. If a page's visible text comes from somewhere else — a page builder, shortcodes, theme templates or custom fields — Frontpen cannot verify that editing it is safe, so it keeps the edit option visible and links to the standard WordPress editor instead.
Why is there no Frontpen button on a WooCommerce product?
WooCommerce product screens commonly render titles, prices and summaries from product fields and templates rather than Gutenberg post content. Frontpen stays hidden when it cannot safely edit those fields. A product description built with supported Gutenberg blocks can still use inline editing.
How do I stop a specific block from being edited?
Add the CSS class frontpen-no-edit to the block in the block editor (Advanced → Additional CSS class(es)). To lock an entire post, tick "Lock this content from front-end editing" in the Front-End Editing box on the edit screen.
Does it work with custom post types?
Yes, for any public post type whose content is built from supported blocks.
What happens if two people edit at once?
Before writing, the server checks that the block still contains the text the editor started from. If it changed, the save is refused and you are asked to reload, so no one's work is silently overwritten.
更新日志:
- Text nested inside wrapper elements is now editable — e.g. a paragraph inside a list item, the structure produced by many HTML exporters and AI tools.
- Classic content now also supports table cells, figure captions and definition lists.
- Per-user access control: always-allow specific users regardless of role, or block specific users entirely (administrators can never be blocked).
- The toolbar reports how many text regions are editable when entering edit mode.
- Inline editing now works on classic (non-block) content: plain-HTML paragraphs, headings and list items are matched back to the stored content and edited in place.
- Elements that cannot be verifiably matched — page-builder or shortcode output, nested lists, elements containing images or media — are never made editable, so the design cannot be broken.
- Classic saves reuse the same conflict detection, sanitisation, revisions and undo as block saves.
- Hide the no-block fallback on unsupported WooCommerce products and other custom post types.
- Keep inline editing available when a custom post type actually contains supported Gutenberg blocks.
- Avoid loading editor assets on unsupported custom post types with no editable content.
- Keep an edit control visible to authorized users when a page has no supported inline-editable blocks.
- Improve front-page detection by removing an unnecessary main-query restriction.
- Queue rapid saves and preserve edits typed while an earlier save is running.
- Use the WordPress HTML API for safer block annotation.
- Defer the front-end script, cache block settings per request, and add a Plugins-screen settings shortcut.
- Strengthen conflict detection and prevent nested blocks from being flattened by inline editing.
- Initial release.