Staff replied Templates

WebAssetManager is locked, you came late

Asked by Hugh 3 years ago Last activity 3 years ago

I realise this hsa been asked a few times, but I can't see an answer.
This is a website which was originally built in J3 and is now being migrated to J4
The template is Helix Ultimate which has been updated to the latest version 2.0.15
There are other extensions installed including Regular Labs modules anywhere.

The problem however does seem to be isolated to the Helix Ultimate template. If I change template, the error goes away.

With the help of debug I can see that the issue arrises when jQuery is loaded

5 replies

Oldest first Newest first Most helpful
Toufiq Senior Staff
3 years ago

Hi there,

I appreciate you reaching out. I sincerely apologize for this oversight. Will you please provide me the Joomla administrator access to check the issue? I will check & get back to you soon. 

-Thanks

Hugh Asked this
3 years ago

Hi Toufiq many thanks for reaching out, hidden details contains the access details. I have loaded a few of your other templates which do seem to work (but are not quite the same). it is really Helix Ultimate that I need to get working.

Hugh Asked this
3 years ago

Toufiq
Thank you for your help, however that doesn't work since the pages are built using modules imported with modules anywhere. I know we are in a situation where the problem is between your template and this plugin, but the reality is that any other template works with modules anywhere turned on. What I have discovered is the failure (locking) appears to be on the load of jQuery, does that give any clues?

thanks
Hugh

Toufiq Senior Staff
3 years ago

I have enabled again your modules of anywhere & it works fine.

Hugh Asked this
3 years ago

Thanks, I have move a way forward since my last post. The reason it now works is because I turned off most of the modules, it seems there is 1 or just a few modules which cause this. I will continue investigating and post the results back here, hopefully others can benefit from a solution

Toufiq Senior Staff
3 years ago

Sure, Your cooperation will help others. Thanks

Hugh Asked this
3 years ago

SOLVED:
This may be of use to others, I have now tracked down the issue:

It is caused when using RegularLabs Modules Anywhere plugin, but it is not that plugin directly. If you have a custom module which then attempts to load another module through {module nnn} where nnn is the ID of the module you are calling. You need to set Prepare Content to YES in the wrapper module (the one with the plugin call). without this, expect to get the error message.

Toufiq Senior Staff
3 years ago

Thanks for the nice explanation. Have a nice day <3

Log in to reply.