Frontman – AI Website Editor for WordPress, Elementor & WooCommerce
Changelog
1.4.0
Sync the Frontman plugin release with Frontman v1.4.0
See the GitHub release notes for the full cross-product changelog
1.3.0
Keep the WordPress plugin aligned with the Frontman v1.3.0 release train.
Refresh WordPress.org listing metadata, including the tested WordPress version, to keep the plugin page current for new installers.
Improve plugin-directory search copy around AI WordPress editing, live preview editing, Elementor editing, and WooCommerce store management.
Add clearer FAQ entries for AI page editing, Elementor support, WooCommerce tools, and the live preview workflow.
Improve screenshot captions so users can understand the AI editor, live preview, visual selection, and WooCommerce editing workflow before installing.
1.2.0
Improve WordPress.org listing copy for non-developer WordPress teams.
Position Frontman more clearly as an AI website editor for marketers, content teams, support teams, store operators, and agencies.
Highlight practical editing workflows for pages, posts, Gutenberg blocks, Elementor pages, WooCommerce data, menus, templates, widgets, settings, and Additional CSS.
Clarify the live preview workflow so users know they can review site changes beside the AI editor.
Expand safety and third-party service details so administrators understand access controls, data flow, and recommended staging-site use before using AI editing on important sites.
1.1.0
Update WordPress.org listing copy for non-developer WordPress teams
Position Frontman as an AI website editor for marketers, content teams, support teams, store operators, and agencies
Highlight live preview editing, visual selection, Elementor support, WooCommerce tools, safety controls, and third-party data handling
1.0.0
Launch Frontman for WordPress as a self-contained AI editing plugin
Add native tools for posts, pages, blocks, Elementor, WooCommerce, menus, templates, widgets, safe options, and Additional CSS
Run WordPress, Elementor, and WooCommerce tools directly inside the PHP plugin
Improve safety with admin-only access, nonces, sanitized inputs, allowlisted options, and safer CSS validation
Strengthen WordPress source-of-truth guidance for Elementor and theme edits
Fix WordPress admin menu icon alignment
0.18.2
Improve Elementor mutation schemas so empty add-element, update-settings, full-page-data, and generated-child payloads are rejected before they reach Elementor
0.18.1
Preserve existing WordPress page templates when saving or rolling back Elementor page data, and report any template side effect in Elementor tool responses
0.18.0
Add WooCommerce tools for products, orders, customers, shipping, taxes, coupons, reports, settings, system status, and store data when WooCommerce is active
0.17.2
Improve Elementor editing tool guidance and recovery errors for non-empty settings diffs and full-tree updates
0.17.1
Align plugin metadata and release packaging for the next WordPress.org build
0.17.0
Align plugin dependencies with the Frontman v0.17.0 maintenance release
Keep WordPress package metadata current with the shared client and framework packages
0.16.1
Fix image attachment uploads for WordPress media replacement workflows
Strengthen Elementor rollback safety for precise widget and HTML-fragment edits
0.16.0
Add Elementor selected-element context so Frontman can inspect and edit Elementor-backed selections more directly
Add a WordPress media upload workflow that resolves user-provided images into Media Library attachments for posts and Elementor elements
Preserve previous Elementor data as private rollback snapshots when updating, removing, or replacing Elementor content
Fix WordPress page duplication so Elementor page metadata and post-backed navigation item metadata are preserved
Run WordPress Elementor edits serially and route target metadata deterministically between settings edits and HTML-fragment edits
0.15.0
Fix WordPress Playground relay requests so scoped tool calls and source-location POSTs keep the leading /scope:… path prefix
Improve transient error handling in the shared Frontman UI with categorized errors, automatic retry, retry countdowns, and a manual retry button
Keep WordPress editing sessions more reliable when network or relay requests fail temporarily
0.14.0
Bump package versions for a maintenance release across the Frontman workspace
0.13.0
Bump package versions for a maintenance release across the Frontman workspace
0.12.0
Add production-ready WordPress support with PHP-native filesystem tools and plugin ZIP release packaging
Add safer mutation history snapshots for WordPress editing tools
Add richer WordPress editing tools for menus, blocks, templates, and cache workflows
Require confirmation before destructive delete tools run
Preserve freeform HTML during block mutations and limit widget mutations to supported safe widget types
Remove the old standalone package and release flow from normal WordPress plugin operation
0.3.3
Send the WordPress runtime nonce on plugin tool POST requests from the shared client
Keep the WordPress plugin metadata aligned for the next release
0.3.2
Remove the standalone package and remaining standalone references from the WordPress flow and release tooling
Show a first-use caution warning reminding users to use backups and review experimental changes carefully
0.3.1
Preserve freeform HTML while mutating blocks so block edits do not silently drop non-block content
Restrict widget mutations to the supported safe widget types instead of generic direct option writes
Add tests for the new menu, block, widget, template, and cache tools plus delete-confirm flows
0.3.0
Add WordPress-native menu, block, widget, template, and cache tools that remove more admin tasks from the browser UI flow
Require explicit confirmation for destructive WordPress delete tools before they run
Capture pre-edit snapshots for the new mutating WordPress tools so tool history preserves the previous state
0.2.3
Add wp_create_menu_item so the agent can add navigation links directly through WordPress tools
Include pre-edit snapshots in menu item creation and update flows
0.2.2
Include the prior asset state in mutating WordPress tool results so edit history captures what changed
Add PHP mutation snapshot tests for posts, blocks, menus, options, and widgets
0.2.1
Remove the extra server dependency from the WordPress plugin and release ZIP
Run all normal file tools entirely inside the PHP plugin runtime
Clear PHP file-tracker state on deactivate and uninstall
0.2.0
Move the core filesystem tools into the WordPress plugin itself and stop relying on the Bun standalone for normal file operations
Add PHP tests for the local core tool implementations
0.1.14
For Lighthouse bootstrap, prefer using the bundled standalone binary as the Bun CLI before falling back to system Bun or installing Bun
0.1.13
Prepare Bun and Lighthouse runtime dependencies only when the lighthouse tool is called, with the WordPress plugin performing the bootstrap before proxying the audit
0.1.12
Detach bundled standalone startup more cleanly with setsid/stdin redirection to avoid tying the process to the originating web request
0.1.11
Fix bundled standalone cleanup paths when Frontman classes are loaded during uninstall without bootstrap constants
0.1.10
Install Bun on startup when needed and run bun install for standalone Lighthouse runtime dependencies
0.1.9
Make search_files avoid Git fallback outside Git repositories and use plain filesystem search instead
0.1.8
Improve plugin lifecycle cleanup during uninstall and deactivation
0.1.7
Improve plugin deactivation cleanup
0.1.6
Improve WordPress production tooling support
0.1.5
Add plugin-side runtime logs for debugging tool execution
0.1.3
Let list_files work outside Git repositories for typical WordPress hosting setups
0.1.2
Improve file tool behavior on restrictive WordPress hosting setups
0.1.1
Improve release packaging for the WordPress plugin
