Simon Coggins

Yes, they both switched to using totaralms.com emails when they joined us so it only counts their work for Totara against the totaralms.com domain.

I would like to offer a counterpoint to that because I don’t think it’s fair on the hard work our developers have put in to upstreaming and contributing changes over the last 5 years.

Here is a list of the top 20 contributor’s domains, calculated from the number of lines of code in current moodle/master using the email domain of the author, over the last 5 years [1]:

1. moodle.com    529125
   
2. skodak.org    335213
3. open.ac.uk    97749
4. nicols.co.uk    59915
5. moodle.org    39338
6. gmail.com    28804
7. netspot.com.au    17577
8. totaralms.com    17420
9. moodlerooms.com    13471
10. vedrine.org    10903
11. mondragon.edu    10790
12. jamiep.org    8648
13. danmarsden.com    8341
14. grabs-edv.de    6284
15. spvickers.freeserve.co.uk    4774
16. massey.ac.nz    3707
17. luns.net.uk    3622
18. oakland.edu    3422
19. goffstown.k12.nh.us    3399
20. mouneyrac.com    3212

Totara’s contributions to Moodle have been on par or greater than any Moodle partner. If Learning Plans, Competencies and Report Builder all get integrated into Moodle you can increase that figure by another 100,000 lines.

I don’t think it’s fair to call that work "minimal”.

Simon

[1] While not a perfect metric I would argue it is reasonably representative (enough to make the point valid). Code used to calculate the numbers above is attached.

Hi Adin,

I think your suspicions about it being an issue with the loading of external resources are likely to be right. There are a number of possible causes including a misconfigured webroot, SSL issues or possibly the proxy.

The first thing I would do would be to view the source of your homepage and check the path of resources like stylesheets or javascript are what you expect. If the path is correct I'd try manually loading one of those resources via a browser and seeing if you get any errors.

By the way, in this case I think your problem is unlikely to be Totara specific, but if you do want to ask any Totara specific questions you are welcome to self-register on our community site and post there.

Best of luck,

Simon

Hi John,

I'm afraid it was the wikipedia article that was a bit dated (I've updated it now), Totara's based on 2.7 currently.

Simon

Hi,

It's not fixed quite yet, Yuliya created a patch today and it is currently working through Moodle's review and testing process. Hopefully the fix will be included in the next Moodle point release.

As for your next steps the best thing would be to wait until the next point release (due around Mid-march I think) and then upgrade your site.

Alternatively if you can't wait or are running an unsupported version you could ask your system administrator to apply the patch for this specific issue from the bug. If you are going to do that I'd probably wait until the review and testing process has finished in case any changes are needed.

Simon