Helix Ultimate Plugin UpdateCrashes Joomla 3.x (yes I Know It is EOL) - Question | JoomShaper
Black Friday sale is live with flat 50% OFF. Sale ends soon! Grab your deal now!

Helix Ultimate Plugin UpdateCrashes Joomla 3.x (yes I Know It is EOL)

R

Rvdzande

Helix Framework 3 weeks ago

Running a few legacy sites which are about to be stopped because the projects are halted. Organisations just need them for regulatory reasons till the they can abandonded.

This is when I discovered the lastest Helix Ultimate Plugin crashes Joomla 3.x

Error backend (can't log in): 0 Call to undefined method Joomla\CMS\Factory::getContainer()

Error frontend 'error'

Workaround:

  • deleted plugin via FTP
  • uploaded older plugin

Seams to work for now!

I can imagine you will not be supplying a fix since Joomla 3.x is EOL, still mentioning this here so the issue is at least known.

0
5 Answers
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 3 weeks ago #208328

This is when I discovered the lastest Helix Ultimate Plugin crashes Joomla 3.x

info_3420_2025.jpg

Yes, You are using Joomla 3 on your own risk, and I don't recommend updating anything if you are not 100% sure, that new version is for current Joomla version only.

Good tip! Read extension changelog BEFORE you will decide to update anything on J3 sites. Just treat J3 as an old car where you have to use only old parts. Okay?

Hopefully, you had old plugin version.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 3 weeks ago #208315

Hello Rvdzande,

Sorry for the inconvenience you're experiencing. Please check the technical requirements for Helix Ultimate 2.2.x at www.joomshaper.com/documentation/helix-framework/introduction#technical-requirements. As mentioned there, it's no longer supported for Joomla 3.

Best regards

0
R
Rvdzande
Accepted Answer
3 weeks ago #208342

I rather throw it away and I understand why this decision was made.

0
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 3 weeks ago #208358

In last HU updates we focused to improve code according to PHP 8.4 and J6, so those changes are not needed for J!3 that even cannot use PHP 8.4 or 8.3 without long list of errors.

Maybe hire somebody who will upgrade/migrate your sites to J5x , otherwise one day, Russian Hacker bot may come and ... infected site or broken site. I have seen it too many times.

0
R
Rvdzande
Accepted Answer
3 weeks ago #208374

Sorry my answer was maybe a bit unclear. Shouldn't do two things at once while replying.

It should be: I rather throw the sites away :) I understand why the decisions was made

0