## Blocks: MRBS

block_mrbs
Maintained by Davo Smith
Based on the stand-alone MRBS project ( http://mrbs.sourceforge.net ), this allows users to book rooms and other resources from within Moodle.
15k
738
2
Moodle 2.0, 2.1, 2.2, 2.3, 2.4

For a full description of this block, please see here http://docs.moodle.org/en/MRBS_block

A Moodle 1.9 version of this plugin can be downloaded directly here: https://github.com/arborrow/moodle-block_mrbs/zipball/MOODLE_19_STABLE - this is not available on Moodle.org as there would be a lot of work involved in rewriting it to pass the automated database naming checks.

### Contributors

• Thu, Jul 24, 2014, 6:43 PM
David,

The MRBS block initially contained a very lightly modified version of the MRBS application. However, over time, this has been changed to a much greater extent and is now completely incompatible with the latest version of MRBS. There has been some talk about starting again with a clean version of MRBS, but that would require some funding to complete and has, as yet, not come to anything.

There is no support for SSO to an external copy of MRBS, as the version of MRBS included in the plugin has been modified to directly check the Moodle login credentials.
• Thu, Jul 24, 2014, 6:46 PM
To follow up your second point, the permissions are checked at the system level, not at the course level. So, unless you have allocated anyone the role of 'student' at the system level (which would give them access to every course on the site), granting view MRBS permission to the student role will not grant access to MRBS.

You can either assign one of the custom MRBS roles to users at the system level (these roles are automatically created during install) or you can override the 'logged in user' role to grant 'view MRBS' access.
• Thu, Jul 31, 2014, 8:28 PM
Thanks, we've got it running (authenticated user has view MRBS permission). Things I can't find out how to do in settings (if it can be done):
- holiday hours (big thing for us, but worked around by adding a link to the web page with opening hours)
- stopping it allowing people to book appointments on days that aren't included in the 'display' settings (i.e. we've excluded Sunday from the week, and it still lets you go direct to that day and book appointments)
- stop anyone other than those users with mrbs-edit rights being able to see the name for the booking (data protection possibly)
• Thu, Aug 21, 2014, 9:19 AM
HI Davo,

I seem to have an issue where the View Day and View Week list at the bottom of the page are advancing a day ahead. (eg Says |25 Aug| but link is /blocks/mrbs/web/day.php?year=2014&month=08&day=26&area=8).

This is only happening with the menu at the bottom and none of the other dates (in the booking area or calendar view). Otherwise thanks for a great block.

Thanks Chris
• Wed, Feb 4, 2015, 10:30 AM
Dear Davo,

I have an issue in getting the report on meetings. When I go to generate the report, in the Summary of (Entries) Hours, all total hours are negative numbers. May I know where I should fix it?

Thanks.
• Wed, Feb 4, 2015, 11:05 AM
Dear Davo,

I found the problem now. There was a typo in the code report.php, line 201.
The first input argument should be &$item instead of &$row. Then, the computation of summary will be correct even if period is disabled.

Wish that this will be included in next version.

• Wed, Mar 4, 2015, 11:23 PM
HI Davo,
Thanks for this great block, which I've been very happy using for several years. We use periods I've always had some difficulties with British Summer Time. In the past, all booking appeared fine until the time change and then disappeared but could be recovered by using an SQL query to add or subtract 60 min from all the start/end times in the database. At some point, I noticed that this was no longer a problem and assumed that you had updated mrbs to cope with such timezone weirdness.
Now I have a new problem, any new booking for after the start of BST (29 March 2015) is saved and appears in the database but with an epoch timestamp for the GMT time rather than the BST time. This means the booking can't be seen in the web interface.
My server timezone is Europe/London and I've checked that PHP also believes the timezone is Europe/London
Can you possibly help me understand what's happening here?
thanks very much
Carol
• Wed, Mar 4, 2015, 11:25 PM
Carol - I've not made any recent changes to the block, so I'm not aware of any reason why the behaviour would suddenly change.

Davo
• Wed, Mar 4, 2015, 11:36 PM
Hi Davo, this might have been many months ago as the last time change was October 2014. I've also found an inconsistency between week view and day view - can I send you a screen grab?
Carol
• Wed, Mar 4, 2015, 11:40 PM
Carol - nothing has changed since long before then, apart from fixing a few warning messages - certainly nothing in the timezone handling code. Feel free to email a screenshot to moodle@davosmith.co.uk - but I can't promise a quick fix.

Davo
• Wed, Mar 4, 2015, 11:49 PM
Thanks Davo that's very kind of you. I've shared a google doc with you.
Carol
• Thu, Mar 5, 2015, 6:53 PM
Hi again Davo
My test server is now working properly The only difference I can see is that the date section of phpinfo has:

date.timezone Europe/London Europe/London

whereas my live server says:

date.timezone no value no value

I'm afraid it's my server configuration rather than anything in the MRBS block that's causing the problem - php.ini? I'm going to look...
Carol
• Thu, Mar 5, 2015, 6:58 PM
OK, I'm pretty sure that was it. On my live server:
grep timezone /etc/php5/apache2/php.ini
; Defines the default timezone used by the date functions
; http://php.net/date.timezone
;date.timezone =

but on working server:
date.timezone = Europe/London

I will have to wait to restart apache on live and will post if that wasn't the answer.
• Fri, Apr 17, 2015, 1:12 PM
Hi
Great block. Having been using it for years.

Query . .. How can I can change the colours of the meeting type.

TIA
Peter
• Fri, Apr 17, 2015, 4:28 PM
The colours are defined in blocks/mrbs/styles.css:
#mrbscontainer TD.A {background-color:#FFCCFF}
#mrbscontainer TD.B {background-color:#99CCCC}
#mrbscontainer TD.C {background-color:#FF9999}