Posts Tagged ‘Tracker’

Searching the Moodle tracker

These days I spend a fair bit of time searching the Moodle tracker to check whether problems with Moodle i.e. ‘bugs’ have been reported previously. I’ve discovered it’s not difficult to end up with thousands of search results! Thus, over time I’ve refined my search techniques. Here is how I usually manage to find what I am looking for:

  1. Follow the Find issues link.
  2. Select Moodle as the project and if necessary click where indicated to refresh the search menu.
  3. If the problem has a very obvious component e.g. Quiz then select it.
  4. For 2.0 bugs, select 2.0 as affected version.
  5. Think of a word or phrase which is specific to the bug, such as an error message, and enter it in the text search box.
  6. Scroll to the bottom of the page and click View.
  7. Click the Updated column header to sort the search results so that the most recently updated issues are listed first. Generally any search results which don’t appear on the first page are pretty old and so far less relevant.

I usually find what I’m looking for by browsing the summaries on the first page of the search results. If not, then I conclude that the bug has not been reported.

Perhaps you also search the tracker in this way? Or maybe you can suggest further tips for improving search results? If so, please add a comment below.

If you come across a bug in Moodle but don’t have much time to search for it in the tracker, please just create a new issue for it. Don’t be afraid of creating a duplicate issue, as it’s better that bugs are reported twice than not at all!

Finally, many thanks to everyone who reports and comments on tracker issues. Your help is much appreciated!


Read Full Post »

Today is the last day of MOODLE_17_STABLE in the Moodle Tracker. As Martin mentioned in the moodle.org news back in February, New releases: Moodle 1.9.4, 1.8.8, 1.7.7 and 1.6.9,

Moodle 1.6.9 and Moodle 1.7.7 mark the last builds that the core team plan to release from those branches… please upgrade to later versions!

For anyone interested, our process of dropping support for older stable branches is detailed in Development:Stable branch support.

Keeping your site up-to-date is highly recommended in order to keep your site secure. Also recommended is to regularly run the Security overview report in Site Administration > Reports > Security overview (source: Hacked site recovery).

Read Full Post »

Issue security levels

Did you know that the security level setting of an issue in the Moodle Tracker determines how many people can view it?

I knew that serious security issues could only be viewed by members of the security team (led by Petr Škoda) but I only discovered recently that the other security levels also restrict access.

The different security levels provide access as follows:

  • None – Viewable by everyone, including non-logged-in users
  • Could be a security issue – Viewable by all logged-in users
  • Minor security issue – Viewable by developers and testers only
  • Serious security issue – Viewable by members of the security team only

If you’re not sure whether your issue is security-related or not, please report it in the tracker anyway. If you’re not sure which security level to choose, select a higher level. The issue can then be reviewed by a member of the security team and if necessary the level changed (as happened for MDL-18996).

The reason for restricting access to security issues, is that Moodle practises responsible disclosure. This means we have a policy of disclosing all security issues that come to our attention, but only after we have solved the issue and given registered Moodle sites time to upgrade or patch their installations. (Source: Moodle security procedures)

If you have a non-security-related issue, then the more people who can view it the better.

“Given enough eyeballs, all bugs are shallow” (Linus’s law).

Read Full Post »

Last Friday, 31st July, was System Administrator Appreciation Day. A belated big thank you to our moodle.org system administrator Jordan Tomkinson for looking after all our servers so well.

Moodle server availability info can be found on http://moodle.org/stats/network.php together with info on the availability of CVS mirror servers.

Last Friday was also the last day of Moodle 1.6.x in the Moodle Tracker (MDLSITE-737). As Martin D mentioned in the moodle.org news six months ago, New releases: Moodle 1.9.4, 1.8.8, 1.7.7 and 1.6.9, “Moodle 1.6.9 and Moodle 1.7.7 mark the last builds that the core team plan to release from those branches… please upgrade to later versions!

Read Full Post »

Eloy reminded me the other day of the importance of linking between Moodle Tracker issues and forum discussions to ensure that developers and testers have the full picture.

It’s easy to add a tracker issue link to a forum post – simply type the issue number and the tracker issue auto-linking filter will do the rest. Adding a tracker issue link to a forum post encourages others to watch, vote for and/or comment on the issue.

If you’re looking for a challenge, you may like to check out a particularly difficult issue which Eloy reported a while ago – MDL-15169.

Read Full Post »