Mahara Community


Forum Topics Subscribe Edit


Official news and events for Mahara


Need help using or installing Mahara? Ask your questions here.

If you're customising Mahara, please ask your questions in the Developers Forum , the Themes Group or the Translations Forum as appropriate.

Please read the README thread first, it has answers to some common questions!


If you have found a bug in Mahara, please file a bug report on the Mahara bug tracker at

Report a bug


A non-techie () place to discuss eportfolio use for teaching and learning.


Anything about Mahara software development, or developing for Mahara:Core developmentDatabasesUsabilityTestingDeveloping new plugins

Note that the Mahara core developers tend to discuss things in #mahara-dev on freenode. You're welcome to lurk there, and listen in on conversations, but it's only for discussions about Mahara's development itself - you can use #mahara for those questions.

Also, check out the developer area of the wiki - it has information about Mahara's internals and on how to write plugins.

Open Discussion

Discuss anything about Mahara - as long as it doesn't fit in another forum!

Mahara/Moodle integration

Using Mahara with Moodle - everything from set up problems to usage case studies. Also check out the Moodle Mahara Integration Group.

Mobile Mahara

Discussions around mobile apps for Mahara.

Security Announcements

Subscribe to this forum to be notified about security fixes.

Comments on feature proposals

Discussion of new features for core Mahara that a developer (team) is getting started on and invites comments.

This forum is not for making feature requests - we have a bug tracker for this. However, if you want a feature to be implemented, and have funding (part or full) for it, you can post about it in here. Please read the forum instructions before posting.

Heads up: shuts down weak TLS ciphers on 15 February 2016

Hello Mahara community,

To continue to provide a secure environment for the community discussions forums, we are going to strengthen our security on the server infrastructure by disallowing weak TLS ciphers. We will make that change on 15 February 2016 to allow any users who still use old browsers to find an alternative.

What does that mean for me?

The majority of you will not have to worry about this change. Only users with old browsers that still support these weak ciphers should upgrade their browser. Recommended alternative browsers to any built-in ones that will not be supported anymore are Mozilla Firefox and Google Chrome.

After we disable the weak ciphers on 15 February 2016 and you are still running an old browser that allows them, you will not be able to connect to anymore and will need to install a newer / recommended browser.

Am I affected by this change?

As per the SSL Labs report (as at 18 January 2016), the following browsers are affected....