[#38647] - No Migration from twofactorauth to multifactorauth in Joomla 4.2.1
- Closed
- 4 Dec 2022
- Urgent
- Build: 4.2.1
- # 38647
Joomla 4.2.x Updates delete the twofactorauth plugin directory and creates an new multifactorauth directory. But the extension database will not be updated. It is not possible to delete the old extension-entries for plg_twofactorauth_totp and plg_twofactorquath_yubikey within the backend (only direct in database). The new multifactor plugins must be installed via the Backend com_installer | View=discover.
Would it be possible to update the database with the update?
Votes
| Labels |
Removed:
?
|
||
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
I upgraded first to 4.2.0 with the Joomla_4.2.0-Stable-Full_Package.zip because the automatic update was not available. I was not using the Update-Package. Perhaps that was the mistake?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38647.
My question is Exactly how did you upgrade?
@hsm-berlin What @brianteeman and me would like to know is whether you have used the upload button of the Joonla Update component to update, which would result in a normal update taking place, including the execution of database updates, or if you just have uploaded and unpacked the zip package without using the Joomls Update component, which would mean the database updates are not run, and the result is a messed up site which you better revert to the state before the update with use of a backup which you hopefully have made before the update.
I used /administrator/index.php?option=com_joomlaupdate&view=upload with the Joomla_4.2.0-Stable-Full_Package.zip
No idea why the databases have not been updated. With Joomla 4.2.1 the automatic update is available and the databases will be updated.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38647.
For me it's the same.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38647.
I understand the last comment by @hsm-berlin that the issues is solved and maybe triggered by using the wrong (none) update package.
I'm closing this.
@spamzini please provide additional information if you still have the problem.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-12-04 09:53:14 |
| Closed_By | ⇒ | HLeithner |
Sounds like you did not update joomla using the joomla update component?