mahara-contributors team mailing list archive

[Aaron Wells <1214124@xxxxxxxxxxxxxxxxxx>]

Actually on further reflection, I think maybe we should mimic the Moodle
approach. What they do is store a separate arbitrary "themeversion"
number. It gets incremented each time you upgrade, or if you push the
"Purge cache" button on a special admin page. This allows the cache to
be purged manually at any time, for instance if you deploy a change to
one of your plugins.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1214124

Title:
  Improve stylesheet cacheing

Status in Mahara ePortfolio:
  In Progress

Bug description:
  There is no "purge the stylesheet cache" functionality in Mahara. This
  lack of functionality prevents stylesheet changes to be seen directly
  and generally, users will need to clear their browser cache.

  Suggestion from Pace University:

  Add a URL parameter for the version of Mahara in which the stylesheet
  changes.

  So for example, instead of calling

       <link rel="stylesheet" type="text/css"
  href="/theme/raw/static/style/style.css">

  consider calling the 1.7.1 stylesheet:

       <link rel="stylesheet" type="text/css"
  href="/theme/raw/static/style/style.css?v=1_7_1">

  and in version 1.8.1 call:

       <link rel="stylesheet" type="text/css"
  href="/theme/raw/static/style/style.css?v=1_8_1">

  So the stylesheet would be still be named style.css, but the URL
  parameter will prevent the browser from using a locally cached
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1214124/+subscriptions