Hello Bob,

Thank you for reaching out to our technical support forum. I’m sorry to hear about the trouble you’re experiencing. Rest assured, I will look into this issue for you and work to resolve it as quickly as possible.

I have renamed this file as a temporary fix:

templates/shaper_helixultimate/html/layouts/joomla/editors/buttons/button.php

I will ask the developer team to check the issue. The issue only happens with JCE Editor.

Best regards

Thanks so much for the help Ofi

The temporary fix you have applied has got things working again. We do use JCE Editor. Do I need to rename that file after any future updates to SPPB? I'm happy to note this change if I do until a permenant solution is found. Please let me know

Bob

Apology for the inconvenience. To demonstrate the issue to the developer team, I have renamed the file back to original and the issue came again. The team will fix it on the next Helix update. Currently, I see 403 Forbidden on your site and can't change my modification. Please do this yourself to get the site running without issue.

I have turned on debug and create an SP Page Builder page named "Test". Please turn off debug mode from Global Configuration and rename this file:

templates/shaper_helixultimate/html/layouts/joomla/editors/buttons/button.php

Thanks for your update Ofi and for letting me know you accessed our site again. Our firewall software flagged an unexpected login from an IP address that wasn't in our safelist and blocked yoru account too. Please always let me know beforehand if you wish to login to our site and I can make the arrangements for you to help me further. I will always welcome the help and am happy for you to show your development team if we can be told first. I have removed the restriction on you if you want to log in again and put things back to be working now you are finished.

For my info - can I rename the button.php page to any other name and things will work? Please let me know that you have corrected it again once you have and turned off debuig mode or if you want me to do it.

I'd rather you do it as you have the SPPB knowledge of what you did more than me. Thanks again for the help and always happy to help if you would kindly let me know first going forward.

Bob

If you could please confirm this is working for me as our SPPB staff have left for the evening now and i want to make sure they are good to start work first thing in the morning please.

Thank you

My sincere apology for accessing without informing you. Thank you for letting me enter. I have fixed the issue again. Just renamed the file to _button.php. You can rename it to anything actually.

prnt.sc/7gbvC0m748hk

I have demonstrated the issue from your site to the team. The team will now check on our local environment and fix it on the next release. Then you can rename the file back to button.php and use it again.

Thanks for your understanding. Let me know if you require further help.

The developer team have not found the issue on our local setup. Can you please share you share your site backup for testing? We will check it on the localhost.

If you agree, then please take a full site backup with Akeeba Backup in ZIP format and share here via any drive link. Follow this tutorial if needed.

Hi Ofi Thanks for getting back in touch with me. I am sorry but I cannot provide you with a full backup of our website due to data protection and privacy policies of our organisation. This is not an option we could agree to. I hope you are able to replicate the issue in some other way and find a fix. If I can help with any other way, please let me know. I can provide temporary backend access to a UAT website we have for testing our website extensions in a similar way to what i have provided to our live website. If you broke anything in your testing on this website - it would be fine as no one visits it and it is designed to be broken and restored as we test new things. Again it wouldn't be legally possible for you to take an Akeeba backup of that site either but I could agree to temp login access for you to investigate the issue more.

Please let me know if that is an option.

Yes, that would also work. Then share me a testing environment credentials. Make sure that the issue exists there. I will share the credentials with the team for testing. Then they will work and fix it.