unable to edit content using Advanced editor

Hi,
kwanumzen108 it looks like you have pasted theme shortcode into a text element, but you have extra HTML before and after the shortcode, typically this will cause breaks:


sometimes this occurs when a page is saved as a default WordPress builder page, and then converted back again.
cws0827 I’m not sure what you mean by scenery theme package, please open a new thread with the url to the page in question and an admin login so we can be of more assistance. It gets confusing when we are working on more than one site per thread. Thanks for understanding.

Best regards,
Mike

Hi,
I don’t believe that there is a issue with backward compatibility, we would have also experienced this on our sites and seen other users post this, but I have seen shortcode in the text element become corrupt as in this screenshot:
https://img.savvyify.com/images/2024/07/21/Enfold_Support_6362.md.jpg
I also note that you seem to have put your ALB shortcodes in a text element, instead of adding the elements to the page, do you recall building your pages like this, it is unusual.
You could try rolling back to the older version, or restore your server backup to before you updated.

Best regards,
Mike

Hi,
Ok, so you have had this issue for a few years?
The ALB code doesn’t become outdated, but unclosed HTML tags can break the backend of a site and the frontend can still look fine, this is because of how the shortcode is rendered for the frontend.
For your homepage each of the elements on the backend seem to show the code for the whole page and not for the specific element, I copied a couple of them and compared the code.
Unfortunately this page is corrupt and I don’t see a way to correct it, I believe your best option is to restore your site to a older working version, or you could try using the page Revisions to go back to before the page was corrupted, probably by saving it as a Block Editor page, or you could create new pages from scratch.

Best regards,
Mike

Hi,
Often when a page is corrupt in this way, you can not correct it and save again, the error just returns, typically using the page Revisions will also not work, but perhaps if you go back far enough it might work, it might be worth a try. But please note to might not be able to recover if it breaks this page.
I would recommend creating a staging copy of your site first to test on.
I would draw your attention to the av_fullscreen shortcode in the beginning of the text elements, this is your full screen slider at the top of your page, but it shows in the text element below the slider:


and it also shows in the last text element on the page:


so this doesn’t match the frontend of your site, as you don’t have more than one full screen slider on your page, thus this page is corrupt and I don’t see a way to correct it,
this is why I recommend either recreating the page in a new blank page, or using your server backup. I know you said that you would have to go back years, but it sounds like you have not been able to update the page in years, so the backup should be the same as the last time you edited the page. In my guess.

Best regards,
Mike

Hi,
I believe this would not be a good idea. If you want to try to copy and repair the shortcode in each page, you could try creating a new site with a fresh install on a temp domain and Enable the Avia Layout Builder Debugger on it and your lave site and then copy the debugger shortcode from the live site and paste it into a text editor like VScode or Notepad++ and then search and replace all of the HTML entities like these

and the paste it into the new site, this might work, but you will need to be very careful to not miss any as this would create unclosed tags and break the new page.
But when I view your site it looks like it is based on the health demo with your text added, so in considering the time it would take, it seems to me that it would be a faster and better process to create a new site with a fresh install on a temp domain, then import the health demo, and then copy the text from the frontend to the new site, not the backend because you don’t want to copy the errors over.
Also when you copy the text from the frontend ensure to first paste it into a text editor like VScode or Notepad++ and remove any HTML code before to paste it into the new site, otherwise you might copy unclosed HTML tags into your new site a break it.
This would be a safer method than copying the debugger shortcode if you don’t work with HTML a lot and can spot the errors.

Best regards,
Mike