mahara-contributors team mailing list archive

[Aaron Wells <1214124@xxxxxxxxxxxxxxxxxx>]

Seems like a decent approach. The get_config('release') value goes up
with each minor release, which is the most likely time that people will
deploy new versions of Mahara. And in between minor releases, the
version number gets changed to e.g. 1.7.3testing, which again is
different, so if admins deploy a minor release and then update to HEAD
before the next minor release, they'll get another version number.

I suppose if we want to be really complete on this, we should adopt a
policy that if you push a commit that changes static assets, you should
increment the release number e.g. 1.7.3testing1 1.7.3testing2, etc.

-- 
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