Staff replied SP Page Builder

SP Builder Pro UI crashes after update to 6.2.2

Asked by Denis 10 months ago Last activity 10 months ago

I just updated the SP Builder Pro to current version 6.2.2. When I try to edit an item of a slideshow the UI crashes with the message: 'Unhandled Runtime Error
TypeError: x.map is not a function'
It's strange that this only happens from the second item onwards.

The call stack is

vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2 TypeError: x.map is not a function
    at ih (bundle.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:1210216)
    at xs (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:560436)
    at xl (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:617268)
    at yc (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:606420)
    at mc (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:606348)
    at pc (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:606211)
    at rc (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:603018)
    at sc (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:603407)
    at zo (vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:544282)
    at vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2:600959
ca @ vendors.min.js?3e7e96fad5e237fb2d5a081c6cb11212:2
/administrator/components/com_sppagebuilder/assets/editor/dist/js/bundle.min.js.map:1  Failed to load resource: the server responded with a status of 404 ()
/administrator/index…ponent#/editor/4/:1 Uncaught (in promise) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

2 replies

Atick Eashrak Shuvo Staff

10 months ago

Hi there,

Thank you for bringing this to our attention, and please accept my sincere apologies for the delayed response due to the weekend.

To assist you more effectively, I kindly request temporary administrative access to your site. This will allow me to investigate the issue thoroughly and work toward a resolution as quickly as possible.

Before sharing the credentials, I strongly recommend taking a complete backup of your site to ensure that all data remains secure.

I appreciate your understanding and look forward to your response.

Best regards

Denis Asked this

10 months ago

Hi there,

thank you for your quick answer!
Sorry, but my security policy doesn't allow to pass access right to external persons.

I tried to repeat that error within a Firefox browser, actually I work with Chrome (Linux), but it worked fine without issues. So I assume the problem comes with Chrome or my local settings. I allready cleared all caches etc. but nothing helped. At least, I have a workaround for that and I hope that it will work again in a future update.

Best regards

Atick Eashrak Shuvo Staff

10 months ago

Hi there,

Thank you for the clarification. We understand and respect your security policy.

Based on your testing, this appears to be a Chrome-specific issue, most likely related to browser cache or local settings. Since it works correctly in Firefox, the extension itself is unlikely to be the cause. In some cases, Chrome may retain cached data even after clearing the cache.

We’re glad you have a workaround in place, and hopefully a future update will resolve this behavior. Please feel free to reach out if the issue persists or changes.

Best regards