array_replace(): Argument #1 ($array) must be of type array, string given

Hi guys.

Is there an update for PHP8 support for the helix framework? As you know PHP 7.4 is running out of security fixes by end of November and I am worried that my website will not be supported.

We tried helixultimate but the server response times (TTFB) have been between 3 and 5 seconds, which was not acceptable.

I hope there is some good news out there.

Regards
Christian

Hello Christian,

depending on the tempalte I have several patches available or create new ones if needed.
For Helix 3 as well as for Helix Ultimate.

For Helix 3 templates you can find some of the patches under the following post.
https://www.joomshaper.com/forum/question/17313#qa-answer-83050

For the long loading times of the Helix Ultimate template, expired cache can be the cause.
Something like this was reported by another user.

Found a solution: delete expired cache. :-)

Helix Ultimate with SPPB 3.8 and Joomla 4

Important: I am not from Joomshaper Support and do this on a voluntary basis.

i think i have same problem with , i hope soon have an update for PHP 8

You guys are cutting it fine with this fix I would really like to know my site is secure moving forward
This is coppied from my joomla dashboard, it dosnt get much clearer to me.

'Your PHP version, 7.4.32, is only receiving security fixes from the PHP project at this time. This means your PHP version will soon no longer be supported. We recommend planning to upgrade to a newer PHP version before it reaches end of support on 2022-11-28. Joomla will be faster and more secure if you upgrade to a newer PHP version. Please contact your host for upgrade instructions.'

When is the fix due I need to go to at least PHP 8

Thanks that would very much appreciated

Me too.
I can't run PHP 7. It will be picked up on web scans.
:(

Yes Still waiting for UPDATE Site Security is becoming a very big concern
Please advise with a FIRM timeline
Thanks

@Toufiq
This Version still has incompatibilities.
system/helix3/core/helix3.php on line 641 to 655.
The arguments are in the wrong order and will throw an error when used with php 8.1.
https://github.com/JoomShaper/Helix3/pull/112/commits/079bb8f33d3c39b1c39ebc1d0bdb5f32da3e1a72

Please use the provided and tested fixes from github.
Furthermore, it would be great if the developers would set the repository to Archived when it is no longer maintained and serviced.
That the free developers can save the time to provide updates and bugs there.
Me, pepperstreet, RagdollOp, aranemac and so on

https://github.com/JoomShaper/Helix3/pulls
https://github.com/JoomShaper/Helix3/issues

When I find some time, I will check this version with PHP 8.1.
I will also check if the API calls work at the same time.

https://github.com/JoomShaper/Helix3/issues/114

I have now moved over to build a new site on the helix ultimate as I can't rely on the updates for the current site
So all work to date lost very frustrated and annoyed

Don't want to muddy the post but for reference I get this when using the front page editor.
The home page will then error with the same message and continue to state that error, until a cookie clear.

Does anyone know if this problem will be fixed soon? I cannot use front page editor with helix 3 on PHP 8. Going back to earlier PHP is not an option.

@sydk2017

Do you get an error message that could indicate the cause?
If not, you could switch on the debug mode, that you hopefully get an error message with stacktrace displayed.
Then I could possibly help you further and at least provide a patch that you can continue to work.

I have tried to add the debug message but it will not upload. i did not see anything called stacktrace.

Below I'll add the admin login if you want to check it yourself.

@sydk2017

I have tried to add the debug message but it will not upload.

Yes, that's because of Cloudflare. They filter the sent data.
If there is something that Cloudflare classifies as bad, the call is blocked.
If you try this too often, the IP of the user is even banned.

i did not see anything called stacktrace.

Yes, as a non-developer the terms can be confusing. :)
Stacktrace is a list of steps "files and functions" that were processed in order before the actual error occurred.

If in Joomla under "System -> Global Configuration -> System -> Debug" the item "Debug System" is activated, the stacktrace should also be displayed in case of an error.

If there is still no error to be seen, then it seems to be a problem of the SPPB.
This would have to be looked at by @Toufiq.

Below I'll add the admin login if you want to check it yourself.

That's very nice of you, unfortunately as a normal user I don't have access to the hidden content.

You can alternatively create an account for me.
E-mail: [email protected]

Hallo,
yesterday I installed a new quickstart pack joomla 4 (template yoga) and now I have exactly this error when I try to start the frontend editor. Have now also switched php 7.4, then it works again. Means probably that this error is still not eliminated. I paid over 100 euros for this.

@Toufiq
He has created a dedicated ticket/post.
https://www.joomshaper.com/forum/question/23493

Please help him there.
Here he would share or disclose his access data in the hidden content with the creator of the post.
This should not be done for safety reasons.

Have a nice day.

Hello.

Yesterday I installed a new quickstart pack joomla 4 (template yoga) and now I have exactly this error when I try to start the frontend editor. Have now also switched php 7.4, then it works again. Means probably that this error is still not eliminated. No one has been working on fixing this bug for over a year?

Regards