Hi, please try temporarily deactivating all non-SiteOrigin plugins on the beta site to see if the issue persists. If the issue does persist, please, try temporarily switching the beta site to a default WordPress theme, do the issues persist with a default theme and only SiteOrigin plugins activated?
- No known issues.
- No reports at this stage but testing is not currently being done on PHP 8.5.
Hi,
Thank you for your quick response.
I have carried out both steps as requested:
- Deactivated all plugins except the SiteOrigin plugins — issue persists.
- Switched to a default WordPress theme with only SiteOrigin plugins active — issue still persists.
For reference, the live comparison is still visible here:
Could you please advise on next steps?
Thank you.
Here is a quick test with the HTML from the Custom HTML Widget that’s currently printing to the site front-end: https://demo.siteorigin.com/corp/sandbox/. You can try adding only the row that’s at issue to a new test page to see if the issue persists when only the Custom HTML Widget is present.
Hi @misplon ,
Thank you for the suggestion. I have completed the test as requested.
I created a new blank test page on the beta site with a single row containing only the Custom HTML Widget, and pasted the AP Projection content into it. https://prnt.sc/FjR4ITMsE-47
URL: https://beta.apdiving.eu/en/test-page-3/
Please check from your end.
Thank you!
How is the issue presenting on the beta home page? I’m focussed on the HTML printing to the site front-end near the bottom of the page.
On the test page, can you please try inserting the HTML version of the content to see if it outputs normally to the site front-end. It starts with an h2 tag.
Yes when copy paste html it’s working fine. you can check
Strange that the HTML content is not being maintained in the Custom HTML Widget. Was HTML copied into the Custom HTML Widget?
Yes – https://prnt.sc/SwMW0wUOsOoe – If you want temp admin access i can provide it to you.
To confirm, the issue on the beta home page is there are two Custom HTML Widgets and instead of outputting the slider shortcode contents and the HTML contents, the raw shortcode and raw HTML is being output. Is this a correct summary?
If my summary above is correct, unfortunately, I’m not sure of the cause at this time. Does the issue resolve on the beta home page if you edit the two Custom HTML Widgets in a small way, perhaps change the widget Widget Styles background, save, then change it back again, does the Custom HTML Widget then output normally?
Hi @misplon ,
Thank you for the suggested workaround.
I have completed all the steps as advised:
- Opened each Custom HTML Widget in the Page Builder editor
- Changed the Widget Styles background color
- Saved
- Reverted the background color back to original
- Saved again
I have done this for the widgets on the beta home page.
Could you please check from your end whether the issue has resolved or if anything still appears incorrect?
Beta site URL for reference: https://beta.apdiving.eu/en/
Thank you.
Hi, thanks for the update. I don’t know if that exact sequence is needed but it looks like the Master Slider and Custom HTML Widget > HTML content are displaying normally on my end.
Thank you for confirming the home page is displaying correctly on your end.
We have a major problem: the same issue exists on every single page across the entire site built with Page Builder.
This means we would need to manually repeat this workaround on hundreds of pages and thousands of widgets, which is not practical or scalable.
ISSUE:
After updating from WordPress 6.8.5 to 7.0, the front end styling of pages built with Page Builder is completely broken. Widgets are not displaying correctly — layout, spacing, and styles are all affected.
LIVE COMPARISON:
Thanks for the update. Front-end styling is a bit broad to investigate and troubleshoot. To confirm, on other pages, the issue relates to the rendering of the contents of the Custom HTML Widget?
Thanks for the update.
At the moment, we don’t have any open issues related to Custom HTML Widgets producing malformed content, so we don’t have much existing information to reference. We also don’t currently offer a settings-based way to bulk-save Page Builder content across multiple pages.
You’re welcome to send us a layout from one of the affected pages, and we can test the Custom HTML Widgets locally to see whether we can identify anything further. To export a layout, edit the page and go to Layouts > Import/Export > Download Layout. You can then upload the JSON file to Dropbox, Google Drive, or a similar file-sharing service and send us the link.
It may also be useful to export a layout from a page containing Custom HTML Widgets both before and after the WordPress core upgrade, so we can compare the two versions.
As a separate troubleshooting step, you could try rolling the beta site back to a working state on WordPress 6.8.5, then upgrading first to the final 6.9 release before moving on to WordPress 7. This may help confirm whether the issue is related to a specific upgrade path. You can do this using the Core Rollback plugin:
https://ww.wp.xz.cn/plugins/core-rollback/
