I tested this on a 7/18/2017 version of master, and I'm seeing something odd.
It looks like the block in header.tt2 gets called multiple times, and it doesn't handle that well.
# Browser cache-busting key
145 # Fall back to the eg_cache_hash (set by autogen) so that we don't have to
146 # add conditionals into the rest of the templates
147 IF ctx.cache_key;
148 ctx.cache_key = "?v=" _ ctx.cache_key;
149 ELSE;
150 ctx.cache_key = "?" _ ctx.eg_cache_hash;
151 END;
I'm seeing that catch busted files in the beginning of the document show
expert_row_close_btn.png?a16b97
and then further down they change to a different pattern.
eg_tiny_logo.png?v=?v=?a16b97
Which looks to me like it would be caused by multiple calls of the mentioned block of template code. I don't think it causes anything to not work, but it might cause some unnecessary requests.
Maybe the code should also check to see if the ctx.cache_key == "?" _ ctx.eg_cache_hash before changing it?
I tested this on a 7/18/2017 version of master, and I'm seeing something odd.
It looks like the block in header.tt2 gets called multiple times, and it doesn't handle that well.
# Browser cache-busting key
145 # Fall back to the eg_cache_hash (set by autogen) so that we don't have to
146 # add conditionals into the rest of the templates
147 IF ctx.cache_key;
148 ctx.cache_key = "?v=" _ ctx.cache_key;
149 ELSE;
150 ctx.cache_key = "?" _ ctx.eg_cache_hash;
151 END;
I'm seeing that catch busted files in the beginning of the document show row_close_ btn.png? a16b97
expert_
and then further down they change to a different pattern. logo.png? v=?v=?a16b97
eg_tiny_
Which looks to me like it would be caused by multiple calls of the mentioned block of template code. I don't think it causes anything to not work, but it might cause some unnecessary requests.
Maybe the code should also check to see if the ctx.cache_key == "?" _ ctx.eg_cache_hash before changing it?
Josh