Re: [MRBS-general] Separate timezone per area

[Campbell M. <cam...@gm...>]

Every user is able to see every area.     If you want to stop users in one
location from seeing bookings in another location, your best bet is probably
to have an MRBS installation for each area.      The same applies if you
want users in one location to be able to see bookings in all locations but
only to be able to book in their own location.   You could have a single
location but you'd have to modify MRBS - the function to change is
getWritable() in mrbs_auth.inc.    This function checks whether someone can
make a booking and takes the username room id as a parameter.  In standard
MRBS the room id is ignored, but you could use it to stop users booking
outside their own area.

 

Setting a timezone per area is a fairly easy modification.    You'll need to
add the timezone to the area table, modify the function get_area_settings()
in functions.inc and modify the area editing page to allow the timezone to
be changed.    It's something I've been meaning to do for a while, so if
you're interested I could have a look at it over the next couple of weeks.

 

Campbell

 

 

 

From: Chris Thompson [mailto:cth...@dt...] 
Sent: 29 November 2011 19:49
To: mrb...@li...
Subject: [MRBS-general] Separate timezone per area

 

I'm working on setting up MRBS. The company has multiple locations across
the country, from LA to New York. The plan was to setup a different area for
each city, but it appears the software isn't configured to allow for a
different timezone per area.

 

Has anyone thought about how to deal with multi-city installs? Is the
preferred method to have a separate installation for each office? As a PHP
developer, I'd be willing to invest some time into adding per-area timezone,
depending on the complexity of how to do that.

 

Is it possible to setup a user account that has access to only certain
areas, or is every user able to see all areas?

 

--

Chris