Solved Helix Framework

Error on Joomla 4.2 update

Asked by Olivier Frascone 4 years ago Last activity 4 years ago

Hi,
After updating to Joomla 4.2 we experiment on ALL sites using Helig Ultimate the following error :

Class 'Joomla\Plugin\Behaviour\Taggable\Extension\Taggable' not found

When debug is enable :

ClassNotFoundError
Symfony\Component\ErrorHandler\Error\ClassNotFoundError:
Attempted to load class "Helper" from namespace "HelixUltimate\Framework\Platform".
Did you forget a "use" statement for another namespace?

Thanks for your fix

Accepted answer

Marked as the solution

6 more replies

Olivier Frascone Asked this
4 years ago · edited

I disabled the following plugins to have it back working :

  • plg_behaviour_taggable
  • plg_behaviour_versionable
  • plg_actionlog_joomla
  • plg_system_schedulerunner

Hope it helps, i will try to isolate the problem but it seems to be a problem with Joomla 4.2 update.
Thanks for your answer

Paul Frankowski Senior Staff

So it's sort of Joomla bug?

Olivier Frascone Asked this

Hello Paul, yeah the problem was with the administrator/cache/autoload_psr4.php not being regenerated after update.
Do the upgrade, then manually DELETE this file -this allows the site to come online again and is then an up to date Joomla 4.2.0 with a regenerated autoload_psr4.php
Thanks.
Olivier

Paul Frankowski Senior Staff
4 years ago · edited

Thanks for details. Yesterday I was too tired to think clear.

Good Joomla tip for everyone here.

And information that is not Joomshaper bug this time ;] hahahha

blue_Shift
4 years ago · edited

deleting autoload_prs4.php did not work for me. I hade made an Akeeba copy of a development site running J 4.1.5 on the same server, and front and back end of the production site are both bricked.

Doesn't joomla test this stuff? I'm in the middle of a complete disaster.

blue_Shift
4 years ago · edited

I completely blew away the contents of the root folder, and reinstalled the akeeba - and now it's a website again. I am afraid to update Joomla at this point. Getting this particular project, a large one going back to 2011, into Konstra and then J4 has been an ordeal.

Log in to reply.