Closed (fixed)
Project:
Public Bookings
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Reporter:
Created:
5 Dec 2008 at 12:20 UTC
Updated:
13 Apr 2009 at 23:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
kenorb commentedNothing in README.txt and documentation;(
Any help with this module?
Comment #2
kenorb commentedComment #3
twodA Resource is the item being booked. You can use this module to manage booking of multiple objects, each of their own type and at their own physical location etc. After digging through the code I noticed that resource handling is probably meant to be (atleast all GUI stuff) handled by the "resource-type plugins", of which atm there is only one: publicbookings.
Resource managment is not available unless you also enable the publicbookings module. You can then find it under admin/content/publicbookings/resource (appears as a sub-menu below Public bookings under admin/content).
I have yet to find a link to the page where one defines the availability for a resource though. (Not the default status, but the actual periods when a resource is available or unavailable). I ended up hacking my own link into the resources list, it goes to /admin/content/publicbookings/resource/RESOURCE_ID/availability/list. Without the ability to clearly define resources as strictly unavailable by default (when creating/editing it), as well as defining when the resource is actually available, would make this completely useless to me hehe.
Comment #4
Anonymous (not verified) commentedYou could add a repeating booking of a resource (at admin/content/publicbookings/booking/add ).
Let's say you have a computer that will be in service each friday between 13:00 and 14:00 - add a booking that repeats every week, use a friday as starting date, and enter the clock - this should give you the flexibility to set periods where resources are unavailable.
Comment #5
Anonymous (not verified) commentedActually it is a documentation problem related to Public Bookings, not Bookings API. It is correct that the documentation should state more clearly, that a resource has to be added before a resource can be booked - and perhaps the "booking-page" should not be enabled prior to adding resources.
Comment #6
Anonymous (not verified) commentedSee attached patch - this patch is only supplied to maintain a complete issue queue. It only adds a single line to the file README.txt stating that at least one resource has to be added.
Comment #7
kenorb commentedhttp://drupal.org/node/156119