well with debug = on. In fact the change password screen didn't play at all.
Made a few small changes to fix notices and now everything works OK.
Added a missing language string.
*****************
This problem may very well exist in MOODLE_14_STABLE too! Unfortunately I
don't have access to a 1.4 checkout right now, so it will have to wait.
*****************
for user field locking and forcing of password changing
- Locked user fields always apply (for any authentication method).
Currently these can only be defined in the LDAP auth screen
but later these can be brought out as part of the generic
interface for defining user fields and their behaviour.
- Fields are now locked using Javascript and will work for any
user fields that exist (list is not hard coded anymore).
- Admins can always edit locked fields.
- Admins can always force a password change. The checkbox reflects
the current status of this, and the admin can UNSET the checkbox
if they want. It is no longer necessary for the admin to change
the old password for this to take effect, either.
These patches are maintained in an publicly accessible Arch repository, see: http://lists.eduforge.org/cgi-bin/archzoom.cgi/arch-eduforge@catalyst.net.nz--2004-MIRROR/moodle--eduforge--1.3.3
Index of arch patches in this commit:
arch-eduforge@catalyst.net.nz--2004/moodle--eduforge--1.3.3--patch-66
2004-09-16 00:03:41 GMT
Penny Leach <penny@catalyst.net.nz>
changes to upload class to be silent if we want it to be, integration with editing user profile and group profile (which meant changes in lib/gdlib.php as well as course/group-edit and group.php and user/edit.html and edit.php
Full logs:
Revision: moodle--eduforge--1.3.3--patch-66
Archive: arch-eduforge@catalyst.net.nz--2004
Creator: Penny Leach <penny@catalyst.net.nz>
Date: Thu Sep 16 12:03:41 NZST 2004
Standard-date: 2004-09-16 00:03:41 GMT
Modified-files: course/group-edit.html course/group.php
lib/gdlib.php lib/uploadlib.php user/edit.html
user/edit.php
New-patches: arch-eduforge@catalyst.net.nz--2004/moodle--eduforge--1.3.3--patch-66
Summary: changes to upload class to be silent if we want it to be, integration with editing user profile and group profile (which meant changes in lib/gdlib.php as well as course/group-edit and group.php and user/edit.html and edit.php
Keywords:
1) There is a new site-wide configuration variable called maxbytes,
which provides an upper filesize limit for all (student) uploads.
2) There is a new course-level variable called maxbytes, which further
limits uploads within a course.
3) There is a new maxbytes field for forums, which further restricts
the size allowed in a particular forum. There is also a new config
variable in the module configuration to specify a default size
to use when defining a new forum.
4) Assignments already had a limit, but this is now aware of the other
limits, and like forums there is now a settable default value.
5) Finally, the sizes of files (Gb, Mb, Kb, bytes) is now translatable
in the language packs.
so it can be translated.
There is now a new function get_list_of_countries() which will return a
sorted array of countries in the best current language.
get_string("AU", "countries") will also work if needed
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!)
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
Uploaded images are now saved even if the rest of the form
has errors.
If errors are found in the form then a message is printed up
the top to make it clearer that they need to fix something.
confirmation on deletions, removing deleted user from all student lists,
teacher lists and subscription lists and freeing up their username and
email to be used again.
