William, I thought about your simple response and liked it. It made me think about how what is shown for the specific version in the Moodle download area is abbreviated (see below). This made me wonder if it would make sense that the download area should someday, in the future, show this Server|Enviroment list in addition to the abbreviated list. Yes, in the Moodle docs, these items in the complete list are covered, but I wonder if it would help to reproduce them in the download's description, such as:
Or maybe a link saying "See the documentation for full installation requirements."
Yes, as an example, the "intl" extension seems to be lacking, and (for me) difficult to install in some AMP packages. It is "required" and if not installed, the current Moodle installation fails. So this seems to be just as important as having php7.0 or the right version of MySQL.
I seem to recall that there was a way to get to this Server|Environmet check without having to go through the Moodle installation. Sure, one can run the info.php command, but it doesn't provide the nice summary that Server|Environment provides. Maybe someone will remember.
You are definitely right about that- if any extension is *REQUIRED*, particularly ones that are being added to that required list, they should be spelled out more obviously. I know these are mentioned in the documentation, but still easy to gloss over. In addition to required php versions, a required extension list would be helpful since these are critical to installing new instances, or updating older versions. Some greater weighting or preference to this information might go a long way for some. It wouldn't take much more effort than presenting it as:
| Moodle 3.5.2+ MOODLE_35_STABLE Built Weekly 11 hours 49 mins ago | This package is built every week with new fixes produced by our stable development process. It contains a number of fixes made since the 3.5.2 release and is usually a better choice for production than the actual 3.5.2 package below.
|
I still need your help, Howard.
Okay, AMP stands for Apache, MySQL, and PHP. Or said a little more generically: a server, a database, and a language.
In the Moodle download description, the "database" seems to be very precisely defined, and it is very visible. Yes, as we know, there are some other database requirements, such as barracuda and collation. Yet these added requirements are not mentioned.
In the Moodle download description, the "language" is defined. PHP7.0, for example. Yes, maybe somewhat consistent to the "database", it doesn't mention the required php extensions, and some of the required php settings (such as memory_limit).
In the Moodle download description, the "server" isn't defined. We know that it could be Apache, or nginx, or some other server like Microsoft. Nor are server requirements defined on this download description.
So, maybe the way the current download description is worded is really the best that we can do. Maybe it is best to refer people to the Moodle installation documentation. However, if this is the case, I wonder if it would be helpful to provide a hyperlinked "See installation documentation" statement somewhere. I support a perspective to inform the user of these installation requirements, yet keep things as clean as possible.
Okay, now I see... the word "Requires" is a hyperlink, that does take one to more details. Somehow, this has never been obvious to me. It takes me to "Moodle 3.5 release notes" and from there I can probe the more detailed requirements. And I do see a note that "intl" is required. The only thing that seems to be missing are the additional required php extensions.
All of this makes me wonder if there is some opportunity for some improvement?
I completely agree that the link to the release notes should be much clearer. I'll put in a ticket.
I also agree that the release notes should probably be a bit more comprehensive regarding requirements. As that is part of the Wiki I shall undertake to research this and get it done.
I am guilty of saying quite frequently, "make sure you read the release notes" but thinking about it vital information is probably spread amongst those notes, the installation pages and the upgrade pages.
I'd be very interested in Helen and Mary's thoughts.
As promised, MDLSITE-5540
Your MDL already has one vote.
I feel guilty too because I know that the docs are a wiki, but I haven't devoted time to making improvements.
It does seem to me that we get a fair share of "installation" questions, and problems because the person has missed something. Improvements to the installation documentation can help all.
@all ...
what is it 'they' say ... tell 'em, tell 'em what you told 'em, tell 'em again!' Info or links to info found in multiple places.
1. in the notifications screen a link to check environment atop of the versions available. I do this now on sites and have to putz with Language files to get that link.
2. environment check requires clicking a link to update component. How about if it were a task and done automatically? Yes, I know one could create a task ... but am talking no addon ... but core.
3. in the listing of the environment ... link to check on a row goes to where? Me thinks there is enough room on every row to put a link to where ever - release notes? Could the link be determined by the drop down pick list setting?
2 cents.
'spirit of sharing', Ken