Hello

Apologies for the inconvenience. Could you kindly mention which template and PHP version are you using, please? Also, kindly do not use SP Page Builder 4 directly on production sites for safety reasons. First, test it on a staging site. You can follow the link below to create a staging site: https://www.joomshaper.com/forum/question/16053

You can check this link too: https://www.joomshaper.com/forum/question/17120

Template: https://www.joomshaper.com/joomla-templates/rhino PHP version: PHP 8.0

Could you try downgrading your PHP please? Kindly check the technical requirements for the Rhino template in the documentation link below:

https://www.joomshaper.com/documentation/joomla-templates/rhino/technical-requirements

If I may....

DELETE that file:

templates/shaper_rhino/html/mod_login/default.php

It's becuase Joomla 4.2 made some code changes, added Multi-Factor Authentication that replaced Two-Factor Authentication that was before in Joomla 4.1.x

@ Paul,

That did not work.

@ Ariba,

I was running PHP 7.3 and still received the error.

Upgraded to PHP 8 and the same error occured.

Hello Morgan Baggs,

I am not from support, but I already know the problem.
I have already provided a patch for this.

https://github.com/JoomShaper/Helix3/pull/112/commits/079bb8f33d3c39b1c39ebc1d0bdb5f32da3e1a72

If you make these adjustments in your "plugins/system/helix3/core/helix3.php" file, the error should be gone.

To be on the safe side that it is indeed the same problem, please trigger the error once with debug mode enabled.
You should then know the exact files that triggered the error and where exactly.

For this Joomla should generate a display with the text "Call Stack" in debug mode.

You activate the debug mode via: System -> Configuration -> System -> Debug Settings -> Debug System

If it is not fixed by this patch, please let me know the message generated by Joomla with enable debug mode.
So I can reproduce the problem and provide a solution for you.

With kind regards

I really can't understand how this has not been fixed yet??? I used to love you're products but I am affraid I need to look elsewhere now. I have a bunch of sites displaying the same errors and and bunch of irrate (and rightly so) clients. Downgrading to PHP 7, is not an option for me, it has been remove from by service provider.

Is Helix 3 compatible with PHP 8 or higher? Please answer this with a YES or NO.

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

December 12th, 2024

@Martin. How I can help, if you didn't share any details!?

13 Dec 2024, I close that topic, NEW ONE PLEASE.