1 min read
Hard and soft requirements for running MyBookaro.
Required #
- WordPress 6.0 or later (tested up to 6.9)
- PHP 8.1 or later
- MySQL 5.7 or later, or MariaDB 10.3+
- HTTPS recommended for production (required for Pro Calendar OAuth)
Optional #
- WooCommerce — required for Pro WooCommerce checkout.
- MyListing theme — for the MyListing Directory lane.
- Twilio account — for Pro SMS.
- Google Cloud project — for Pro Google Calendar sync.
- Real cron — recommended over WP-Cron for low-traffic sites.
PHP extensions #
openssl— required for Pro license signature verification.curl— used for outbound HTTP calls (Pro Calendar, Twilio, webhooks).mbstring— string handling.json— payload handling.
Compatibility notes #
| Component | Compatibility |
|---|---|
| Multisite | Site-level activation supported. Network-wide activation untested. |
| Headless / decoupled | REST API is fully usable. Frontend Vue apps designed for the WP frontend; bring-your-own-frontend possible. |
| Block themes (FSE) | All blocks work in Site Editor. Provider Dashboard / Customer Dashboard render server-side. |
| Page builders (Elementor, Bricks, etc.) | Shortcodes and blocks work in any page builder that supports either. |
| Caching plugins | Booking endpoints must not be cached. Most caching plugins exclude /wp-admin/admin-ajax.php and the REST API by default. Verify before launch. |
| WP Multilingual (WPML, Polylang) | Booking pages can be translated. Service titles per language not yet first-class. |
Browser support #
Provider Dashboard, Customer Dashboard, and the booking form are Vue 3 apps. Last two major versions of Chrome, Firefox, Safari, Edge. IE 11 not supported.
