外掛標籤
開發者團隊
原文外掛簡介
Alura Booking helps hotel and accommodation businesses manage inventory and accept reservations through their WordPress website.
Features include:
Manage accommodation inventory, room types, rates, and availability.
Let visitors search for accommodation and proceed through a multi-step booking flow.
Collect guest details and review booking information at checkout.
Manage reservations and booking status from the WordPress dashboard.
Configure supported payment methods, including manual payment and available gateway integrations.
Set up booking notifications and customer emails.
Use frontend shortcodes to display booking forms, search results, room information, and booking-related pages.
Exchange unavailable dates through compatible iCalendar (.ics) feeds. Sync is periodic, not real-time, and does not synchronise guest data, rates, or reservations.
Some features require configuration of the relevant settings or third-party services. Payment gateway availability depends on the gateway credentials and setup.
External services
This plugin can connect to the following third-party services. Each one is used only when the site owner enables or configures it in the plugin settings.
Stripe (online card payments)
Used when Stripe is enabled as a payment gateway. When a guest pays, the booking reference, amount, currency and guest email are sent to Stripe (https://api.stripe.com) to create and verify the payment.
Terms: https://stripe.com/legal/ssa | Privacy: https://stripe.com/privacy
Razorpay (online payments)
Used when Razorpay is enabled as a payment gateway. The Razorpay checkout script is loaded from https://checkout.razorpay.com only when a guest chooses to pay with Razorpay. Booking reference, amount, currency and guest contact details are sent to Razorpay (https://api.razorpay.com) to create and verify the payment.
Terms: https://razorpay.com/terms/ | Privacy: https://razorpay.com/privacy/
Twilio (SMS notifications)
Used when Twilio is selected as the SMS provider. The guest phone number and the notification message text are sent to https://api.twilio.com.
Terms: https://www.twilio.com/legal/tos | Privacy: https://www.twilio.com/legal/privacy
MSG91 (SMS notifications)
Used when MSG91 is selected as the SMS provider. The guest phone number and the notification template variables are sent to https://control.msg91.com.
Terms: https://msg91.com/terms-of-use | Privacy: https://msg91.com/privacy-policy
Custom SMS webhook
If the site owner configures a custom SMS endpoint, the guest phone number, message text and event details are sent to the URL the site owner enters.
Frankfurter (currency exchange rates)
Used when multi-currency display is enabled. The plugin sends only currency codes (for example, USD and EUR) to https://api.frankfurter.dev to retrieve exchange rates. Rates are used to show estimated prices in the selected display currency; the actual booking amount remains in the configured base currency. No guest or booking data is sent.
The service is operated by the open-source Frankfurter project. It does not publish a separate terms of service or privacy policy; its statement that it does not collect or log personal data, IP addresses or request URLs is in the FAQ at https://frankfurter.dev, and its license is at https://frankfurter.dev/license/. Rates are stored on your site and refreshed at most about every two days, not on every page view.
iCalendar feeds (calendar synchronisation)
Used only when the site owner adds a compatible external iCalendar feed. The plugin downloads the feed URL entered by the site owner to block dates that are unavailable elsewhere. The site owner may share the private export URL generated by the plugin with another calendar system to publish availability. This exchanges calendar dates only; it does not synchronise guest data, rates, or reservations. No guest data is sent when importing a feed. The terms and privacy policy of the calendar provider whose URL is entered apply.
Source code
All JavaScript and CSS shipped with this plugin is human-readable and unminified. There is no build step, so no separate source repository is required: the files in admin/assets/ and frontend/assets/ are the source. No third-party JavaScript libraries are bundled. The Razorpay checkout script is loaded from Razorpay’s own servers only when a guest chooses Razorpay (see External services).
Getting Started
After activating the plugin, create the pages that visitors will use for booking. You can add shortcodes with the WordPress Shortcode block or Elementor’s Shortcode widget.
In Pages > Add New, create a page such as Hotel Search and add [alurbo_booking_search]. Publish the page and copy its full URL.
In Alura Booking > Settings, set the booking search page URL to the URL of the page you just published. Use your own site’s URL; page addresses vary by site.
To show results on a separate page, create a page such as Hotel Results, add [alurbo_available_rooms], publish it, and set its URL in the booking results page setting. If you leave the results URL empty, the plugin can show results on the search page.
Create a page such as Hotel Checkout, add [alurbo_checkout], publish it, and set its URL in the checkout page setting.
Add your locations, room types, rooms, rates, and availability in the Alura Booking dashboard. Configure payment and notification options you plan to use, then run a test search and booking.
The Alura Booking > Shortcodes page in the dashboard lists available shortcodes. Optional examples include [alurbo_availability_calendar months="2"] for an availability calendar.