UI Bug on Page Builder on latest V29.5.1

September 27, 2024 4:12 PM

We just upgraded to the newest version and in the Admin, we started to see the widget headers with broken icon images while the page is in non-edit mode. See a screenshot: Page Builder Error

You can actually click the broken edit icon and the widget config opens. If you try saving it, it does give an error so it doesn't actually save..

I think it is good to be able to see the widget configs without having to put the whole apge in edit mode but it should not show the broken icons or present the save button or active fields. The widget config fields should be de-activeted in any case.

We are also seeing a JavaScript error on the admin now, see attached image.

JS Error

Thank you!

Environment

  • Xperience by Kentico version: 29.5.1
  • .NET version: 8
  • Deployment environment: Azure

Answers

September 27, 2024 6:48 PM

Your linked images are broken - they look like sharepoint links? Maybe they display for you but I don't think they will for anyone else.

You could try something like https://imgur.com.

What version did you upgrade from? The Page Builder read-only mode was added in v24.0.0. There were some Page Builder script changes and you might be seeing the effects an older cached version of the scripts.

Try clearing your browser cache or removing those scripts from the CDN if you are using one.

September 30, 2024 1:50 PM

Thanks Sean, here are the image links:

https://imgur.com/NA81DtU https://imgur.com/enCs7XG

We were upgrading from 29.3.0 I believe and we did flush the cache from everywhere and checked it on Incognito and it still happens.

October 1, 2024 10:43 AM

Like Sean mentioned, this is most likely related to the improved 'read-only' mode added to the Page Builder, which displays the Admin UI for widgets and sections on pages in non-edit mode. To fix this, make sure the Page Builder styles are correctly rendered within that context in your layout file. At least this was my issue.

October 8, 2024 7:08 PM

Thanks Milan, that was it!

To answer this question, you have to login first.