Closed (fixed)
Project:
Woopra
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
29 Apr 2008 at 16:44 UTC
Updated:
2 Jul 2008 at 11:02 UTC
Jump to comment: Most recent file
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.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 252745.patch | 764 bytes | tomdeb |
Comments
Comment #1
tomdeb commentedCould you try the attached patch and let me know if it fixes the problem ?
Comment #2
chadcrew commentedI noticed this problem also. Your patch seems to have solved the problem for me. Thanks,
Chad
Comment #3
tomdeb commentedfixed and released in 6.x-1.1 and 5.x-1.1
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.