Skip to content

Bookingfor/bookingfor-wordpress-plugin

Repository files navigation

BookingFor Wordpress plugin - V.3

Wordpress plugin repo for Bookingfor. BookingFor wordpress plugin is a free and open source web-based booking plugin for reservation multi hotel and multi merchant booking based on the service bookingfor. You must have a bookingfor subscription to use this open source booking plugin.

Demo: https://wordpress.bookingfor.com

This release is currently maintained and supported

Setup

  1. install Bookingfor Plugin;
  2. configure Bookingfor Plugin with your Subscription code, Bookingfor Apikey and Google Maps ApiKey;
  3. add Bookingfor widgets.
  4. enjoy!

Bookingfor engine

Every plugin work with his specified version of Bookingfor engine
This version required Bookingfor v.7.5

Requirements

Wordpress 4.8 +
PHP 5.6 +
cURL 7.40 +
OpenSSL 1.0.2 +
Bookingfor v.7.x.x

Compatibility

Polylang v. 2.2 +
WPML v. 3.7

Supported theme:
twentyseventeen
twentysixteen
twentyfifteen
Genesis (Agent Focused Pro)

Shortcode

[bookingfor_merchants category=1019 rating=4]
[bookingfor_resources categories=6,4]
[bookingfor_onsells]
[bookingfor_onsells order=asc]
[bookingfor_tag tagid=7]
[bookingfor_merchantscarousel tags=1,32]
[bookingfor_resources condominiumid=2]

Translations

To help in translation http://translate.bookingfor.com/collaboration/

How to override Bookingfor template files

You can edit the markup and template structure for front-end of your site in an upgrade-safe way using overrides.

Templates files can be found within the /wp-content/plugins/bookingfor/templates/ directory.

Copy the needed file into the directory within your theme named bookingfor (create if it does not exist), keeping the same file structure but removing the templates subdirectory.

For example, if you need to overwrite file /wp-content/plugins/bookingfor/templates/thanks.php, copy this file to /themes/themexxxx/bookingfor folder:

The copied file will now override the bookingfor default template file.

Do not edit these files within the core plugin itself as they are overwritten during the upgrade process and any customizations will be lost.