Reviewed:  https://reviews.mahara.org/11029
Committed: 
https://git.mahara.org/mahara/mahara/commit/d49359dbd3cb4b74e4259f717f011828eb3f0641
Submitter: Robert Lyon ([email protected])
Branch:    master

commit d49359dbd3cb4b74e4259f717f011828eb3f0641
Author: Cecilia Vela Gurovic <[email protected]>
Date:   Sat Jun 20 19:24:11 2020 +1200

Bug 1884346: adding mahara.org version to SESSION var

behatnotneeded

Change-Id: I05f8b7892d88507e8de74057a4c534c321330d37

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask 
on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1884346

Title:
  function cron_check_for_updates takes too long to run

Status in Mahara:
  New

Bug description:
  It's unlikely that the mahara.org mahara version will change very
  often, and we are calling the function cron_check_for_updates
  constantly (everytime we load a page, when loading a modal, etc) to
  see if the mahara version has change.

  Everytime this function is called when using the site (not by cron
  job), it executes a mahara_http_request that will take a bit more than
  2 seconds, making the mahara instance work slower than it should.

  If this data doesn't change that often we can save this value in the
  $SESSION variable so the mahara_http_request is not being called all
  the time.

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

_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~mahara-contributors
More help   : https://help.launchpad.net/ListHelp

Reply via email to