Jamie's Front-End Editor for Content Teams -- WordPress 插件

开发者	jamiemarsland
更新时间	2026年7月21日 17:56
PHP版本:	8.0 及以上
WordPress版本:	7.0
版权:	GPL-2.0-or-later
版权网址:	版权信息

Jamie's Front-End Editor for Content Teams lets your team edit page and post content directly from the front end of your WordPress site. No need to open the block editor — click any text, link, button or image on the live page and change it in place. Built on the WordPress Interactivity API with no build step required. Give your team precise, bounded editing: let them fix the copy that should change, and lock down the parts that shouldn't. Features:

Click any paragraph or heading to edit it inline, right on the live page
Add, edit or remove links on your text without leaving the page
Replace images from the media library, set alt text, or remove an image, all on the front end
Edit button text and links from the front end too
Block markup is fully preserved on save
Lock a whole page from front-end editing with a single checkbox
Lock individual blocks or whole sections, using the block's own Lock option (padlock) or a CSS class. Locks cover everything nested inside and are enforced on save, not just hidden in the UI
Edits are recorded as native WordPress block notes, so there's an audit trail
A central Site changes screen (Tools menu) lists every front-end edit across the whole site — what changed, where, by whom and when — with filters by user, page, block type and date, plus search and CSV export
Admin settings to choose which block types are editable
Option to restrict chosen roles to front-end-only editing (no wp-admin access)
Secure — only users with edit permissions see the editing UI

0.8

New: a central "Site changes" screen under the Tools menu that gathers every front-end edit across the whole site into one filterable, searchable list — what changed, where, by whom and when. Read-only, for editors and admins. Export the current view to CSV.
Front-end edits now store structured data (page, block type, old/new text, user) so the new screen can filter and search them. Existing notes are backfilled once on upgrade.
Fixed a brief flash of the editing toolbar and dialogs when a page first loads.

0.7.1

Updated the plugin description to reflect that you can now edit text, links, buttons and images from the front end.

0.7

Inline image editing. Click an image while editing and a small toolbar appears over it: Replace opens the WordPress media library and swaps the image in place, Alt text lets you set the image's alt for accessibility, and Remove deletes the image block. Changes save straight into the block, and concurrent edits are still guarded.
Button editing. Click a button to change its text and its link (and whether it opens in a new tab) in a small dialog, right on the front end.
More reliable saves. Edits are now matched to blocks by content fingerprint, so removing or replacing an image no longer causes a later text save to report a false "changed by someone else" conflict.

0.6

Inline link editing. Select some words while editing and a small link bubble appears — click it to add a link (set the URL and, if you like, open it in a new tab). Click an existing link and the bubble offers Edit and Remove. Links save into the block markup like any other edit, and they no longer navigate away while you are editing.

0.5

A friendlier way to enable other block types. The Advanced setting is now a search-and-add field with removable chips instead of a long checklist: type to find a block, click to add it. Much easier on sites with lots of blocks.

0.4

Fixed a bug where pressing Enter while editing could insert invalid markup and cause a "block validation" error in the block editor. Line breaks are now saved cleanly.
Concurrent editing is now safe. Front-end editing takes WordPress's native post lock, so two people (whether on the front end or in the block editor) can no longer edit the same page at the same time and silently overwrite each other. Anyone else who opens the page sees a read-only "So-and-so is currently editing this page" notice, and as a backstop the save is rejected if the content changed underneath the editor.
Added an Advanced setting to enable front-end editing for other (non-core) block types on your site, such as blocks from your theme or other plugins. Tick the ones you want in Settings > Front-End Editor. This works best for blocks that show their text in a normal heading or paragraph tag; incompatible blocks simply do nothing, so nothing breaks.
Documentation: the plugin description now covers the editing locks added in 0.3.

0.3

Added editing locks for finer control over what your team can change. Lock a whole page with a checkbox in the "Front-End Editing" box, or lock a single block or section using the block's own Lock option (padlock) or the CSS class "fie-no-edit" (locks that block and everything inside it). Locks are enforced on save, not just hidden in the UI.

0.2

Added a live demo preview (WordPress Playground blueprint).

0.1

Initial release.

Jamie's Front-End Editor for Content Teams

标签

下载

详情介绍:

安装:

常见问题:

更新日志: