Broken/missing handler: bookings_resources > default_availability

Comments

rodrigobb’s picture

Priority: Normal » Critical
rodrigobb’s picture

Priority: Critical » Normal
Anonymous’s picture

Do you need 1.x for some reasons? The list of bugs in 1.x is slowly growing and I'd prefer to concentrate on 3.x ;) (of course I'm going to fix 1.x bugs if 1.x is needed)

rodrigobb’s picture

I need Public Bookings and I need it for tomorrow ;).

I was testing 3.x but I'm afraid it isn't ready for a production enviroment though it will have very good new features (calendar view on top). And I think 3.x wont be available soon enough :(

So I have to use 1.x because my client needs it now :(

In fact I'm just following your directions:

Stay with 1.x unless you really, really know what you are doing, have backups and like to test software. And then: Please report back.

Anonymous’s picture

Okay ;) I'll look into the bugs

Anonymous’s picture

Project: Public Bookings » Bookings API
Version: 6.x-1.0-alpha5 » 6.x-1.x-dev
Assigned: Unassigned »
Status: Active » Fixed

It's actually a problem in Bookings API and it *should* be fixed with the last commit to BA 1.x-dev

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.