I discovered that while caching of the js code is enabled, any pages that have a url longer than a primary 'folder' (e.g. site.com/customer/contact, site.com/node/435) does not work. Only single folders work (e.g. site.com/home). I'm not quite sure how to explain that properly, so I hope those examples work.

Looking at the HTML returned when caching is enabled, it appears that instead of linking to the cached js file in the correct location, it simply removes the last bit of the current URL and appends the js url to the end, resulting in a URL with the first part of the current URL still there.

CommentFileSizeAuthor
#1 252745.patch764 bytestomdeb

Comments

tomdeb’s picture

Assigned: Unassigned » tomdeb
Status: Active » Needs review
StatusFileSize
new764 bytes

Could you try the attached patch and let me know if it fixes the problem ?

chadcrew’s picture

I noticed this problem also. Your patch seems to have solved the problem for me. Thanks,
Chad

tomdeb’s picture

Status: Needs review » Fixed

fixed and released in 6.x-1.1 and 5.x-1.1

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.