anhskohbo

Thanks for reporting that. I will check your issue. And release will come the end of this week.

Sorry, the feature is not implemented yet.
Could you please open an issue for this on github repo: https://github.com/awethemes/awebooking/issues

The plugin has been stopped development for a while, but now I have planing to bring the plugin back.

Thank you!

• This reply was modified 3 years, 6 months ago by anhskohbo.

It’s the [awebooking_checkout].

We have an addon todo that (sync via icalendar), but it’s now public here. You can send an email to me to request that. [email protected]

(hope this not policy violation of here)

Closed

Seem this issue has been fixed. Close for now.

Hello, in the latest version (v3.2) we intro new “experiment fom style”, you will be able to control the limit of the date-picker at front-end as you want.

To enable going into: “Settings > Appearance > Enable experiment form style”

Date-picker setting available at: “Setting > Appearance > Datepicker”

Just pass the only_room attribute on the shortcode, e.g:

[awebooking_search_form layout="vertical" only_room="101"]

That’s funny, but I’m petty sure that you have an old version of awebooking (v3.0) in your local. And your theme has outdate. Activate with another theme should works.

Switch back to awebooking 3.0.x or update your theme match with newer version. Some functions has been deprecated or remove (@ ~ @).

Please, try to install the latest version. I think this would help because awebooking no longer requires taxonomy_single_term anymore and seem you’re working with an old version.

We’re working on that, v3.2 will come with

– Improve the appearance (new look)
– Improve the services
– Rest API
– …

But why?

Just a bit of CSS:

`
html{ font-size: 16px; }
`

Seem you custom your awebooking template. Find data-bind="value: checkInFormatted" and data-bind="value: checkOutFormatted" and append () after.

Ex:

data-bind="value: checkInFormatted()"

Or update your theme to latest version (if available).

Best Regards!

This has been fixed on the lastest version. Pls update.