These are chat archives for jescalan/roots

8th
Aug 2015
Mark
@markphillips100
Aug 08 2015 06:44
I'm trying to use the roots-contentful extension which functionally works okay when obtaining a list of entries and rendering a single page from a template jade file. However, when I have hash:true on both js_pipeline and css_pipeline to generate cache-busting urls for production the urls generated in the dynamic single pages does not contain the hash number. The hashed file versions exist on disk so the pipeline extensions are generating them. It seems roots-contentful is generating single pages before the pipeline extensions have done their work. Is it possible to synchronize the order of these plugins?
Mark
@markphillips100
Aug 08 2015 08:35
I've replicated the same issue using roots-records extension instead as the dynamic content generator against "api.bycarrot.com/staff";. Again, none of the dynamically generated files that are using the same layout and therefore the same "!= css()" and "!= js()" include the correct hashed filepaths. Also noticed the inclusion of either of these two extensions affects the hashed filenames generated for the css and js combined files. A regular jade file using the layout showed the following: <script src='/js/build.d41d8cd98f00b204e9800998ecf8427e.d41d8cd98f00b204e9800998ecf8427e.d6b53b53596e26481b4927c51b826a44.js'>. This file exists on disk so it looks like it passed through the hash function of js_pipeline several times, but only when either roots-contentful or roots-records it used.