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.
This is a course setting. By default it is off. When on, there
is a new link in the course admin menu for students, and they can
browse the same report that teachers see.
The report icon is temporary.
for recording the last access to the COURSE.
This is updated at the same time as add_to_log and is now used instead
of user->lastaccess when course user listings are required.
This means course listings now show what you expect and open up the way
for a "current users" listing and instant messaging etc ...
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.
that tells us how far to indent the activity when it is displayed.
This gives us some more flexibility on the course outline to
arrange things as we might like them, into subtopics etc
Backup/restore is updated as well.
There is also a bit more robustness in course/mod.php
that is much better than the proposal to change the role of course creators.
There is a new field in user_teachers called "editall", which is
ON BY DEFAULT, and allows teachers to edit courses. It can be modified
on the teacher editing screen (formerly assign teachers).
The value is cached in the session.
To test for it, there is a new function isteacheredit($course->id)
which works much like isteacher did.
I'm going through now and applying this new function wherever
it is needed.
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.
OK, some big changes here to the front end, particularly in
course categories and course display.
Course categories can now be nested (to any level).
Courses and course categories can now be manually sorted
any way required.
There is a groovy front end for managing these, and a better
range of options for formatting the front page.
It all still needs some polishing, which I'll be doing over
the next couple of days, including better auto-sorting.
I would not use this on production systems just yet.
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!)
Now these are saved in a new table called course_display,
each user and each course can have independent settings.
I'm intending to expand this table later for all the other
course display stuff (like hidden topics etc)
Course creators are managed by /admin/creator.php , same way that admins.
Or if authetication module have 'auth_iscreator'-function (right now only ldap-module have) ,
users are added to creators at login time.
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
Basically all the Database functions are in lib/datalib.php
and the web functions are all in lib/weblib.php, so
moodlelib.php is much thinner than it was.
Data functions have been extended ... most old calls will
still work, but now many more SQL commands can be performed
using the datalib functions rather than using SQL. I'm
currently moving through the whole tree replacing SQL
calls or at least concentrating them in one section of
mod/xxx/lib.php
Still working on forums, quizzes, surveys, resources.
The tree is currently not full working ... some things are
half-completed ... will resume tomorrow.
