11.2. Admin home¶
Administration menu → Admin home
Admin home is only accessible by site administrators.
You see all administrative items on the main page of the Administration on Admin home.
If a core Mahara plugin requires an upgrade, you will see a notice about it and only need to click the button Run upgrade.
If a plugin needs to be installed, click the Install via extensions page button to be taken to the Plugin administration for the installation.
After you have installed Mahara, you may see a number of warnings when you go to the Administration as site administrator. They should all be resolved to ensure that your site is secure and has all the necessary settings.
Session entropy length: Your PHP session.entropy_length setting is too small. Set it to at least 16 in your php.ini to ensure that generated session IDs are random and unpredictable enough. You can learn more about this advisory on the OWASP session management cheatsheet.
Noreply email address: If the system email address is empty or a malformed email address, you are asked to check and correct it in the system mail address setting.
Site-wide password salt: If you do not have one set, please edit your config.php file and set it to a reasonable length.
SAML setup: If you do not have SAML authentication set up properly and do not have SAML activated, you do not see any warning messages as they would only go away if you activate the plugin and install all the required dependencies.
Administration menu → Admin home → Register
As of October 2022, all Mahara sites are automatically registered with the Mahara project when they are updated to the latest minor point release or upgraded to Mahara 22.10 though you can opt out of the data collection.
If you have set the config.php variable
$cfg->productionmode to ‘false’, no data will be sent to the Mahara project as it is assumed that the site is a non-production site.
The registration data helps the project get more insight into how Mahara is used. The project does not collect person-identifiable data, but only anonymised and aggregated information.
When you are on the administration overview page, you will see a link directly to the registration page.
When you upgrade your site to a version of Mahara that changes the registration from opt-in to opt-out, site administrators are taken directly to the registration screen to review the data that is being sent.
You can preview the data that is sent on a weekly basis. All information is sent anonymously. We will only know, for example, which version of Mahara you are running, how many times blocks or artefacts have been used, how many account holders you have etc.
The date since the site was registered is displayed.
If you opted out from the data collection, this will be stated here.
Click the individual sections to see what data is sent.
Opt out from the data collection: Set this switch to ‘Yes’ if you do not wish to send weekly updates to the Mahara project of the data seen on this page.
Click the Save button to finish making changes or click Cancel to abort.
11.2.4. Site information¶
The Site information gives you as site administrator a quick overview of:
How your site is used.
When your site was installed.
How big the database is.
How much site data has been accumulated.
Which version of Mahara you are running.
Whether your cron is running or not.
If you have problems with your Mahara instance and you request information from the community in the forums, this information, esp. about your version and the cron, are useful to have. Furthermore, the version number allows you to check that you have the latest security release of your Mahara version installed.
When you ask for help in the forums, it is recommended that you do not post the minor point version for security reasons. That means, only give the major version number, i.e. 20.04, 20.10 etc. but not 20.04.1 so that it is harder for a malicious actor to know which specific security issue they could exploit.
We also recommend that you update to the latest minor point version of the releae you are using before requesting assistance as we may have already fixed the problem you are reporting in a subsequent minor point release.
In addition to seeing what version of Mahara you have installed and what the latest major version is, you now also see whether your version of Mahara is out of support. If you are still on a supported version but not on the latest minor point release, that information will be displayed. This gives you easier certainty about how up-to-date your Mahara site is.
You must run the cron regularly to keep that information current.
The cron job is very important in Mahara as a number of vital tasks are only performed when it is running. You can find more information of how to set it up on the wiki. If the cron is not running or only partially running, that information is displayed in red.
11.2.5. Clear caches¶
Administration menu → Admin home → Overview
A number of elements are cached in Mahara on the system level to speed up the site. In some cases, you may wish to force a new version though if the browser doesn’t recognize it on its own.
Click the Clear caches button to clear all caches.
The caches can also be cleared via a commandline script, which system administrators can find in
11.2.6. Close site¶
Administration menu → Admin home → Overview
You may close the site to everyone except administrators. This is useful when you prepare for and complete a database upgrade. Only administrators will be able to log in during maintenance mode until you either reopen the site or an upgrade is successfully completed.
Since the site is not accessible to anyone unless they are logged into the site as site administrator, certain processes would also fail, e.g. accessing the SAML metadata that is monitored by IdPs. It is possible to add a flag to a php file to ignore maintenance mode.
Administration menu → Admin home → Monitor
While the monitor plugin is mainly to alert you about cron job failures outside of Mahara, e.g. if you have a dashboard, you can see some information directly in Mahara in the site administration area, depending on your site configuration:
Cron processes: Long running processes
LDAP lookup: LDAP status of availability
LDAP suspended accounts: Percentage of LDAP accounts suspended by the LDAP account sync since midnight
Elasticsearch: Queue status
The item that is being monitored.
What is being monitored.
Results of the monitoring.
Export the results as CSV file.