Starting with version 8.3, WPBakery Page Builder has introduced a significant new feature: the ability to save core WordPress Page Settings directly within the Frontend Editor. This functionality includes managing:

• Page title
• Post status
• Featured image
• Excerpt
• Other WordPress native attributes

These settings can be accessed through the gear icon (the same icon previously used exclusively for custom CSS settings), screenshot ;

User Experience Trade-off

While this feature represents a valuable addition to the editor's capabilities, there are concerning implementation choices that impact the overall user experience. The most significant drawback is that saving these WordPress attributes triggers a full page refresh. This fundamentally undermines one of the core advantages of the Frontend Editor.

In previous versions, all saves occurred via AJAX, allowing users to remain in their working environment without interruption. In version 8.3+, saving WordPress attributes forces a complete page reload, disrupting the editing workflow.

The integration decision has created an additional regression. Since WPBakery chose to use the same interface window for both WordPress attributes and custom CSS, even custom CSS saves now trigger a page refresh, which didn't happen in previous versions. This represents a clear step backward in user experience.

This implementation has been met with concern from multiple theme authors and developers (#31355127, #31416976). At present, WPBakery has not provided a clear response regarding whether they plan to restore the previous AJAX-based saving functionality. While the new version does introduce useful features and improvements, these specific workflow changes represent a regression in user experience. We will continue to monitor the situation and update this documentation as more information becomes available.