-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assets not registering on FE #176
Comments
How are the asset bundles being generated? Can you show the code of your injected template? I'm not sure if this is related, but note that a limitation of injecting the result of an AJAX request into HTML is that any script tags will not be executed. This may have adverse effects on injected content that includes JavaScript code to be run. |
They're added by the plugin using Our include is super simple, and doesn't register the asset bundle itself directly.
Ref your second point, we've made use of your |
Just ran some tests and I see that the asset bundles are indeed not returned when using I know that @lindseydiloreto has been adding cache-proofing to his plugins lately and have asked him if Ad Wizard might get an update soon. |
Ah yes, of course. I did have a request open over at the repo for this doublesecretagency/craft-adwizard#9, I guess this is more an adwizard issue than a Blitz issue, as this is just how Blitz works? |
Yes, the way you've manually hooked it up on the front-end is probably your best bet for now. |
Describe the bug
We are using Blitz Cache to import our include that loads a plugin called adWizard
{{ craft.blitz.getTemplate('ism/includes/_adwizard') }}
. The include is pretty much some divs and the init for adWizard i.e.{{ craft.adWizard.randomizeAdGroup('leaderboard') }}
However, it's not registering the asset bundles correctly on the front end. If I default back to the standard
{% include %}
tags the assets get loaded in correctly, so I can only assume Blitz is doing something weird when it runs thegetTemplate
code.Thanks!
To reproduce
Steps to reproduce the behaviour:
getTemplate
Expected behaviour
Assets to be registered on the front end
Versions
The text was updated successfully, but these errors were encountered: