Dreamfox Client Edit Mode
| 开发者 | dreamfox |
|---|---|
| 更新时间 | 2026年9月29日 21:28 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Protect the pages the client may edit.
- Assign one or more Client Editor users to those pages.
- Choose per page (and optionally per user) whether text, images and links may be changed.
- The block editor's REST save — rejected with a clear per-violation error in the editor.
- Classic admin saves and XML-RPC — a late
wp_insert_post_dataguard. - Page-level access —
map_meta_cappins Client Editors to their assigned protected pages; everything else (including deleting and creating posts) is denied. - Elementor-built pages — Client Editors can open the Elementor editor, and saving plus direct
_elementor_datawrites are validated the same way as everywhere else.
- A simplified admin: a My Pages screen with an Edit button per assigned page, irrelevant menus and toolbar items hidden.
- An optional "Edit this page" toolbar link on their assigned pages.
- Clear error messages when a change is not allowed, instead of a broken layout.
- Every allowed change creates a normal WordPress revision — nothing is ever overwritten without a trace.
- An activity log of allowed and blocked saves (summaries only: element IDs and attribute names, never full content, never IP addresses), with configurable retention.
- Text / image / link permissions per page, with per-user overrides.
安装:
- Upload the plugin files to
/wp-content/plugins/dreamfox-client-edit-mode, or install through the WordPress plugins screen. - Activate the plugin through the 'Plugins' screen.
- Open Client Edit in the admin menu, protect a page and assign a Client Editor.
- Create client users under Users → Add New with the "Client Editor" role.
屏幕截图:
常见问题:
Is the protection just hidden editor buttons?
No. The editor UI is locked for the role, but every save is additionally validated on the server against the stored page. Even a hand-crafted REST API request with a Client Editor's credentials cannot add, remove, move or restyle elements — the whole save is rejected with a 403 and a list of violations.
What exactly can a Client Editor change?
Only what you allow per page, in three categories: text (headings, paragraphs, button labels …), images (replace an image, its alt text or caption) and links (URLs and link targets). Layout, styling, element structure and everything else is always locked. You can override the three categories per user.
What happens when a Client Editor tries something that is not allowed?
The save is rejected as a whole — no partial merge — and the editor shows a clear message explaining what was not allowed. The attempt is recorded in the activity log.
Does it work with Elementor?
Yes. Client Editors can open the Elementor editor on their assigned pages, and every save (plus direct _elementor_data writes) is validated against the same text/image/link rules as the block editor.
How many pages can I protect?
As many as you like — there is no limit.
Are changes traceable?
Yes, twice over: every allowed save creates a regular WordPress revision (so you can compare and restore), and the activity log records who changed what, when, linked to that revision — plus every blocked attempt.
A block I added later is not editable for the client. Why?
Blocks get a persistent internal ID when a page is protected. Blocks added afterwards do not have one yet and are read-only for Client Editors until you press Re-sync IDs on the Protected Pages screen.
Which hooks can developers use?
dreamfox_client_edit_permissions— filter the permission set used for a protected page.dreamfox_client_edit_can_modify— filter a single per-element/attribute permission decision (structural changes never reach this filter; they are always denied).dreamfox_client_edit_allowed_attributes— classify attributes of custom blocks/widgets into the text / image / link / layout / style / advanced categories.dfce_protected_post_types— post types guarded by the block editor save guard (default: page, post).dfce_save_blocked(action) — fires whenever an enforcement path blocks a save.
Where can I find documentation and support?
- Knowledge base: setup guides, permissions, Elementor and troubleshooting.
- Support: submit a request to the Dreamfox Media team.
- Dreamfox Media: more plugins and services.
Does it delete my data on uninstall?
Not by default. Enable "Delete all plugin data when the plugin is uninstalled" under Client Edit → Settings → Advanced first if you want a clean removal. The Client Editor role itself is always removed on uninstall.
更新日志:
- Added the plugin icon, banner and screenshots for the WordPress.org plugin page.
- Readme: added links to dreamfoxmedia.com and the knowledge base.
- Remove all Pro feature gating: unlimited protected pages, Elementor editing and per-element permission rules are now standard, unrestricted functionality.
- Move the "My Pages" admin menu item to the default (lower) position instead of a prominent top position.
- Bump "Tested up to" to WordPress 7.1.
- Trim short description to meet the wp.org 150 character limit.
- Harden activity log queries with esc_sql() on the table name.
- Initial release.
- Client Editor role restricted to assigned protected pages (map_meta_cap).
- Permission diff engine: server-side validation of every save (block editor REST, classic admin, XML-RPC, Elementor) with all-or-nothing rejection and per-violation messages.
- Text / image / link permissions per page and per user; layout, styling and structure always locked.
- Content-only block editor experience for the role; persistent block IDs with re-sync.
- Simplified client dashboard (My Pages), pruned admin menus/toolbar, login redirect, frontend edit link.
- Activity log with revision linking, configurable retention and daily cleanup.