Hello sdlsites

Apology for the inconvenience. Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup with you before sharing.

Best regards

in hidden area

Any update here?

Apology for the delay. It seems like a bug. I have reported it to the development team. It will be fixed soon.

what is the issue you are reporting?

For me, fresh install of joomla 5 and latest version of sppb. Its not a migration, but a clean install. Seems though there is still an issue with the accordion item. I cannot change the name of "accordion".

Got it! Thank you for the clarification. Hope you are having a good day.

Hello.

Is this fixed in the new version of SPPB 5?

We noticed that in 5.2.9 there is no way to even edit an accordion that was created in 3.x.

Will you please check SPPB 3.0? If it does not work, then let me know.

It doesn't work. When you go to edit any accordion menu that was created is 3.x, all of the content disappears.

Please export the page in SP Page Builder 3 and share the JSON file here. I will check it with SP Page Builder 3 and upgrade the component to SP Page Builer 5. Then I will check the page again.

i have added the link.

The fix has been

• Upgrade to SPPB 5
• Duplicate the accordion menu
• Delete the original

Once it is duplicated in SPPB5, it works. If it is just the SPPB3 that is upgraded, it doesn't work. The issue is that once we roll this out to all of our sites versus just the 3 test sites, we will have around 80 websites running accodions on over 40 pages each, so we would need to manually modify over 3,200 pages if there isn't a fix.

Your JSON file does not contain any Accordion addon. Please export the page with SP Page Builder 3 and share the JSON file. I will check it. In general, I have not found the issue on my testing.

It definitely had the accordion menu. I have attached in the hidden content.

In the prior comments you did acknowledge that this was a bug. Let me know if you want more videos showing the issue.

Hello - Just following up on this. Thank you

Apology for the delay due to my illness. I have uploaded the JSON file in SP Page Builder 5. The accordion addon works fine in the page. I have not encountered any issue. Please share a screenvideo of the issue. I will then talk to the development team about this with reference.

Hello

Based on the video that I sent 2 months ago, you said that there was a bug and that the developers were looking into a resolution. Please let me know what I should demonstrate in the new video.

The accordion in the JSON that I shared does work. The issue is when the extension is updated and then the accordion is edited. Please confirm that you loaded it into SPPB 3 then upgraded to SPPB 5 and then tried to edit the accordion or add a new one onto the page. This is the only way that you will be able to replicate the results.

Just let me know what you need in order to get this resolved because it has been months since I shared the original video and you told me that there was a bug and now you are now asking for a video again.

John

My apology for the miscommunication. My bad!

Since I have identified the bug, it is definitely a bug. Unfortunately, we are not developing SP Page Builder 3 any more. You have to manually update these to SP Page Builder 5. You already know a fix by duplicating the addon. But have you checked exporting JSON files on SP Page Builder 3 and then importing on SP Page Builder 5. If this method works, then it would be easier for you (I think so).

This is getting infuriating.

The bug occurs during the upgrade from Pagebuilder 3 to Pagebuilder 5. It works perfectly fine when in SPPB 3. I am trying to upgarde our websites and this bug presents itself after the extension is upgraded.

Please watch the video. You will see exactly what I am talking about. You told me that it is a bug and that the development team would be working on a fix. This was 2 months / 2 releases ago.

Okay, I have seen it again. It has been reported to the team. It will be checked in the next release.