bespokomatic Embedded Booked Scheduler
Go to file
Sam Black e72f10df96
Merge branch 'feature/admin_create_resources' into develop
2020-09-21 11:45:39 +01:00
.vscode Ignore booked directory for phpcs 2020-08-10 18:09:35 +01:00
admin Add resource types setting 2020-09-21 11:43:34 +01:00
includes Add resource types setting 2020-09-21 11:43:34 +01:00
languages Initial commit 2019-12-01 15:07:34 +00:00
public Use custom CSS to separate bootstrap CSS from WordPress CSS 2020-09-02 14:55:10 +01:00
.gitignore Ignore logging config 2020-08-10 14:48:41 +01:00
LICENSE.txt Initial commit 2019-12-01 15:07:34 +00:00
README.txt Add basic settings 2020-08-26 16:51:21 +01:00
bespokomatic-ebs.php Add user/group autocomplete 2020-09-05 13:27:55 +01:00
index.php Initial commit 2019-12-01 15:07:34 +00:00
uninstall.php Fix phpcs complaints 2019-12-01 15:22:23 +00:00

README.txt

=== bespokomatic-ebs ===
Contributors: bespokomatic
Donate link: https://www.bespokomatic.co.uk
Tags: booking, booked-scheduler
Requires at least: 5.3
Tested up to: 5.5
Stable tag: trunk
License: GPLv3 or later
License URI: http://www.gnu.org/licenses/gpl-3.0.html


Embed Booked Scheduler into WordPress.


== Description ==

Embedded Booked Scheduler from bespokomatic adds [Booked Scheduler](https://www.bookedscheduler.com) to WordPress.

This allows WordPress sites to create an integrated booking system, without the need for an external instance of Booked Scheduler.

This plugin is not affiliated with Booked Scheduler, and includes a copy of 2.7.7 under the GPLv3 or later licence.


== Installation ==

1. Upload 'bespokomatic-ebs' folder to the `/wp-content/plugins/` directory
1. Activate the plugin through the 'Plugins' menu in WordPress


== Frequently Asked Questions ==

= Can I use, or link to, a pre-existing Booked Scheduler installation? =

There is no functionality currently to allow this, but this might be available in the future.


== Screenshots ==

1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`
(or jpg, jpeg, gif).
2. This is the second screen shot


== Changelog ==

= 0.1 =
* Initial version.


== Upgrade Notice ==

= 0.1 =
Initial version.