-
1. Re: BC.Next Caching With Content Holders and Includes
They are different things Lynda, you do not cache them, they are server rendered elements. Wrong thinking Lynda
-
2. Re: BC.Next Caching With Content Holders and Includes
I am sorry, I wasn't clear at all. Scripts, CSS and images WITHIN content holders and includes do not have the appended tag as other files do.
-
3. Re: BC.Next Caching With Content Holders and Includes
Ok, gotcha.
That will probably be a bug, but I suspect it is because how those render, so it would need a bit to fix I think.
-
4. Re: BC.Next Caching With Content Holders and Includes
I hope they do fix it sooner rather than later because I use content holders and now includes to manage scripts, css and images with templates. Makes like so much easier!
-
5. Re: BC.Next Caching With Content Holders and Includes
How do you think pestered them the most to get includes in?
-
6. Re: BC.Next Caching With Content Holders and Includes
Hmmm, I wonder. =>
I have no doubt that you do and thank you for the pestering that you do. I believe it will help make a better system!
-
7. Re: BC.Next Caching With Content Holders and Includes
Hi Lynda,
For this release, the new caching features works with static content from templates and pages. Content from modules and content holders it not supported for now, but we are looking for methods to enable that as well.
Cristinel
-
8. Re: BC.Next Caching With Content Holders and Includes
Appreciate that will be more involved Cristinel, Thanks for the update.
When you say static content that covers templates, pages, blog etc.
-
9. Re: BC.Next Caching With Content Holders and Includes
Hi Liam,
Static content covers images, styles and scripts from pages and templates. Blogs are not supported at this point. We'll follow-up on that as we will be adding a method to cache some content from modules as well. But for now, pages and templates represent a huge chuck of the BC content and we wanted to start with that first.
Cristinel
-
10. Re: BC.Next Caching With Content Holders and Includes
Hi Lynda,
Indeed they don't and it's not a bug, as we only mark the static assets that can be found directly in the template and page and not the ones that get included through content holders, liquid includes or modules.
Cristinel
-