Hi Angela,
I used the Activity Locking course format above 1.9.9.1 and followed the included instruction for a fresh install. I have tested/installed it after a moodle installation and also before the moodle installation i.e. the tables were installed along with all new tables. For any one using this I suggests testing it first on a test server with a new moodle installation and turning on debug - php error reporting to trace problems.
I quote the instructions provided by Chardelle below:
1. Put the blocks/activity_locking folder under your moodle/blocks folder.
2. Put the course/format/locking folder under your moodle/course/format folder.
3. To set activities to visible and provide warnings about prerequisites I altered moodlelib.php file:
3.1 backup your moodle/lib/moodlelib.php e.g. copy it and rename new file moodlelib.php.orig
3.2 open your moodle/lib/moodlelib.php file with a text editor (gedit, notepad; warning: in my experience sometimes when you edit a file in windows and your server is in unix or vice versa the file is messed up because of line endings and other hidden characters).
under the function_require_login find the following code:
/// If the site is currently under maintenance, then print a message
if (!has_capability('moodle/site:config', $sysctx)) {if (file_exists($CFG->dataroot.'/'.SITEID.'/maintenance.html')) {print_maintenance_message();exit;}}
3.3 paste in the following code below the above code:
//Check to see if Activity Locking criteria have been metrequire_once($CFG->dirroot.'/course/format/locking/locklib.php');global $cm;check_locks($cm);
I'm running things on an Ubuntu Lucid Lynx amd 64 server so I usually change the owner of the AL files by issuing the commands:
chown -R www-data.www-data *
If the AL course format is installed after an moodle install, hit notifications to update the database tables.
Hope this helps,
Roel