Hoi Ton,

Can I be fully honest with you? If yes, please consider template framework change from OLD Helix3 to Helix Ultimate. Go forward, and don't try to use by force solutions from years ago.

Yes, in theory you can still use raw Helix3 - but .... as you may noticed in changelog, that template gets only urgent updates and nothing more! Legacy mode!

If you have template based on Helix3 - there is a different story. But you forgot to share full template name.

• Helix Ultimate 1.x is on the market since 2018.
• Helix Ultimate 2.0 is on the market since 2021 (!)

and as you see it's time to go ahead.

BTW

In Joomla Admin you can enable Error reporting & Debug mode (two options) to see all errors details:

It helps to understand of bug source.

I am using template Helix 3 with SP page builder. On a staging site I already tested Helix ultimate. But there are to many problems with compatibility and errors. On top of that I am having trouble mastering the user interfase. So if helix 3.05 can not work with php 8.2 i am considerig dropping Joomshaper as a partner. That would be sorry.

1. Raw Helix3 should work with PHP 8.2. But I still don't know full name of your template.
2. Enable Debug to see more details, then you can share (screenshot link or message itself) - if you don't unterstand them.
3. Test site using PHP 8.1 as well. Error500 can be caused by extension: module or plugin.

I am working in J4. template name: shaper_helix3 - Standaard But hold on... I set php to 8.1 and debug on... but nothing to debug right now. It seems to work :-)

As I told before, Error500 can be caused by extra plugin or module, also module override.