Support

Hello,

just to double check: do you have Akeeba Engage installed?

Ok that makes sense: Engage 2 is built on FOF. The latest version includes FOF 4.1.0. When FOF 4.1.0 detects that it's not used by anything (per the DB information) and it's under Joomla 4 it automatically uninstalls itself. If this happens and Engage is installed you will get an error.

Delete the plugins/system/engage folder, log into the backend and upgrade to Engage 3.0 released this early afternoon our time. Akeeba Engage 3 does not use FOF, it uses Joomla 4's core MVC.

Finally, all our software under Joomla 4 does not use FOF anymore, but only core Joomla features; you can find more details in this announcement https://www.akeeba.com/news/1747-joomla-4-is-around-the-corner.html

Please rename plugins/system/backuponupdate to its normal name. Akeeba Backup 9 DOES NOT use FOF. This plugin is unrelated to your issue. Renaming it and forgetting to change its name back will cause update issues when Joomla 4.1 is released next month.

Regarding FOF, you can follow the manual workaround.

Download its ZIP file.

Extract it on your computer.

Rename the folder fof to fof40

Upload the fof40 folder into your site's libraries folder so now you have a libraries/fof40 folder

Whatever was using FOF 4 will continue working

Download and install Akeeba Engage 3.0.1 WITHOUT uninstalling your existing version.

Install the FOF 4.1.0 ZIP file you have already downloaded. Now that it's no longer needed it will uninstall itself. If it doesn't, uninstall it manually. You should not have any other extension using FOF 4 on your site. The only other extension of ours using FOF 3 on Joomla 4 is Akeeba Ticket System and that's only until we release Akeeba Ticket System 5 next week which uses core Joomla MVC. After that there will be no Joomla 4–only extension of ours using FOF anymore. As we announced in August, FOF will be retired.

The error message about the WebAuthn plugin does not tell me anything because you did not give me the most important part of it: the actual error message. The file you are referencing is a core plugin in Joomla 4. The line it's referencing is just the start of its code (the class declaration). Without knowing the actual error message I can't make heads or tails of it. If it's something like class not found delete the administrator/cache/autoload_psr4.php file. This is an internal cache of extension class names to filesystem paths maintained by Joomla. If it gets borked you get weird errors about missing classes. Deleting that file will cause Joomla to create it afresh. Creating this information afresh is a bit slow (about half a second) which is why this file gets cached; it saves a lot of page load time.

Regarding the other issues, please try this dev release:  Version 3.0.2-dev20220106120 It should fix both issues.

You can use that dev release on both of your sites.

Regarding FOF, do install version 4.1.1 (it's 4.1.1, not 4.0.11, there was never a 4.0.11 version — we went from 4.0.9 to 4.1.0 to 4.1.1). I have removed the code for automatic uninstallation on Joomla 4 from FOF 4.1.1. There are too many screwed up sites out there. I will re–enable that code in 2023 when FOF will become end of life.

New features will be implemented in version 3.1.0. The main goal here was to make this extension Joomla 4 native.

I will be focusing on releasing Admin Tools 5 for Joomla 4, finally converting our own site to Joomla 4 and then start working on new stuff, always giving priority to paid software (gotta pay the bills!). Joomla 4.1 will be out in February and I will need to rework all our scheduled tasks to use its new CRON system which I expect will take a lot of research over months.

So... new features for Engage should be expected around summer at the earliest. I can't keep working 60–70 hour weeks. I've been doing that for two years. It's not healthy.