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.
OK, this is a big check-in with some big changes, and needs work still.
It seems relatively stable, but I need help identifying the rough patches.
1) First grading scales support. There is a now a new table called "scale"
that contains grading scales. There can be site scales (course=0) and
custom course scales. These can be used in modules - I've only done
forums for now but that was the hard one. Scales can be edited via
the new item in the course admin menu.
There is one default scale - the connected/separate knowing one that used
to be in forum. To build this I pull data from the language packs
to create one during the upgrade, or anytime a scales menu is called
and no scales are found.
2) New roles for course creator and teachers. I've fixed up the course
menus and some other things but there's a lot left to do on this to
make it all smooth. The idea is that teachers no longer can edit courses
unless they are also course creators. The interface for this needs to
be smoothed out a fair bit and I need help with this.
The upgrade will upgrade all teachers to be creators, but will default
the new site config "creatornewcourses" to "no", so that effectively
these new teachers have the same privileges.
3) Simplified teacher management. There is no longer an "assign teachers"
and a "teacher roles" page - it's all on one page in course/teacher.html.
Phew ... time for a shower and then back into it.
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!)
You can now hide/show individual activity modules and even delete them completely!
For example, if you hide the "choice" module, then all choice activities
will be hidden throughout the whole site, and "Choice" will not
appear on any "Add..." menu.
Deleting a module is a complete deletion of all data from the database.
If you want to try out the deletion on a real module, I suggest the
pgassignment module, since it will soon be deleted from CVS anyway
(because it's being replaced with workshop).
Look for "Manage modules" on the admin menu.
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)
- rename the main_frame variable to framename, because it
- might have caused some confusion
- none of the global variables have underscores
- put the config in the config table, with a default of _top
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
