Title: Pierce's Replies | WordPress.org

---

# Pierce

  [  ](https://wordpress.org/support/users/maintainwp/)

 *   [Profile](https://wordpress.org/support/users/maintainwp/)
 *   [Topics Started](https://wordpress.org/support/users/maintainwp/topics/)
 *   [Replies Created](https://wordpress.org/support/users/maintainwp/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/maintainwp/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/maintainwp/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/maintainwp/engagements/)
 *   [Favorites](https://wordpress.org/support/users/maintainwp/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[FrontEdit - Live Frontend Block Editor] The free version is useless](https://wordpress.org/support/topic/the-free-version-is-useless-16/)
 *  Plugin Author [Pierce](https://wordpress.org/support/users/maintainwp/)
 * (@maintainwp)
 * [8 hours, 43 minutes ago](https://wordpress.org/support/topic/the-free-version-is-useless-16/#post-18982017)
 * Hi [@alamea](https://wordpress.org/support/users/alamea/),
 * Thank you for taking the time to try FrontEdit and explain what disappointed 
   you. I value feedback like this, especially when it identifies a gap between 
   what I intended to communicate and what a new user actually experiences.
 * You were right that the additional Pro preview pages could make the free plugin
   appear much more limited than it is. The free version includes the full FrontEdit
   editing experience for currently supported blocks, including editing multiple
   blocks during the same session. Pro does not unlock additional editing capabilities
   for those blocks; it adds advanced workflows such as drafts and approvals, per-
   user permissions, request management, a content catalog, and edit history.
 * However, I understand that presenting those Pro features as separate menu pages
   created the impression that much of the plugin was unavailable. Based directly
   on your feedback, I have removed those preview pages, added a more useful Getting
   Started section, and revised the plugin’s messaging to explain more clearly what
   is included in the free version. Those changes will be available in the next 
   update which will be live soon.
 * Regarding custom post types, FrontEdit is currently designed to edit supported
   Gutenberg blocks stored in standard WordPress post content. It does not edit 
   Meta Box fields, custom metadata, or content created through third-party page
   builders. Every supported block is implemented and tested individually because
   preserving valid Gutenberg serialization and avoiding corrupted content or invalid
   blocks is one of my highest priorities.
 * That said, your review highlighted that FrontEdit currently excludes custom post
   types even when they use the normal block editor and contain blocks that FrontEdit
   already supports. I am now actively investigating how to add safe support for
   those block-based custom post types. This would not mean attempting to edit arbitrary
   custom fields, but it could allow FrontEdit to work with supported Gutenberg 
   blocks wherever WordPress stores and manages them through its normal block-content
   workflow.
 * I am committed to continuing to improve FrontEdit when user feedback identifies
   something that fits its purpose and can be implemented safely. Your review has
   already resulted in concrete changes, and it has also helped shape an important
   area I am now working to expand.
 * I hope the revised onboarding makes it easier to evaluate FrontEdit for its intended
   use: editing supported Gutenberg blocks directly on a post or page. If you have
   a chance to revisit that core workflow, I would genuinely welcome any further
   feedback. Either way, thank you again for pointing out where the experience and
   expectations did not match.

Viewing 1 replies (of 1 total)