Proposals/Upgrader: Difference between revisions
From Mahara Wiki
< Proposals
m (Anitsirk moved page Roadmap/Archive/Installer//Upgrader to Roadmap/Z Archive/Installer//Upgrader: So it's not listed first in a subpage listing) |
m (Anitsirk moved page Developer Area/Specifications in Development/Upgrader to Proposals/Upgrader: Shorter navigation, not always technical) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<div style=" | <div style="border:2px solid #ba9c53; text-align:left; padding:10px; border-radius:5px"> | ||
<i class="fa fa-arrow-circle-o-right fa-lg"></i> '''Please see https://blueprints.launchpad.net/mahara for proposed features and those that are being worked on.''' | |||
</div> | </div> | ||
A few ideas for ways we could improve this process: | A few ideas for ways we could improve this process: | ||
Latest revision as of 17:43, 11 July 2020
Please see https://blueprints.launchpad.net/mahara for proposed features and those that are being worked on.
A few ideas for ways we could improve this process:
- Get rid of the LOG_ENVIRON errors, especially the one for not being installed. It would be much nicer to present a friendly screen informing the user about creating the config.php file - and even better if we could create a form that would help them generate one. This screen could present friendly notices about things like magic_quotes_gpc, other hints to make Mahara work better, and links to documentation or even videos that explain the installation process.
- The import/export work proved we could make loading bars that worked without javascript, it would be nice if we could change the installer and upgrader to use those. The current method of listing each plugin has gotten very long...
- Error reporting: currently you are only notified that a query failed, not why it failed, which is important information. It would be good to show all relevant information about the failure, as well as instructions on how to report the problem.
- Once the site has been installed, log the user in straight away so they can set their password and e-mail.
- Once everything has been set up, maybe we want to dump them at the admin panel with instructions of what to do now?