Destroyed template after updating SP Page Builder 3.7.14 - Forum | JoomShaper
Staff replied SP Page Builder

Destroyed template after updating SP Page Builder 3.7.14

Asked by marvays 5 years ago Last activity 5 years ago

Hi. I'm embarrassed, but I have a problem again. I just updated your products. Helix is fine. But Page Builder has a huge problem. After installation, my page will be completely broken. When I open a page edit in the backend after the update, some lines are missing or do not display correctly. Almost all custom css are gone.

I enclose two pictures. . . . status before and after the update.

How to proceed? Will you find the problem, or do I have to make a copy, update and then fix everything again? The site is under active development and I must continue to work. The launch date is approaching.

Printscreen before:
https://postimg.cc/fJmHZSjL

Printscreen after:
https://imgur.com/a/dMlzVMd

Live page under construction:
https://renerga-j4.richta.eu/

7 replies

Oldest first Newest first Most helpful
Ofi Khan Staff
5 years ago

Hello marvays

Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials.

Best regards

marvays Asked this
5 years ago

Thank you for your interest.
I'm sending login information.
I will now back up the pages.
Please compare the sp pagebuilder entry with id 10. It will be completely destroyed after the update.

I posted some issues with SP Page Builder yesterday. Your administrators have requested a login, but probably haven't looked at it yet.

I work exclusively in the backend. I don't like working on a live frontend :)

Ofi Khan Staff
5 years ago

I am having this error while going your administrator page

marvays Asked this
5 years ago

sry. bad link . . . :(

Ofi Khan Staff
5 years ago

Thanks. I have updated SPPB 3.7.14 and your homepage looks the same as before. Please check.

marvays Asked this
5 years ago

Good. Thank you.
Where could the problem be?

Ofi Khan Staff
5 years ago

You are welcome. I am not sure. But it could be a cache issue.

Log in to reply.