Update: if I activate the joomla system cache, the whole site is not visible, with the error message "WebAssetManager is locked"

Hi Daniele,

In Helix Ultimate we don't have such a fuzzy messages like:

(..) WebAssetManager is locked, you came late.

Forum Joomla: https://forum.joomla.org/viewtopic.php?t=994191

also found: https://regularlabs.com/forum/modulesanywhere/49465-webassetmanager-is-locked,-you-came-late

UPDATE:

Probably it may be conflict with extra extension with template somehow. Becuase error is generated by Joomla 4 error system.

If you have too many extensions from Regular Labs - it may be one of them. But on the forum I cannot fix it. It request deeper investigation. By now just check what extra extensions you have, disable all and check, later you can share list.

Hi Paul, the error "0 WebAssetManager is blocked, you are late" when trying to preview Helix disappears if you disable Regular labs' free "Module anywhere" plugin. How to resolve the conflict?
Instead, the error "0 WebAssetManager is blocked" which prevents the site from loading when the Joomla system cache is set to "Yes" does not seem to depend on the Regular labs extensions (and does not occur with other templates). The error persists even when those extensions are disabled.
Let me know if I need to provide credentials for accessing the backend to review the installed extensions.
Thank you!

I presented the problem to the developer of Modules anywhere and this was the answer:

"Seems to me to be something specific to the Helix template. It doesn't happen on the core template. And the moments Modules Anywhere is normally triggered (and loads modules that can potentially load media through the WebAssetManager) is done at normal stages in the rendering process. So my best guess is that the Helix template is doing so, mething a bit funky. I recommend you ask them about it."

So partialy I guess where the problem was.

Fix won't be so fast as you probably wish, sorry. But I hope template preview can wait.

Yes, I added to bug list.

The template preview can wait, of course. It makes me more concerned about the total inability to open the site if I activate the Joomla system cache. Hope you can fix that problem too, by covering the same error "0 WebAssetManager is blocked"! Thank you!

total inability to open the site if I activate the Joomla system cache.

Can you share details (screenshots, video?), I cannot reproduce that issue. Becuase cache do not damage template is only keeps design views in /cache foler.

1. set the Joomla system cache to "Yes - moderate unique cache" (screenshot 1);
2. verify that the site is unreachable (error message: "0 WebAssetManager is locked" - screenshot 2);
3. set the system debug to "Yes" to see the error log (screenshot 3); as you can see, it would still seem a conflict with Regular labs Module anywhere, but disabling the related plugin the problem is not solved. Problems do not occur with other templates (Cassiopeia and LT News).

Thanks, shared info with our developer.

Hi again,

1. do you have this same problem also in Joomla 4.2 with Helix Ultimate 2.0.11?
2. what is "moderate unique cache"? in Joomla there are different names, convervative and progresive.
3. can we get access for one day? or at least please make a video and share link to it.

we are making deeper investigation of that issue for next helix update.

1. On the advice of the developer of Relular labs, I recently set to "Yes" the parameter "Interpreta codice pugin" (Interpret plugin code, as it is written in Italian) of the "Options" tab of the custom modules published on the home page. In this way, the preview of the template is displayed and the error with the cache no longer occurs. However, they are in the testing phase. If the problem still arises, I will not hesitate to write
2. In the italian translation of the Joomla 4 backend, the options for the cache in Global Configuration -> System are: No - cache disabled Yes - moderate unique cache Yes - progressive multiple cache At the moment, however, it appears that the problem does not occur.
3. If necessary, as has happened in the past, I will gladly provide the credentials. For the moment it does not seem necessary.

Thank you, Daniele

Hi and thank you very much for your availability. I confirm that the problems reported in this thread seem to have been solved, after the joomla update to version 4.2.2, of Helix Ultimate to version 2.0.11 and after the application of what reported by the Regular labs support. So I don't think there is a need for further action, at least for the moment. If other malfunctions occur, I will come back to write to you. Thanks again, Daniele