I've agreed with you (4 or more times now) that accesslib-related stuff is definitely very delicate, and that all significant changes should be posted as patches for general discussion and testing first (we already do this for lots of stuff). Regardless of this issue, it's a lot more efficient for most of us to work with CVS than git.
I'm not sure what you're looking for ... are you asking to personally review and vet every single change to anything related to accesslib from now on? How many peers are you talking about? I'd be ecstatic if you want to continue testing and working on accesslib issues, assuming you have time.
Martin Dougiamas
Posts made by Martin Dougiamas
Yep, but I think we're OK to go ahead in HEAD now, though. Quite a lot has been found and fixed in the past couple of weeks and it's looking like there are no major gotchas remaining. In addition, this is now holding up other work. Can you check it into HEAD today / tomorrow please? Thanks!
I wasn't aware that we overrode templates that way. If Guido's patch allows devs to provide their own templates while still using the default Moodle templates the rest of the time then it seems safe to put into HEAD and 1.8.
All you should ever need to do is add entries to the 'course' table. The rest should all be created automatically when the course page is viewed.
You can define things like default block configurations by adding things like this to your config.php:
// These variables define DEFAULT block variables for new courses
// If this one is set it overrides all others and is the only one used.
// $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
//
// These variables define the specific settings for defined course formats.
// They override any settings defined in the formats own config file.
// $CFG->defaultblocks_site = 'site_main_menu,admin,course_list:course_summary,calendar_month';
// $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,admin,course_list';
// $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
// $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
//
// These blocks are used when no other default setting is found.
// $CFG->defaultblocks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
You can define things like default block configurations by adding things like this to your config.php:
// These variables define DEFAULT block variables for new courses
// If this one is set it overrides all others and is the only one used.
// $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
//
// These variables define the specific settings for defined course formats.
// They override any settings defined in the formats own config file.
// $CFG->defaultblocks_site = 'site_main_menu,admin,course_list:course_summary,calendar_month';
// $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,admin,course_list';
// $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
// $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
//
// These blocks are used when no other default setting is found.
// $CFG->defaultblocks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';