Has anyone noticed any issues with the Customizer in Wordpress 6.7? I have one theme built with Pinegrow, and recently, every time I make a change in the Customizer, the page refreshes and takes you back to whatever page you entered the Customizer from. If you try to navigate to any other pages (to see what the changes look like on those pages) the new changes don’t appear and it reverts back to the old settings.
Once you save, all the changes show up fine on the live site. The issue is just with the Live Preview within the Customizer. I also checked my other Wordpress themes not built with Pinegrow and they’re not having this issue. Has anyone had this problem?
Yes, this is a known issue with WordPress 6.7 affecting the Customizer functionality, particularly with custom themes. The problem you’re experiencing with the page refreshing and reverting changes is being reported by many users across different themes. The issue seems to be related to how WordPress 6.7 handles the Customizer preview and rendering.
I can confirm that this is not specific to Pinegrow-built themes, as similar issues have been reported with other themes like GeneratePress and XStore. Some users have found that clearing browser cache and cookies can help temporarily, but it doesn’t fully resolve the underlying issue.
For now, as a workaround, you can still make your customizations and save them - they will appear correctly on the live site as you mentioned. WordPress developers are aware of this issue and are collecting information about it. Until a proper fix is released, you’ll have to work around the preview limitations.
If you need to check how changes look on different pages, you might want to save the customizations first and then view the actual pages on the live site. While not ideal, this approach ensures your changes are properly applied across the site.
The “good news” is that this appears to be a WordPress core issue rather than a theme-specific problem, so it should be addressed in a future update.
I hope so because I’ve recently encountered many issues trying to disable WordPress frontend and use it only as a backend (with the frontend being “managed” by a site builder - an idea I’ve been exploring for some time to avoid reinventing the wheel when I need a CMS and don’t want to or know how to develop one ).
is that this appears to be a WordPress core issue rather than a theme-specific problem, so it should be addressed in a future update.
).