This includes some significant cleanups to the new course categories
system. The basic idea is that the categories/course browser is now
unified under one system, and admin features related to that have
all been moved into the browser (as little icons).
I'm much happier with this as a foundation that can scale and be
built upon.
Still to go:
- searching
- paging
- polishing
Also in here are a lot of little cleanups around the place, such as
the initial setup process.
- moved user images to /pix/u folder, and changed format to .png to allow
transparent images etc. These can now be customised in themes.
- removed legacy madewithmoodle logos
changing passwords, and enabled the internal "change password" button
just like "email" and "none".
Thanks to Danilo Massa for pointing out the inconsistency.
This sets the default value for on-the-fly forum subscription.
Defaults to on = subscribe.
(Also fixed a bug in postgres7.sql - a missing field for htmleditor!)
Hopefully this is also the end of the occasional errors we keep
hearing about to do with never getting to setup the admin user.
(I think admin/site.php had a redirect that didn't always work).
The setup process is now much better at "trapping" you until it's all done.
- they could break accounts in existing installations
- strtolower can corrupt strings in multibyte languages
Is it really a problem that usernames are case sensitive on PostgreSQL?
When using authentication module (ldap, smb, pop etc...) and postgres-database multiple moodle
users were created for usernames like 'Username' 'username' 'userName'
Firstly, I'm replacing all use of old-style global variables like
$HTTY_REFERER with their new-style equivalent $_SERVER["HTTP_REFERER"]
Also using $_POST instead $HTTP_POST_VARS etc
Secondly, if gdversion == 0 (ie GD is not installed) then:
- users are not even allowed to upload new images
- graphs now just print a message instead of failing.
this allows Moodle to still be used even if GD is not present
Should be fixed now. As a bonus, I've removed all the uses of
HTTP_POST_VARS from all scripts.
All forms should use the new data_submitted() function to collect
form data (it does the match_referer thing internally now).
Much nicer.
Moodle tables.
ie user -> userid in many tables, plus in user_students
start -> starttime and end -> endtime
I've just done all this as carefully as I could ... I don't think
I missed anything but it's pretty intensive work and I'd be fooling myself
if I didn't think I'd missed a couple.
Note that this version should pretty much be able to bootstrap itself
using PostgreSQL now ... but this is untested