Hello,

We would like to use BOOK IT for the company's intranet.
Joomla is set up so that all authentication is done trough LDAP and our AD server as soon as we get to the booking screen we are getting following Error
BookingModelCustomer->setIdByUserId(): user with id 123 isn't active customer or admin

Even when I ignore this and still continue the reservation is created, but status is "canceled"

is there any way to get this working with LDAP as this is one of the main requirements set by our company.

thanks in advance


edit: I should probably add some info on versions we are using now.
PHP 5.3.10-1ubuntu3.6
Joomla! 3.1.1 Stable [ Ember ] 26-April-2013 14:00 GMT

Hello,

We never thought about LDAP, so this feature is not included in Book it! component. Book it! momentally work only with Joomla users. But I will add this feature to our project management.

Because we have already planned features for many releases, it will be added probably after many months. If you need this solution, we can offer you only custom paid support. If you are interested in, let us know on Diese E-Mail-Adresse ist gegen Spambots geschützt! Du musst JavaScript aktivieren, damit Du sie sehen kannst. (copy to Diese E-Mail-Adresse ist gegen Spambots geschützt! Du musst JavaScript aktivieren, damit Du sie sehen kannst. )

EDIT: That status canceled can be because of different settings. For example if you set only online payments in bookable item settings.
But generally it doesn't work with LDAP users and that you can create reservation, it is only because you create new Joomla user automatically.

The canceled status is indeed a result of LDAP user then as the reservation expiration is set to disabled, as all the items are free anyway, we would like to use this mainly for booking meeting rooms, parking spaces, beamers, and all sorts of internal material.
I will speak with our project manager and most likely we will send a mail.

thanks for the fast reply
Steven

Ok, we have planned free reservations for 2.1.0. So there will be some new features, like hidden payment methods and everything about pricing will be not visible. Maybe it will have effect also on order status after reservation.

But compatibility with LDAP is still good idea.