In moodle.php is a whole lot of help strings that are only shown to admins, ie all the ones starting with "config". In fact this text takes up nearly 20% of moodle.php!!
This file is loaded on every Moodle page, so this extra text is a bit of a waste of memory and time.
Since we were just tidying up the configuration page, I am considering moving these strings to admin.php where they belong. I would do this for every language pack at once, and update the code for 1.4.4 and 1.5 to support it there.
The problem is that people using older versions who download new versions of their own language pack will find that variables page is all in English. If they also update their English language pack then will find that page will have no help on it at all.
Is this worth the problems? Should I leave some stub strings in moodle.php to advise people to upgrade their Moodle to 1.4.4 or 1.5?
Martin Dougiamas
Posts made by Martin Dougiamas
If you find a programmer they might be able to write a filter to do this using a free web service, but it wouldn't read very nice (and it would be slow).
If you are prepared to hand-translate then you can turn on the multilang filter in Admin >> Config >> Filters and put text with this format in every place you want to:
<lang lang="en"> Some english text here</lang>
<lang lang="it"> Some Italian text here </lang>
If you are prepared to hand-translate then you can turn on the multilang filter in Admin >> Config >> Filters and put text with this format in every place you want to:
<lang lang="en"> Some english text here</lang>
<lang lang="it"> Some Italian text here </lang>
The default default is that way on purpose - I could talk a lot about it but basically email encourages interaction.
There's no need to show this error to students using the STABLE branch, Jon, it's more of a developer notice. 
I've changed the function to only print the notify when debugging mode is on.
I've changed the function to only print the notify when debugging mode is on.
Not at all, Joyce - thanks for the report! I wasn't seeing it.
The bugs were fixed today. bug 2513 and this discussion
The bugs were fixed today. bug 2513 and this discussion