Error On Joomla 4.2 Update - Question | JoomShaper
Back to the questions

Error On Joomla 4.2 Update

Olivier Frascone

Olivier Frascone

Helix Framework 1 year 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

0
7 Answers
Order by
Oldest Newest Votes
Olivier Frascone
Olivier Frascone
Accepted Answer
1 year ago #79966

And finaly the fix for people who have same problem : https://github.com/joomla/joomla-cms/issues/38474

0
Olivier Frascone
Olivier Frascone
Accepted Answer
1 year ago #79963

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

0
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 1 year ago #79970

So it's sort of Joomla bug?

0
Olivier Frascone
Olivier Frascone
Accepted Answer
1 year ago #80009

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

0
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 1 year ago #80019

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

1
B
blue_Shift
Accepted Answer
1 year ago #86420

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.

0
B
blue_Shift
Accepted Answer
1 year ago #86422

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.

0