Hi, I installed fresh joomla and latest helix ultimate.
When i change template from casiopeia to helix ultimate i got message:
Sorry, there was a problem we could not recover from.
The server returned a "500 - Whoops, looks like something went wrong."
Best regards
Hi Nikola,
what PHP version?
It should work totally OK in PHP 7.4 and PHP 8.0.x,
as I see everyday many users here have Helix on J4.
Hi, It was 7.3, but I changerd to 8.0.
Same thing
Then I installed Helix ultimate quickstart, and it work fine, except when I click on Edit Page at template, same bug is shown.
Hmm?
Do you have installed any extensions?
or as you said only clean Joomla and Helix?
I have same issue, instealled clean version of Joomla v4.1.5 and Helix Ultimate v2.0.10, and I get this error when going to the shaper helix template: "InvalidArgumentException: Please specify a valid response format, other than that of HTML, such as json, raw, debug, etc."
thankfully i have a helix ultimate older version v2.0.8 and installed that, and the template works again.
I dont understand there is like no bug dev tracker for joint efforts here for Joomshaper bcs the bugs are always popping up I just wonder what testing you do for php 8.1 etc before relasing HU and SP Pagebuilder Pro
Well hope you step up and get things to work well in future
all the best!
Hmm?
Do you have installed any extensions?
or as you said only clean Joomla and Helix?
Yes, just clean joomla and helix ultimate.
1.) Linux
2.) Install Helix Ultimate v2.0.10 Template
3.) no errors in service logs Only successful installions
after installing v2.0.10 plugin package
thanks for access, I will ask developer to check it.
On my two servers I couldn't reproduce that error, it was OK with PHP 7.4 and PHP 8.0x.
Please switch to PHP 8.0 , and let me know after.
PHP 8.1 is not supported yet!!
thanks, we have set the php to 8.0.20, reinstalled the v2.0.10 template and plugin and received the same error
when i install helix ultimate template and plugin v2.0.8 - everything seems to work as expected.
Joomshaper pls investigate fix this bug asap with new release.
Thks.
I just installed
No issue. Everythinh is working normal.
Did you you actiivate htaccess? Or an other component?
Paul when can we expect support for php 8.1 series? php 8 was released 26 Nov 2020 and then php 8.1 25 Nov 2021 so you should have plenty of time to test for more than 7 months now and make HU and SP Pagebuilder to work with latest php 8.1.
It shouldnt be to much to fix it work with both php 8.0 and 8.1 I guess.
Pls kick the developers butt and fix this now..
Cheers!
Next Helix update should be in next weeks, we have to make PHP 8.1 tests and probably fix small issues.
Suring the weekend our developer do not work, so I cannot ask him for help.
If old HU 2.0.8 works for you - install & keep that version by now.
I have the same issue. The instructions were missing the plugin ... I added this by fluke. I get the same screen as anfini.
@Tim
If you need older Helix Ultimate 2.0.9 template to test , you can download from here
it should work without Error 500 on Joomla 4.1.5
We have to make investigation why in some cases HU 2.0.10 generate error page, and make fix update.
I had an identical problem, but found that the helix plug-in was not automatically enabled on installation. Enabling it got past the 500 error, and while it loads a functional page, does not load the proper template. Will open a new thread on that one.
@SonicShock - weird, by defaut it should be Enabled, it has that rule inside template package. But if you installed only Helix plugin Joomla may not enabled it, becuase of Joomla safe rules. But that one we cannot change. But if installed before Helix pligin was enabled, updated version do not disable it.
Paul, thank you for expanding my understanding of all this. I did several iterations actually - plug-in first, then template, then the reverse (does the template automatically install the plug-in? I honestly can't remember, it being a while since I've created a site from scratch, and this time did so many iterations I lost count.) Whatever, once the problem was identified, the fix is is dirt simple & quick.
You had luck. Hopefully it was only reinstall problem.
BTW
Today we had similar problem after user changed PHP from 7.4 to 8.0 but after 30 minutes problem gone without any hacks/help.
Important!
If you notice similar problem after update (or whatever) before panic and using older version please check if "System - Helix Ultimate Framework"
plugin is enabled, this is necessary.
Not used Helix3 plugins can be disabled.
I also have this issue on Joomla 4.1.5 clean install and Helix 2.0.10 the template options button does not appear and home page gets 500 page error if you set it to the default template. Looked in Plugins and "System - Helix Ultimate Framework" plugin does not exist?
Hi Paul,
look under extensions? search for helix?
also, other Paul, i did this again, and i indeed was needed to turn on helix, but the navigation was still missing.. nonetheless.. im just using v2.0.8 helix ultimate and no issues with that one.
yeah you can wonder when this extreme complex issue will be fixed? Before or after Nigeria send a man to the moon..you guess.
I had previously only ever downloaded and installed the template, but however I have just for the first time downloaded the plugin and installed and activated it, and this now appears to have resolved it.
Infini....if I'm correct, your Helix template came up, but it's blank....ie no navigation menu? I had this happen as well, and it was simply a case of going to the template options and turning these functions on. Previously when I've installed the Helix template, a number of options for the header, footer, and menu were turned on by default. Didn't happen this time.
@SonicShock
Templates are always blank. For beginners we have QuickStart with demo content.
Of course if different template used this same module positions you could have some content from old site.
In Joomla there is "Discover" feature if somehow even after full template package you do not see all parts from it. It allows you to find not found extensions, for example, plugins.
