http://moodle.org/mod/forum/discuss.php?d=38604

I think it may be related to some setting in the config.inc.php file so I am including it here with this issue. Thanks to William Lu for reporting this.

Config.inc.php - It has been modified to pull the settings from the mdl_config table

settings.php - It has been extended to support the MRBS configuration options for the Site Identification and Calendar settings sections of the config.inc.php file

lang\en_utf8\block_mrbs.php - The required language files.

lang\de_utf8\block_mrbs.php - The required language files.

Jens

I think we need to clean up the visibility such that if periods are enabled then resolution, morningstarts, eveningends, morningstarts_min, and eveningends_min are grayed out and when periods are disabled then they are able to be edited. Otherwise, folks have to save the change and wait for the page to reload. I think it will be clearer (and more Moodle-consistent) making them dependent upon the periods enabled box.

Peace - Anthony

-MISC SETTINGS-

1. Maximum repeating entrys (max needed +1):
   $max_rep_entrys = 365 + 1;

1. Default report span in days:
   $default_report_days = 60;

1. Results per page for searching:
   $search["count"] = 20;

1. Page refresh time (in seconds). Set to 0 to disable
   $refresh_rate = 0;

1. should areas be shown as a list or a drop-down select box?
   $area_list_format = "list";
   #$area_list_format = "select";

1. Entries in monthly view can be shown as start/end slot, brief description or
2. both. Set to "description" for brief description, "slot" for time slot and
3. "both" for both. Default is "both", but 6 entries per day are shown instead
4. of 12.
   $monthly_view_entries_details = "both";

1. To view weeks in the bottom (trailer.php) as week numbers (42) instead of
2. 'first day of the week' (13 Oct), set this to TRUE
   $view_week_number = FALSE;

1. To display times on right side in day and week view, set to TRUE;
   $times_right_side = FALSE;

1. Control the active cursor in day/week/month views.
   $javascript_cursor = true; # Change to false if clients have old browsers
2. incompatible with JavaScript.

$show_plus_link = true; # Change to true to always show the link as in

1. MRBS 1.1.

$highlight_method = "hybrid"; # One of "bgcolor", "class", "hybrid".

1. Define default starting view (month, week or day)
2. Default is day
   $default_view = "day";

1. Define default room to start with (used by index.php)
2. Room numbers can be determined by looking at the Edit or Delete URL for a
3. room on the admin page.
4. Default is 0
   $default_room = 0;

-MAIL SETTINGS-

1. Set to TRUE if you want to be notified when entries are booked. Default is
2. FALSE
   define ("MAIL_ADMIN_ON_BOOKINGS", FALSE);

1. Set to TRUE if you want AREA ADMIN to be notified when entries are booked.
2. Default is FALSE. Area admin emails are set in room_area admin page.
   define ("MAIL_AREA_ADMIN_ON_BOOKINGS", FALSE);

1. Set to TRUE if you want ROOM ADMIN to be notified when entries are booked.
2. Default is FALSE. Room admin emails are set in room_area admin page.
   define ("MAIL_ROOM_ADMIN_ON_BOOKINGS", FALSE);

1. Set to TRUE if you want ADMIN to be notified when entries are deleted. Email
2. will be sent to mrbs admin, area admin and room admin as per above settings,
3. as well as to booker if MAIL_BOOKER is TRUE (see below).
   define ("MAIL_ADMIN_ON_DELETE", FALSE);

1. Set to TRUE if you want to be notified on every change (i.e, on new entries)
2. but also each time they are edited. Default is FALSE (only new entries)
   define ("MAIL_ADMIN_ALL", FALSE);

1. Set to TRUE is you want to show entry details in email, otherwise only a
2. link to view_entry is provided. Irrelevant for deleted entries. Default is
3. FALSE.
   define ("MAIL_DETAILS", FALSE);

1. Set to TRUE if you want BOOKER to receive a copy of his entries as well any
2. changes (depends of MAIL_ADMIN_ALL, see below). Default is FALSE. To know
3. how to set mrbs to send emails to users/bookers, see INSTALL.
   define ("MAIL_BOOKER", FALSE);

1. If MAIL_BOOKER is set to TRUE (see above) and you use an authentication
2. scheme other than 'auth_db', you need to provide the mail domain that will
3. be appended to the username to produce a valid email address (ie.
4. "@domain.com").
   define ("MAIL_DOMAIN", '');

1. If you use MAIL_DOMAIN above and username returned by mrbs contains extra
2. strings appended like domain name ('username.domain'), you need to provide
3. this extra string here so that it will be removed from the username.
   define ("MAIL_USERNAME_SUFFIX", '');

1. Set the name of the Backend used to transport your mails. Either "mail",
2. "smtp" or "sendmail". Default is 'mail'. See INSTALL for more details.
   define ("MAIL_ADMIN_BACKEND", "mail");

There shouldn't be an issue adding the other configuration options to the settings.php file. The question becomes however would adding all of the options be overwhelming for the average user. For example when I was working on adding the configuration options I had found that none of the categories in the admin menu had any more than 12 or so options. I would be wary that having the 30+ configuration options for the MRBS block could be overwhelming. (The list you posted above would add 20 items to the configuration screen) If there were a way to add sub categories under the mrbs block for each type of configuration (General, email, misc, etc) then it wouldn't be an issue.

As to using mdl_config_plugins in place of mdl_config, I could not find anything that was using the settings.php files that actually used that table. The only part of moodle that seems to use mdl_config_plugins is the authentication plugins. (The authentication plugins are all configured with the config.html files)

-Steve

Jens

Admin works well.

I have a problem, if I enrol as teacher over the ldap in moodle the booking system mrbs is not visible.

The config.inc.php is not configuered for ldap. Should I do configure for ldap?

I've looked at the revised changes to the MRBS block and have one observation:

The Settings "Entry type A" through "Entry type I" should most likely have a clearer "descriptive text" since it is not clear what the option actually does.

My suggestion would be to change the language string from :

$string['config_entry_type2'] = 'Entry type $a';

to

$string['config_entry_type2'] = 'These event types appear on the \'Add Entry\' screen. Every entry type is assigned a different color by default. Entry types are displayed in the following order: \'Entry A\', \'Entry B\', \'Entry C\', etc';

-Steve