There is an error by JCH Optimize when it compresses all the scripts on the site. This is causing the registration to malfunction. As soon as I turn off JCH Optimize everything works.

Can you give this a try again now? I have turned off JCH Optimize.

Thank you, it goes again. But unfortunately, the site is very slow. Is there a solution?

I would suggest that you update to EasySocial 2.0 We have reduced javascript file size by almost 30%.

You should instead use pagespeed to compress and serve script files instead of JCH. JCH Optimize are very prone to errors because it basically collects every single script on the page and store them on a single file.

What happens when there are errors produced by other script files? The whole codes would not get executed.

The update is still done. I wanted to wait for the first patch.

Is there any problem with the extension: Aimy Speed Optimization? https://www.aimy-extensions.com/joomla/speed-optimization.html

I would like to switch to the next payment update to the bundle version, since I use pretty much all extensions of you.

Is it planned in the future fie the bundle version to create a common CSS & Java script file?

That would spare some servers to spare.

Ps .: With the MetaMan extension, the memory is hidden by the menu. Could this be brought forward times. Or should I therefore open an extra ticket again?

Hm, I have not tried Aimy Speed Optimization but I would suggest that you look into pagespeed. Our demo site only runs on:

1. Pagespeed
2. CDN


As for the Metaman issues that you have, please create a new ticket on our forums

Hi

so what you mean is that JCH Optimize doesn't work with EasySocial 2? Thats a pity bcs that optimization plg is really great for many optimizations for your other Joomla components modules etc.

Is there not any css and js for EasySocial that could be in JCH Optimize exlude list that would make EasySocial 2 also work with JCH Optimize? You add this inside JCH Optimize settings..

rgds

It really depends, because what JCH Optimize is doing behind the scenes is compiling all the scripts on your site and compressing them into 1 single file.

If your site has modules, plugins, extensions that renders scripts of their own and has errors, JCH Optimize also collects these errors and place them into the same file.

Then it depends on the ordering, if the errors are towards the end of the file, you are safe. If it is at the early portion of the file, it becomes extremely tricky because when there is an error on the file, the browser will stop execution the remaining codes in the file.

Yep, Pagespeed is definitely the way to go If you have CDN, it's even faster! Because your assets files are hosted in a CDN pop server which serves these files to the nearest location of your visitor!