Support

I don't think these events are related. We only changed a single line compared to FOF 4.0.8. Namely, we simplified an if–block so that it works as it did before, without the possibility of misfiring under CLI.

I visited the first URL you sent me and your site looks just fine.

The second URL you sent me returns a 404. The correct URL seems to be https://www.monkey-security.de/kontakt/kontaktformular Regardless, what FOF 4 changed cannot have any bearing to your site's layout. In fact, I can see that your problem is completely unrelated to our software. It's caused by the third party CSS and JS minifier (JCH Optimize) you are using on your site. It minifies the JavaScript improperly, causing the Fox object not to be defined before it's attempted to be used. JCH Optimize IS NOT an Akeeba product and DOES NOT have anything to do with FOF 4.

I suspect that you may have updated or reconfigured this third party extension at the same time as FOF 4 which is why you are wrongly blaming the FOF 4 update for an issue unrelated to it.

Both problems (Admin Tools and Akeeba Backup) would happen because of JavaScript issues. We know that as shipped our components do not have any such issues. So you either need to clean your browser's cache or, if that doesn't help, you need to find which third party extension is causing a JavaScript issue on the page which prevents our JavaScript from running.

You're welcome!

I have been bitten by minifiers before. The problem is that you need to know in which order to minify things and which things to not minify at all. JavaScript can be loaded in the head of the page (blocking), asynchronously (anytime during the page load) or deferred (after the browser has built the DOM). Extensions which put the JS at the head of the page know that it's being loaded in a blocking manner, therefore any inline head or body JavaScript can access it by definition. Minifiers will typically combine all JS files and load them asynchronously or deferred, breaking this assumption and causing a multitude of problems.

Sure, there are ways around that but they require intimate knowledge of how the JS on your site works. I have created a plugin for my own use, Combinator, which allows this kind of fine–grained control. I wouldn't really recommend it unless you are a hardcore developer who understands everything about how JavaScript works on your site.

Joomla 4 fixes that problem by supporting deferred loading of JavaScript, EcmaScript 6 modules and dependencies. A native Joomla 4 extension written using the Joomla 4 best practices and conventions will not have any blocking JavaScript and make your site faster. The Joomla core already does that and so do our native Joomla 4 extensions. That's why page loads are so staggeringly fast on Joomla 4. I expect it will be another 1–2 years before the bulk of extension developers catch up with the One True Joomla 4 Way of using JavaScript, allowing you to have very fast sites with near–100 Lighthouse scores and the associated benefits for search engine rankings.