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

I have already tested the scenario on my side and did not encounter any issues.

Can I take a backup of your site to test it in my local environment?

I sincerely apologize for the inconvenience. I have tested your website in my local environment, and everything is functioning correctly without any issues.

To further investigate and implement any necessary changes without affecting your live site, could you please create a duplicate of your website in a subdirectory? This will allow us to troubleshoot and make adjustments safely.

Please let me know once it is set up, and I will proceed accordingly.

Best regards

Apologies for the inconvenience. Unfortunately, at this time, the only available solution is to disable the firewall.

I sincerely apologize for the inconvenience. Unfortunately, it was my mistake—the comment was not intended for your post. I truly appreciate your understanding.

Please check this link : www.joomshaper.com/forum/question/38608#qa-answer-188686.

any news about this bug fix?

Apologies for the inconvenience. I have forwarded the issue to the development team. However, due to the ongoing Eid holiday, there may be some delays. Thank you for your understanding and patience.

Thank you for your patience, and we sincerely apologize for the inconvenience caused.

We’ve identified the issue affecting SP Page Builder’s front-end functionality. Our development team is already working on it, and a fix will be included in the upcoming update.

We appreciate your understanding and support. Please feel free to reach out if you have any further questions in the meantime.

Hi,

SPPB release 5.5.6 has been published today and this bug is not resolved yet.

Could you please explain me what are you waiting for ?

It is definitively not acceptable.

I'm not asking a huge work, but just to fix a basic feature = a close button working properly !

Thank you for your message, and I sincerely apologize for the inconvenience this issue has caused you.

I completely understand your frustration—having a basic feature like the close button not functioning properly is indeed unacceptable, and you have every right to expect better.

This specific issue is not affecting the majority of users and has only been reported by you and a couple of other customers. Unfortunately, we’ve been unable to reproduce the problem on our end, which is why it's taking longer than expected to identify the root cause.

However, I want to assure you that your provided website access has been extremely helpful. Our development team is actively using it as a reference environment to investigate and implement a solution. We kindly ask that you keep the access available, as it is crucial for resolving this quickly.

Once again, I’m very sorry for the delay and appreciate your continued patience and understanding.

Best regards

Hello,

Thank you again for your patience.

I'm pleased to let you know that our development team has identified and resolved the issue. The root cause was related to a limitation on your server, which does not support PATCH requests—this was preventing the close button from working as expected.

The fix will be included in the upcoming official update of SP Page Builder. In the meantime, I’m providing you with a patched version in the hidden content area so you can apply the solution immediately.

Please install it and let us know if the issue is resolved on your end. We’re here to support you if you need any further assistance.

Best regards

As for the PATCH request behavior—starting from version 5.5.3, we updated the logic of the frontend editor page to improve overall performance and flexibility. This change introduced the use of PATCH requests in certain operations. That’s likely why the issue began occurring from version 5.5.3 onwards.

We sincerely apologize for the inconvenience caused. The upcoming version is taking some time to be released, as it includes significant new features.

However, if you require an urgent fix, I can provide you with a patch version that resolves the current issue.

Please let me know if you would like to proceed with the patch. I look forward to your response.

Best regards

Check the hidden content area