[4.2] Fix fatal error when update to Joomla 4.2 #37990

joomdonation · 2022-06-05T10:24:32Z

Pull Request for Issue # .

Summary of Changes

In Joomla 4.2, we convert some plugins to new structure, so the namespace map will need to be re-generated before avoid Joomla calls com_joomlaupdate to finalize upgrade process to avoid fatal error.

Testing Instructions

Install Joomla 4.1.
Try to Update that 4.1 website to Joomla 4.2 nightly build. During the update, you would get fatal error saying class Joomla\Plugin\Actionlog\Joomla\Extension\Joomla not found (something like that, I don't remember exactly the error message)
Install Joomla 4.1 again
Try to update to the update package generated for this PR. You can download the package from this link https://ci.joomla.org/artifacts/joomla/joomla-cms/4.2-dev/37990/downloads/54926/Joomla_4.2.0-beta1-dev+pr.37990-Development-Update_Package.zip . Make sure upgrade works properly

Actual result BEFORE applying this Pull Request

Fatal error while upgrading to Joomla 4.2

Expected result AFTER applying this Pull Request

Upgrade to Joomla 4.2 works well.

ChristineWk · 2022-06-05T10:58:15Z

@joomdonation
Confirm Actual Result. Updated from 4.1.4 to Nightly Build 4.2.0-beta1-dev.

An error has occurred. 0 Class 'Joomla\Plugin\Actionlog\Joomla\Extension\Joomla' not found

But now, Frontend and Backend are corrupted.
Can I solve it via phpMyAdmin somewhere (special Plugin Table)?

joomdonation · 2022-06-05T11:00:48Z

@ChristineWk You can delete the file administrator/cache/autoload_psr4.php manually to get the site running again. However, to test the PR, you will need to setup another Joomla 4.1 website. The purpose is confirming upgrading to new package won't get fatal error anymore

ChristineWk · 2022-06-05T11:22:01Z

@ChristineWk You can delete the file administrator/cache/autoload_psr4.php manually to get the site running again. However, to test the PR, you will need to setup another Joomla 4.1 website. The purpose is confirming upgrading to new package won't get fatal error anymore

OK, Done. Thanks for the hint :-)
It shows now: 4.2.0-beta1-dev and: Database: 4.1.3-2022-04-08: After this: DB updated.
Another 4.1 I don't know yet.

brianteeman · 2022-06-05T11:52:28Z

From what I remember that cache file is supposed to be deleted and rebuiult during the update process

brianteeman · 2022-06-05T11:58:56Z

found it #36094

joomdonation · 2022-06-05T13:27:34Z

@brianteeman That PR only solved the issue when new extensions are added during update process (like Schedule extension which we added in 4.1). For 4.2, we converted some plugins to new structure, so the namespace map must be re-generated earlier than that, otherwise, after the extraction process, we will get fatal error immediately and the upgrade could not be completed.

richard67 · 2022-06-05T14:58:47Z

I have tested this item ✅ successfully on 7aaebc4

Hint for other testers: For updating to the 4.2-dev nightly build without the patch (step 2 in the instructions), I had to download the update package from here https://developer.joomla.org/nightly-builds.html and use "Upload & Update" because the update site XML for the 4.2-dev nightlies contains a wrong download URL. See joomla/update.joomla.org#250 .

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

administrator/components/com_joomlaupdate/finalisation.php

toivo · 2022-06-06T03:53:27Z

I have tested this item ✅ successfully on 7aaebc4

Confirmed the error message and tested successfully in Wampserver 3.2.9 and PHP 8.0.15 using the update package created for this PR.

#
#<?php die('Forbidden.'); ?>
#Date: 2022-06-06 03:43:55 UTC
#Software: Joomla! 4.1.4 Stable [ Kuamini ] 24-May-2022 16:00 GMT

#Fields: datetime	priority clientip	category	message
2022-06-06T03:43:55+00:00	INFO 127.0.0.1	update	Starting installation of new version.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Finalising installation.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Start of SQL updates.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	The current database version (schema) is 4.1.3-2022-04-08.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Ran query from file 4.2.0-2022-05-15. Query text: CREATE TABLE IF NOT EXISTS `#__user_mfa` (   `id` int NOT NULL AUTO_INCREMENT,  .
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Ran query from file 4.2.0-2022-05-15. Query text: DELETE FROM `#__postinstall_messages` WHERE `condition_file` = 'site://plugins/t.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Ran query from file 4.2.0-2022-05-15. Query text: INSERT INTO `#__extensions` (`package_id`, `name`, `type`, `element`, `folder`, .
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Ran query from file 4.2.0-2022-05-15. Query text: UPDATE `#__extensions` AS `a` 	INNER JOIN `#__extensions` AS `b` on `a`.`element.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Ran query from file 4.2.0-2022-05-15. Query text: DELETE FROM `#__extensions` WHERE `type` = 'plugin' AND `folder` = 'twofactoraut.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Ran query from file 4.2.0-2022-05-15. Query text: INSERT IGNORE INTO `#__postinstall_messages` (`extension_id`, `title_key`, `desc.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Ran query from file 4.2.0-2022-05-15. Query text: INSERT IGNORE INTO `#__mail_templates` (`template_id`, `extension`, `language`, .
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	End of SQL updates.
2022-06-06T03:44:15+00:00	INFO 127.0.0.1	update	Deleting removed files and folders.
2022-06-06T03:44:19+00:00	INFO 127.0.0.1	update	Cleaning up after installation.
2022-06-06T03:44:19+00:00	INFO 127.0.0.1	update	Update to version 4.2.0-beta1-dev+pr.37990 is complete.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

richard67 · 2022-06-06T06:52:20Z

RTC

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

roland-d · 2022-06-06T13:16:25Z

Thanks everybody

shortyloz · 2022-08-16T21:14:14Z

I have a related issue maybe?

I have removed the file suggested above "@ChristineWk You can delete the file administrator/cache/autoload_psr4.php manually to get the site running again. However, to test the PR, you will need to setup another Joomla 4.1 website. The purpose is confirming upgrading to new package won't get fatal error anymore" But that has not solved my issue.

Any suggestions : Live site is at this URL (I also stupidly did not do a backup!)
https://www.cheshuntrpc.co.uk/

Thanks
Numpty Mark from UK

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

shortyloz · 2022-08-16T21:22:28Z

Thanks PhilETaylor. Where do I do that please?

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

shortyloz · 2022-08-16T21:25:54Z

Sorry, I didn't know I was in the wrong place. I will do that as suggested and also look there. :-)

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

rkostanyan · 2023-02-21T12:58:26Z

Dears, I have new problem, please help
Class "Joomla\Plugin\Authentication\Joomla\Extension\Joomla" not found

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

joomdonation · 2023-02-21T13:16:44Z

@rkostanyan Try to delete the file administrator/cache/autoload_psr4.php from your site. That should address the issue.

rkostanyan · 2023-02-21T13:24:16Z

Problem is not resolved:(

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37990.}

joomdonation · 2023-02-21T13:28:49Z

@rkostanyan If so, I don't have any other idea. You might need to have a developer to look at your site to see what's actual reason and get it sorted. Without accessing to your site, it's hard to know the root reason of the error

Fix fatal error when update to Joomla 4.2

7aaebc4

joomdonation requested review from rdeutz and zero-24 as code owners June 5, 2022 10:24

joomla-cms-bot added the PR-4.2-dev label Jun 5, 2022

richard67 added the Release Blocker label Jun 5, 2022

richard67 reviewed Jun 5, 2022

View reviewed changes

administrator/components/com_joomlaupdate/finalisation.php Show resolved Hide resolved

joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Jun 6, 2022

Merge branch '4.2-dev' into fix_fatal_error_on_upgrade_to_4.2

923f94d

roland-d merged commit 4046858 into joomla:4.2-dev Jun 6, 2022

joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Jun 6, 2022

joomdonation deleted the fix_fatal_error_on_upgrade_to_4.2 branch June 6, 2022 13:26

roland-d added this to the Joomla 4.2.0 milestone Jun 6, 2022

richard67 removed the Release Blocker label Jun 12, 2022

This comment was marked as abuse.

Sign in to view

joomdonation mentioned this pull request Aug 17, 2022

4.0.0 to 4.1.5 upgrade path now also broken - Call to undefined method UpdateModel::isTemplateActive() #38486

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[4.2] Fix fatal error when update to Joomla 4.2 #37990

[4.2] Fix fatal error when update to Joomla 4.2 #37990

joomdonation commented Jun 5, 2022 •

edited by richard67

Loading

ChristineWk commented Jun 5, 2022

joomdonation commented Jun 5, 2022

ChristineWk commented Jun 5, 2022

brianteeman commented Jun 5, 2022

brianteeman commented Jun 5, 2022

joomdonation commented Jun 5, 2022

richard67 commented Jun 5, 2022 •

edited

Loading

toivo commented Jun 6, 2022

richard67 commented Jun 6, 2022

roland-d commented Jun 6, 2022

This comment was marked as abuse.

shortyloz commented Aug 16, 2022

This comment was marked as abuse.

shortyloz commented Aug 16, 2022

This comment was marked as abuse.

shortyloz commented Aug 16, 2022

rkostanyan commented Feb 21, 2023

joomdonation commented Feb 21, 2023

rkostanyan commented Feb 21, 2023

joomdonation commented Feb 21, 2023

[4.2] Fix fatal error when update to Joomla 4.2 #37990

[4.2] Fix fatal error when update to Joomla 4.2 #37990

Conversation

joomdonation commented Jun 5, 2022 • edited by richard67 Loading

Summary of Changes

Testing Instructions

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

ChristineWk commented Jun 5, 2022

joomdonation commented Jun 5, 2022

ChristineWk commented Jun 5, 2022

brianteeman commented Jun 5, 2022

brianteeman commented Jun 5, 2022

joomdonation commented Jun 5, 2022

richard67 commented Jun 5, 2022 • edited Loading

toivo commented Jun 6, 2022

richard67 commented Jun 6, 2022

roland-d commented Jun 6, 2022

This comment was marked as abuse.

shortyloz commented Aug 16, 2022

This comment was marked as abuse.

shortyloz commented Aug 16, 2022

This comment was marked as abuse.

shortyloz commented Aug 16, 2022

rkostanyan commented Feb 21, 2023

joomdonation commented Feb 21, 2023

rkostanyan commented Feb 21, 2023

joomdonation commented Feb 21, 2023

joomdonation commented Jun 5, 2022 •

edited by richard67

Loading

richard67 commented Jun 5, 2022 •

edited

Loading