Linux 软件免费装
Banner图

RideDesk Widgets - Taxi, Transfer & Chauffeur Booking Forms

开发者 ridedesk
更新时间 2026年9月8日 19:45
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

booking transfer rental taxi chauffeur

下载

1.1.0 1.1.1 1.1.2 1.1.3 1.1.4

详情介绍:

RideDesk Widgets puts your booking, enquiry and vehicle-rental forms on your WordPress site. It is the WordPress front door to RideDesk, the booking and dispatch software used by private-hire, airport-transfer and chauffeur companies to quote, dispatch, invoice and get paid. Drop a form into any page or post with a block or a shortcode. The visitor gets a quote-first booking flow with address autocomplete, a route map, and a price calculated from your own rate card. You get the booking in your RideDesk panel, already attached to the customer, the vehicle class and the campaign that produced it. The three widgets What you do not have to set up No API keys. No Google Cloud project, no billing account, no map credentials. Address autocomplete and routing are handled for you, falling back to open data when no commercial provider is configured. Nothing to renew, nothing to leak. No payment plumbing either. If you take payment online, the visitor is handed to RideDesk's hosted payment page, which uses your own Stripe, PayPal, SumUp or Mollie account. Card details never touch your WordPress site, so your site never becomes part of your payment security scope. Why the forms live on your RideDesk domain The plugin renders each form in a responsive frame served from your own RideDesk domain. That is a deliberate design choice with three consequences worth knowing before you install it. Contact Form 7 integration Already using Contact Form 7? Enable the bridge under Settings → RideDesk Widgets and every successful CF7 submission is ALSO filed as an enquiry in your RideDesk panel — spam-classified, your team notified, matched to the customer's booking history. Your existing forms and their emails stay exactly as they are. Conventional CF7 field names (your-name, your-email, your-tel, your-subject, your-message) are mapped automatically; developers can remap custom forms via the ridedesk_widgets_cf7_payload filter. Knowing which advert produced the booking A form inside a frame can only see the page it sits on, not the campaign that brought the visitor to your site three pages earlier. RideDesk Widgets closes that gap: an optional script records the arrival page, the referring site and any UTM tags for the length of the visit, and hands them to the form when the visitor actually books. Each booking then tells you which campaign and which landing page produced it. It sets no cookies, stores nothing a visitor types, and keeps what it does record in the browser's own sessionStorage until the tab closes. Untick one box to turn it off entirely. Usage Add the RideDesk Widget block in the editor, or use shortcodes anywhere shortcodes work, including page builders: Requirements A RideDesk account is required, with the Widgets add-on active. The forms render your organisation's live vehicles, rate card and settings, so there is nothing meaningful for the plugin to show without one. If you do not have an account, start at ridedesk.app before installing. The plugin itself is free and always will be. It adds no upsells to your admin, no dashboard widgets and no banners.

安装:

  1. Install and activate the plugin.
  2. Go to Settings → RideDesk Widgets and enter your RideDesk domain (shown in your RideDesk panel under Settings → Widgets).
  3. Add the RideDesk Widget block — or a shortcode — to any page.

屏幕截图:

  • The route measured on a map, then a live price per vehicle class straight from your own rate card.
  • The enquiry widget. Topics and extra fields are configured in your RideDesk panel.
  • Twelve languages. Pin one per shortcode, or let the visitor switch.
  • The frame resizes itself to its content, so the form fits any theme on any screen.
  • A dark palette for dark themes, set from the same four colours.
  • Colours and corner radius follow your brand. Set them once in RideDesk; no CSS to write.

常见问题:

Do I need a RideDesk account?

Yes. The widgets render your organisation's live booking forms, prices and vehicles from your RideDesk panel, so there is nothing for them to show without one. The plugin is the connector, not the booking system.

Do I need a Google Maps API key?

No. The plugin needs no API keys of any kind, and there is no key field to fill in. Address suggestions and route distances are served through your RideDesk account, which falls back to open data (Photon, OpenStreetMap and OSRM) when no commercial provider is configured. There is no Google Cloud project to create and no map billing to watch.

Will the forms match my theme?

Yes. Set four colours, a corner radius and light or dark once in your RideDesk panel and every embed follows, on every site. There is no CSS to write and no theme compatibility layer to break. The frame is transparent by default, so it sits on your own page background.

Does it work with my page builder?

Yes. There is a block for the editor and a shortcode for everything else, so anywhere that renders shortcodes will render the widget, including Elementor, Beaver Builder, Divi and classic widget areas.

Does it work with WooCommerce?

It does not need WooCommerce and does not use it. Bookings, quotes and invoices live in RideDesk, and online payment goes through RideDesk's hosted payment page on your own Stripe, PayPal, SumUp or Mollie account. If you already run WooCommerce for something else, the two simply coexist.

Can I use several widgets on one page?

Yes. Each frame measures and resizes itself independently, so a booking form and an enquiry form can sit on the same page without fighting over height.

Which languages are supported?

Twelve: English, German, Spanish, French, Italian, Dutch, Portuguese, Russian, Polish, Turkish, Swedish and Norwegian. Pin one per shortcode with lang="de", or leave it and let the visitor choose.

What happens if I deactivate the plugin?

The embedded forms stop appearing and nothing else changes. Your bookings, customers and settings live in RideDesk and are untouched. If you delete the plugin, it removes the handful of options it stored and leaves no tables or orphaned rows behind.

Why is the form not showing?

Check that your RideDesk domain is set under Settings → RideDesk Widgets, and that the Widgets add-on is active in your RideDesk plan. If your site enforces a strict Content Security Policy, allow frames from your RideDesk domain.

Will my bookings tell me which ad or page produced them?

Yes, with Visitor attribution left on (Settings → RideDesk Widgets). The booking form runs inside a frame, and a frame can only see the page it sits on — not the Google or Facebook campaign that brought the visitor to your site three pages earlier. The attribution script captures that on arrival and hands it to the form, so each booking in your RideDesk panel shows the campaign, the page the visitor landed on and the pages they read on the way.

Does visitor attribution use cookies or collect personal data?

No cookies, and nothing a visitor types. It keeps page paths, the referring site and campaign tags in the browser's own sessionStorage, and they are discarded when the visitor closes the tab. If you would rather not run it, untick it in the plugin settings.

How do I report a security problem?

Please report it privately by email to hello@ridedesk.app rather than in the public support forum, and give us a way to reach you for follow-up questions. We will confirm receipt and tell you when a fix ships.

更新日志:

1.1.4 1.1.3 1.1.2 1.1.1 1.1.0 1.0.0