E-cab Taxi Booking Manager for Woocommerce · Version history
E-cab Taxi Booking Manager for Woocommerce changelog and version history
- Latest version
- 2.2.9
- Nov 8, 2026 (2 days ago)
- Releases
- 5
- since 2025
- In the last year
- 4
- about one every 107 days
- Tested up to
- WordPress 7.1.4
- PHP 7.0 or later
Releases each year
- 20252 releases
- 20263 releases
20263 releases
E-cab Taxi Booking Manager for Woocommerce 2.2.9Latest
E-cab Taxi Booking Manager for Woocommerce 2.1.5
- Fixed: A vehicle set to “Combined Pricing Model” with the “Manual Pricing” route table filled in (per-route fixed fares) never showed up in a Manual-mode search (price_based='manual'), even for a route it had explicitly priced – the search only ever matched vehicles whose Pricing Model was set to “…
- Fixed: Searching with price_based='fixed_route' always failed with a “Please enter a dropoff location” error and a blocked Search button, even though Fixed Route mode has no drop-off field by design – the form’s drop-off validation only recognized Fixed Hourly as a mode allowed to skip that field.…
- Fixed: On price_based='manual' bookings, the Route Planning form and the map were stacked on top of each other instead of side by side, unlike every other pricing mode’s search page.
- Fixed: The Bookings list (Pro) showed a “Return” badge for round-trip bookings but never the actual return date/time, even when it had been captured – there was nowhere in the list to see it. It now shows next to the Return badge when available.
- Fixed (Pro): The Google Calendar sync (Settings > Google Calendar) only ever created an event covering the pickup leg, even for a round-trip booking with a captured return date/time – the return journey was silently left out, always ending a fixed duration after pickup regardless of when the vehicl…
- Fixed: A round-trip booking’s return date/time wasn’t shown on the Booking Detail page (Pro) or in the booking confirmation email, even when it had been captured. Both now show a Return Date row when available. (The PDF/thermal receipt already showed this correctly.)
- Fixed: A custom field added via Settings > Checkout Fields > Billing Fields (e.g. a “Flight Number” field) was collected at checkout and saved with the order, but never appeared on the admin order screen or in order emails – those only looked at a separate, older custom-fields list. Fields added th…
- Added: Checkout Fields > Billing Fields (text and select field types) now also work on a site using the WooCommerce Checkout block instead of the classic [woocommerce_checkout] shortcode – previously these fields only ever appeared on classic checkout, since the block checkout doesn’t use the same…
E-cab Taxi Booking Manager for Woocommerce 2.0.1
- Api issues resolved
- buffer time for other days issue resolved
- tax issue fixed
- decimel in extra service issue fixed
- xss vulnerbility fixed
- dropdown issue for manual pricing fixed
- date picker in admin issue fixed
20252 releases
E-cab Taxi Booking Manager for Woocommerce 2.0.0
- Openstreet map implemented
- extra service image issue fixed
- Safari/iphone price not showing issue fixed
E-cab Taxi Booking Manager for Woocommerce 1.3.1
- Drop off location can be hidden when it is hourly price
- Minimal rental duration can be added when it is hourly price
- Minor bug fixes
Questions about E-cab Taxi Booking Manager for Woocommerce’s releases
What is the latest version of E-cab Taxi Booking Manager for Woocommerce?
2.2.9, released on Nov 8, 2026 (2 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.0 or later.
How often is E-cab Taxi Booking Manager for Woocommerce updated?
4 releases in the last year, about one every 107 days. Its first release on WordPress.org dates from September 2025.
Know when your rivals ship
Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.
Start freeRelease dates come from the day each version’s folder was made in E-cab Taxi Booking Manager for Woocommerce’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.