Recommend this pageIf this page was useful to you, please recommend it to fellow websurfers:
You may rate this script by simply clicking on the appropriate star (5 stars is the best rating).
Mahara is officially supported on the following operating systems:
Mahara is not officially supported, but known to work or mostly work, on the following operating systems:
Currently, we’re not certain of the status of Mahara on other operating systems (Solaris springs to mind). If you know more, feel free to add them to the above list!
Mahara is officially supported on the following web servers:
Mahara is not officially supported, but known to work or mostly work, on the following web servers:
Mahara is officially supported on the following database servers:
Mahara’s database must be in UTF8 encoding. In MySQL, you can use any UTF8 collation you like - generally, you’ll pick the one that suits your locale.
If you are using MySQL 5.1.5 or older, you need to add the SUPER privilege to Mahara’s database user in order to enable the Elasticsearch search plugin. (IF you will not be using Elasticsearch, you don’t need this.)
Mahara is not supported or known to work on any other database server.
PHP version 5.3.6 or later is required. In addition, you’ll need the following extensions:
You should make sure that magic_quotes_gpc is off, and that register_globals is off. Mahara will work around these settings if they’re on, but it’s better if you turn them off.
What makes Mahara different from other ePortfolio systems is that you control which items and what information (artefacts) within your portfolio other users see.
In order to facilitate this access control, all artefacts you wish to show to other users need to be bundled up and placed onto a page.
You can have as many pages as you like, each with a different collection of artefacts, and intended purpose and audience. Your audience, or the people you wish to give access to your page, can be added as individuals or as a member of a group or community.
ePortfolio owners create pages using a 4-step process, and page have the following features:
Within Mahara you can share details through a variety of optional profile information fields including:
Mahara includes a file repository which allows you to:
A comprehensive blogging tool is provided in Mahara, where blogs and blog postings are considered artefacts and may be added to a page.
The blogging tool allows you to:
Mahara includes a résumé builder which allows you to create digital CVs by entering information into a variety of optional fields including:
Administrators are able to customise Mahara via a number of configuration settings which include:
In addition, with the Modular plugin structure of Mahara, artefact and block types may be configured, disabled or enabled, according to the organisation’s requirements.
Mahara provides a single-sign on capability that allows users, at the option of the administrator, to be automatically logged in to both their Mahara and Moodle accounts by providing a username and password at only one of these sites.
The user can sign on at Mahara, and click on a link to her Moodle account, or sign on at Moodle, and click on a link to her Mahara account.
The single-sign-on feature runs over an encrypted transport, and the user’s passwords do not have to be shared between sites.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.
Mahara has been designed as a web application with a plug-in architecture. This means it is possible to scale the application up by separating hardware for search, database, file storage and web servers.
It is also possible to replicate each of these operational components to further scale the system upwards. In addition Mahara is designed to:
This hosting setup has proven scalability for similar systems like Moodle.
This label indicates that I could install the script without major problems and I could run the script without the need for major modifications to the original code (except for the usual configuration, of course). The label does, on the other hand, not indicate that scripts without this label would not work properly. The missing of the „tested & working“-label just indicates that I did not yet test these scripts.
This label indicates that the owner of this website uses this script / application for his own projects with success and satisfaction. This does, however, not indicate that these projects could not have been realized using other scripts / applications as well or that other scripts would not fit the demands of other projects as well or even better.