Many CalZope? / CPSSharedCalendar templates make links to CSS / js files dependending on the location of the viewed event / day / week ...
This makes it impossible for the client to cache these resources correctly and multiply the average number of simultaneous requests by 5 to 10 wich impact the overall performance of the application a lot.
The solution is to make them point to ${base_url}++resource++resourcename where
base_url is something like context/portal_url or better request/cpsskins_base_url on CPS.
At least the following templates are affected:
action_needed_events.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
attended_events.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
attendees.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
calendar.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
day.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
event.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
meetinghelper.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
month.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
organized_events.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
week.pt: tal:content="string:@import url(${context/absolute_url}/++resource++calendar.css);"
