SP Page Builder 6.9.1 – backend editor spins forever on legacy pages (pageContentById returns text:null) - Forum | JoomShaper
Awaiting an answer SP Page Builder

SP Page Builder 6.9.1 – backend editor spins forever on legacy pages (pageContentById returns text:null)

Asked by WOLF Anlagen-Technik 2 days ago Last activity 20 minutes ago

Hello JoomShaper team,

since updating to 6.9.x the backend editor no longer opens pages that were created in older versions and never re-saved. The editor shows an endless loading spinner.

Environment: Joomla 6.1.4, SP Page Builder Pro 6.9.1, site migrated from Joomla 3. 658 of our 791 pages still have their content only in the legacy text column; the content column is empty.

What happens

  1. Open a legacy page in the backend editor (administrator/index.php?option=com_sppagebuilder#/editor/<id>/).
  2. The request task=/editor.pageContentById&id=<id> returns HTTP 200, but with "text": null.
  3. The editor then throws "TypeError: Cannot read properties of null (reading 'map')" in assets/editor/dist/js/bundle.min.js and the spinner never goes away.

The same pages open and work in the frontend editor. Pages that were saved once with 6.8.0 (their content is filled) still open fine in the backend.

Expected: the backend editor should convert legacy text content on load, as the older 6.8.x did, or at least show an error instead of a spinner.

Questions: Is this a regression in 6.9.x? Is there a migration tool for pages from older versions? Is there a way to bulk-convert legacy pages?

Thank you!

5 replies

Atick Eashrak Shuvo Staff

Hi there!

Thank you for bringing this to our attention, and I sincerely apologize for the inconvenience caused.

To assist you more effectively, may I kindly request temporary administrative access to your site? This will allow me to thoroughly investigate and resolve the issue for you.

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

Looking forward to your response.

Best regards

WOLF Anlagen-Technik Asked this

Hi,

thank you for your response.

The temporary administrative access details are attached.

I have also completed a full backup of the website before providing access.

Please let me know if you need any further information.

Best regards,

Atick Eashrak Shuvo Staff

Can I take a full backup of your site to check the issue in my local machine?

WOLF Anlagen-Technik Asked this

sure feel free

Atick Eashrak Shuvo Staff

I apologize for the inconvenience caused. Could you please check now and let me know if the issue is resolved on your end?

Looking forward to your response.

Best regards

WOLF Anlagen-Technik Asked this

Hi Atick,

thank you very much for your quick help, the issue is resolved on our side.

I tested both editors after your fix:

Backend editor: about 20 legacy pages that were never re-saved with 6.9.x now open normally, with the full layout and without the endless spinner.
Saving works in the backend editor and in the frontend editor. I tested this on a duplicated page, and all content was still there after reloading.

I will mark your answer as accepted.

One question for my understanding: what exactly did you change on our site? Was it a patch in the component files, or a conversion of the legacy content in the database? I would like to know whether I have to do anything after future SP Page Builder updates, or whether the fix could be overwritten.

You can remove the temporary administrator access now. Thank you again!

Best regards,

Log in to reply.