This can be userd to store "global unique identifier" from external databases
like Windows SID or eDirectorys guid . This will keep upcoming user syncronization
feature reliable in case of renamed users.
Mysql files are untested.
php -l mysql.php does not show any syntax errors, so files
should work.
authentication mechanism used to create that user record.
Also added code to upgrade existing systems to have entries in that
field, and for new users to also have that field defined.
This will allow us to later improve the login procedure to be able to
handle various types of authentication.
Integrated with Moodle:
- Install automatically.
- Update course->blockinfo for each course at installation time.
- Modified course creation to insert into blockinfo field.
- Modified restore to insert into blockinfo field.
- Admin options (hide, show, delete, config) from admin page.
- Lang strings inserted (en only).
- Database support to mysql and postgresql (not tested!!).
Moodle, backup and block versions updated to 2004041800.
Tested with mysql: Install fresh and upgrade from previous.
section_activities block renamed to social_activities and created
its own lang file to support name "Social Activities". This can
be changed at any time.
TODO:
=====
Support it really in backup/restore.
????
Enjoy!! Ciao :-)
------------
I have a site which really needs this, so I went ahead with it already.
This add-on will cache formatted texts in the database and use them
for a specified timeperiod.
By default it is disabled. Enable it with:
$CFG->cachetext = 600; // in seconds
Logs now include a field called modid which contains the coursemodule id.
This makes it now possible to
- see complete logs per-activity
- do backup/restore of logs
The upgrade process will currently try to scan all the old logs and
rebuild this field based on available data (especially forums).
STILL TO DO: alter all the non-forum modules to send the coursemodule id
--------------------------------------
New functions and tables, based on work from Gustav Delius
(see http://moodle.org/mod/forum/discuss.php?d=4466)
This forms the core of a new system to store, track and utilise
event information in all modules, as well as allowing external
calendars to be synchronised with new information.
It's very early (it doesn't actually do anything yet!) but you can
define groups and get an idea of how the interface is shaping up.
I also wanted to show that I have actually done something on this! :-)
From here my plan is to add group support to the modules, one by one
(forums first), then go back and clean up some of the central interfaces,
graphics etc.
Finally, test, test, test and get 1.2 out well before the end of February.
