Title: KwaWingu Tours
Author: kwawingu
Published: <strong>November 22, 2026</strong>
Last modified: November 22, 2026

---

Search plugins

![](https://ps.w.org/kwawingu-tours/assets/banner-772x250.png?rev=3817178)

![](https://ps.w.org/kwawingu-tours/assets/icon.svg?rev=3817178)

# KwaWingu Tours

 By [kwawingu](https://profiles.wordpress.org/kwawingu/)

[Download](https://downloads.wordpress.org/plugin/kwawingu-tours.1.15.1.zip)

 * [Details](https://wordpress.org/plugins/kwawingu-tours/#description)
 * [Reviews](https://wordpress.org/plugins/kwawingu-tours/#reviews)
 *  [Installation](https://wordpress.org/plugins/kwawingu-tours/#installation)
 * [Development](https://wordpress.org/plugins/kwawingu-tours/#developers)

 [Support](https://wordpress.org/support/plugin/kwawingu-tours/)

## Description

KwaWingu Tours turns your KwaWingu operator account into a fast, SEO-friendly WordPress
site. It syncs your tour catalog into native WordPress content (Tours & Destinations),
gives you blocks and a one-click setup wizard, and lets guests book — without you
maintaining a separate site.

**Requires a KwaWingu Tours operator account with API access.** This plugin is a
GPL-licensed, open-source client for that service: it connects to the KwaWingu Tours
Developer API using your operator slug and API keys, and it does nothing without
them. API access is a paid part of your KwaWingu account (included in the Professional
plan, or bought separately), in the same way a payment-gateway plugin needs a merchant
account. The plugin itself has no paid tiers, licence keys, trials or locked features:
every block, shortcode and setting it ships works the moment your account’s API 
access is on. Whether your account has API access is decided by the KwaWingu servers,
never by this plugin: when access is off, the API answers `403 api_access_required`,
your synced tours keep showing, and wp-admin shows you one notice with the fix.

Your KwaWingu account also issues test keys (`kw_pk_test_`, `kw_sk_test_`). With
them the plugin talks to a private sandbox of your account (sample tours, bookings
that are never real, scripted test payments), so you can build and check the site
before you switch to live keys.

**What it does that a generic tour or booking plugin does not:** it does not ask
you to maintain a second copy of your tours in WordPress. Your catalog, prices, 
departures, seat availability, reviews, destinations and brand colours live in your
KwaWingu operator account, where your OTA channels and payment gateway already are,
and this plugin mirrors them into native WordPress content, reads prices and availability
live on every page view, and hands the booking and the payment to your account (
through your own payment gateway) so a seat sold on your site is the same seat sold
everywhere else.

**What you get:**

 * **Native content sync** — your tours become a `Tour` custom post type: real URLs,
   editable in WordPress, great for SEO. Removed tours are set to Draft, never deleted;
   once you edit a tour, sync stops overwriting your content.
 * **Blocks with editor UI** — Tours Grid, Tour Detail, Featured Tours, Book Button,
   Reviews, Destinations, Search, Trip Calculator, and Booking. Each has a live 
   preview and sidebar controls in the block editor. Classic-theme shortcodes included.
 * **Brand-true styles** — blocks are styled with your KwaWingu brand colours out
   of the box.
 * **One-click setup wizard** — auto-brands from your profile, scaffolds starter
   pages (Home, Tours, About, Contact), and imports your tours.
 * **Three booking modes**: _Redirect_ (send guests to your hosted KwaWingu booking
   page), _Widget_ (embed the KwaWingu booking widget), or _On-site_ (a full in-
   page booking and payment flow: scheduled departures, private and group trips 
   on a date the guest picks, accommodation levels, and payment through your own
   gateway). Your API keys never reach the browser: a same-origin server-side proxy
   holds them.
 * **SEO** — JSON-LD (Product / AggregateRating) + Open Graph on tour pages; local
   media for fast pages.
 * **Internationalization** — translation-ready (`.pot` included).

### External services

This plugin is a client for the KwaWingu Tours platform, operated by KwaWingu (https://
tours.kwawingu.com). It cannot work without it. Every external endpoint it talks
to is listed here, with what is sent and when. Terms of service: https://tours.kwawingu.
com/legal/terms — Privacy policy: https://tours.kwawingu.com/legal/privacy

**1. KwaWingu Tours Developer API**: `https://tours.kwawingu.com/api/v1/{your-operator-
slug}/…` (server-to-server, from your WordPress host). Used for: catalog sync (profile,
tours and destinations; branding in the setup wizard), live prices and availability
when a tour is displayed (reused for 60 seconds), tour search and the trip calculator,
and, in on-site booking mode or with the Inquiry Form, creating bookings, quotes,
inquiries and starting a payment. Data sent: your public or private API key in a
request header, the operator slug, and the parameters of the request. Catalog sync
and price reads carry no visitor data. Search and the calculator send only what 
the visitor typed into the form (search text, party size, dates). On-site booking
and the Inquiry Form send the guest details the visitor enters (name, email, phone,
message, chosen departure or start date, party size and accommodation level) to 
your own KwaWingu account so the booking or inquiry exists there. Visitors reach
the API only through a same-origin WordPress REST proxy on your site; the visitor’s
browser never contacts the API and never sees your keys.

**2. Hosted booking pages and widget**: `https://tours.kwawingu.com/{your-operator-
slug}/…` (from the visitor’s browser). In _Redirect_ mode, “Book” links send the
visitor to your hosted booking page; destination cards link to your hosted destination
pages. In _Widget_ mode, the plugin loads KwaWingu’s own embed script `https://tours.
kwawingu.com/widget.js` on pages where a Book Button is placed; it is served by 
the same service and renders your booking flow in the page. Data sent: the ordinary
browser request (IP address, user agent, referrer) plus your operator slug and the
tour slug in the URL or as data attributes. No script is loaded from anywhere else,
and none is loaded in _Redirect_ or _On-site_ mode.

**3. Cloudflare Images (KwaWingu’s image CDN)**: `https://imagedelivery.net/…` (
server-to-server, during catalog sync only). Tour cover and gallery photos in your
catalog are hosted there; the sync downloads them once into your WordPress media
library so your pages serve them from your own domain. Data sent: the image URL 
request from your server. No visitor data; nothing is loaded from imagedelivery.
net in a visitor’s browser.

**4. Your payment gateway’s payment page (on-site booking only)**: after an on-site
booking, KwaWingu starts the payment with the payment gateway you connected to your
own KwaWingu account. With a mobile-money gateway (Snippe) the guest approves a 
prompt on their phone and stays on your site. With Pesapal, DPO or PayPal, KwaWingu
returns that gateway’s payment page and the plugin sends the guest’s browser there
to pay (only `https` addresses are followed). Data sent: the ordinary browser request;
the payment itself is between the guest and your gateway. The gateway’s own terms
and privacy policy apply.

**5. Inbound: instant resync**: KwaWingu can call this site’s `POST /wp-json/kwawingu/
v1/resync` endpoint (signed with the secret shown in Settings  KwaWingu Tours) to
trigger a catalog sync a few seconds after you edit a tour. It carries no visitor
data.

Nothing is sent to KwaWingu on activation, and the plugin contains no analytics,
telemetry or tracking of any kind. Guest booking confirmations are emailed by KwaWingu
from your account; the optional owner notification is sent by your own WordPress
install with `wp_mail()`.

### Source code and build

The editor block bundles under `build/` are compiled with `@wordpress/scripts` from
the readable sources under `blocks/*/index.js` and `blocks/*/edit.js`, which ship
in the plugin. The full development repository, build instructions and test suite
are public at https://github.com/KwaWingu/kw-wp-plugin (`npm ci && npm run build`).

## Screenshots

[⌊Settings → KwaWingu Tours: operator slug, public API key, booking mode, private
key for on-site booking, operator notifications and lead capture, and the catalog
sync status.⌉⌊Settings → KwaWingu Tours: operator slug, public API key, booking 
mode, private key for on-site booking, operator notifications and lead capture, 
and the catalog sync status.⌉[

Settings  KwaWingu Tours: operator slug, public API key, booking mode, private key
for on-site booking, operator notifications and lead capture, and the catalog sync
status.

[⌊The one-click setup wizard after "Build my site": branding pulled from your account,
Home / Tours / About / Contact scaffolded, tours imported.⌉⌊The one-click setup 
wizard after "Build my site": branding pulled from your account, Home / Tours / 
About / Contact scaffolded, tours imported.⌉[

The one-click setup wizard after “Build my site”: branding pulled from your account,
Home / Tours / About / Contact scaffolded, tours imported.

[⌊The block inserter: all twelve KwaWingu blocks (Tours Grid, Tour Detail, Featured
Tours, Book Button, Reviews, Destinations Grid, Tour Search, Trip Calculator, On-
site Booking, Gallery, Availability Calendar, Inquiry Form).⌉⌊The block inserter:
all twelve KwaWingu blocks (Tours Grid, Tour Detail, Featured Tours, Book Button,
Reviews, Destinations Grid, Tour Search, Trip Calculator, On-site Booking, Gallery,
Availability Calendar, Inquiry Form).⌉[

The block inserter: all twelve KwaWingu blocks (Tours Grid, Tour Detail, Featured
Tours, Book Button, Reviews, Destinations Grid, Tour Search, Trip Calculator, On-
site Booking, Gallery, Availability Calendar, Inquiry Form).

[⌊Tours Grid block on the front end — synced tours with their cover photos from 
your own media library and live prices.⌉⌊Tours Grid block on the front end — synced
tours with their cover photos from your own media library and live prices.⌉[

Tours Grid block on the front end — synced tours with their cover photos from your
own media library and live prices.

[⌊Tour Detail block — cover, duration, difficulty, live price, next departure and
description, with the Book button.⌉⌊Tour Detail block — cover, duration, difficulty,
live price, next departure and description, with the Book button.⌉[

Tour Detail block — cover, duration, difficulty, live price, next departure and 
description, with the Book button.

[⌊Availability Calendar block — a month grid of a tour's departures with seats left.⌉⌊
Availability Calendar block — a month grid of a tour's departures with seats left
.⌉[

Availability Calendar block — a month grid of a tour’s departures with seats left.

[⌊On-site Booking block — a real departure picked, guest details, and the live quote
from your account before "Book & pay".⌉⌊On-site Booking block — a real departure
picked, guest details, and the live quote from your account before "Book & pay".⌉[

On-site Booking block — a real departure picked, guest details, and the live quote
from your account before “Book & pay”.

[⌊Trip Calculator block — the party and nights entered, with the estimate computed
by KwaWingu.⌉⌊Trip Calculator block — the party and nights entered, with the estimate
computed by KwaWingu.⌉[

Trip Calculator block — the party and nights entered, with the estimate computed
by KwaWingu.

[⌊Tour Search block — live results linking to the synced tour pages on your site.⌉⌊
Tour Search block — live results linking to the synced tour pages on your site.⌉[

Tour Search block — live results linking to the synced tour pages on your site.

[⌊Inquiry Form block — an inquiry that lands in your KwaWingu inbox and is kept 
as a Lead in WordPress.⌉⌊Inquiry Form block — an inquiry that lands in your KwaWingu
inbox and is kept as a Lead in WordPress.⌉[

Inquiry Form block — an inquiry that lands in your KwaWingu inbox and is kept as
a Lead in WordPress.

## Blocks

This plugin provides 12 blocks.

 *   KwaWingu Destinations Grid A grid of destinations.
 *   KwaWingu Trip Calculator Estimate a trip price live.
 *   KwaWingu Inquiry Form Send an inquiry to the operator directly from your website.
 *   KwaWingu Availability Calendar A month calendar of a tour's departures.
 *   KwaWingu Tour Search Live search across the operator's tours.
 *   KwaWingu Featured Tours A short, highlighted set of tours with a heading.
 *   KwaWingu Reviews Aggregate rating for a tour.
 *   KwaWingu On-site Booking On-site booking + payment for the current tour.
 *   KwaWingu Book Button A booking button for the current tour.
 *   KwaWingu Gallery A tour's photo gallery.
 *   KwaWingu Tour Detail Full detail for a single tour.
 *   KwaWingu Tours Grid A grid of your tours.

## Installation

 1. Install from **Plugins  Add New** (search “KwaWingu Tours”), or upload the plugin
    zip, or `git clone` https://github.com/KwaWingu/kw-wp-plugin into `wp-content/plugins/
    kwawingu-tours` (no build step is needed — the compiled block bundles are committed).
 2. Activate the plugin.
 3. Go to **Settings  KwaWingu Tours**, enter your operator slug and API keys, choose
    a booking mode, and save. Create the keys in your KwaWingu dashboard under **Settings,
    API keys**. Live keys need API access on your KwaWingu account: without it every
    API call answers `403 api_access_required` and the plugin tells you so in wp-admin.
    To try the plugin first, use the **Test** keys from the same page: they reach your
    private KwaWingu sandbox.
 4.  * The **public API key** is a _publishable_ key (`kw_pk_…`). Grant it `site:read`,`
       profile:read`, `tours:read`, `availability:read`, `departures:read`, `calculator:
       read` and `bookings:read`. If KwaWingu asks for an allowed origin, enter your
       WordPress site address (e.g. `https://www.example.com`).
     * The **private API key** (`kw_sk_…`) is only needed for the Inquiry Form and 
       on-site booking. Grant it the `inquiries:write`, `quotes:write`, `bookings:write`
       and `payments:write` scopes.
     * Use two live keys or two test keys, never one of each: the settings page warns
       about a mixed pair.
 5. Go to **Settings  KwaWingu Setup** and click **Build my site**.
 6. Visit your site.

## FAQ

### Do I need a KwaWingu account?

Yes. This plugin is a client for the KwaWingu Tours platform (https://tours.kwawingu.
com) and has no standalone mode. You need an operator account, your operator slug
and API keys: live keys need API access on the account, test keys reach its private
sandbox. Without them the plugin activates but has nothing to show.

### Can I try it before going live?

Yes, with the test keys from your KwaWingu dashboard (Settings, API keys, Test).
The plugin then syncs the sandbox’s sample tours and the on-site booking form books
in the sandbox: no guest is emailed and no money moves. Pay with +255700000001 (
paid at once), +255700000002 (fails) or +255700000003 (stays pending). A test-key
sync never drafts your live tours; switch to live keys and sync again before you
launch.

### Is the plugin itself paid? Does it lock any feature behind a plan?

No. The plugin is free and GPL-licensed, and nothing in it is disabled by a plan,
licence key, trial period or usage quota. It connects to the API access of your 
KwaWingu account, a paid part of that service, similar to how a payment-gateway 
plugin connects to your paid payment account. The only entitlement check is the 
one the KwaWingu API itself makes on every request; the plugin merely reports the
API’s answer (a 403) to the site owner and keeps your already-synced tours online.

### What happens if API access on my KwaWingu account lapses?

Your synced tour and destination posts stay published, editable and indexable. Live
prices, availability, search, the calculator and on-site booking pause with a visitor-
safe “not available at the moment” message, and administrators see one notice in
wp-admin linking to the dashboard page where API access is renewed (Settings, API
keys). Nothing is deleted.

### Are my API keys safe?

Yes. Keys are stored server-side and never sent to the browser. Interactive features(
search, calculator, on-site booking) call a same-origin, nonce-protected WordPress
REST endpoint that forwards to the KwaWingu API on the server. The private key is
only used for booking writes, server-side.

### Which booking mode should I use?

Start with **Redirect**: zero setup, always-correct availability, payment handled
by your hosted KwaWingu booking page. Use **Widget** to embed booking in a page,
or **On-site** for a fully in-page booking and payment flow (needs your private 
key configured). Redirect and Widget need the hosted booking pages switched on in
your KwaWingu account; the settings page warns you when they are off.

### Will it work with my theme?

Yes. Blocks are theme-agnostic and server-rendered; classic themes can use the `[
kwawingu_*]` shortcodes.

### Can I point the plugin at a staging or self-hosted KwaWingu?

Yes. Add `define( 'KWAWINGU_TOURS_SITE_BASE', 'https://staging.example' );` to `
wp-config.php` — the Developer API root becomes `KWAWINGU_TOURS_SITE_BASE/api/v1`
and the hosted booking links and dashboard link follow it. `KWAWINGU_TOURS_API_BASE`
can still be defined separately to override only the API root.

### How do tours stay up to date?

Tour content re-syncs automatically (hourly by default; configurable), via a “Sync
now” button, and instantly when KwaWingu pushes a change to the Instant resync endpoint.
Price, currency and sold-out state are not synced at all — they are read live from
your account on every page view, with the last synced values as a fallback if the
API is unreachable. Your manual edits to a tour are preserved on future syncs.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“KwaWingu Tours” is open source software. The following people have contributed 
to this plugin.

Contributors

 *   [ kwawingu ](https://profiles.wordpress.org/kwawingu/)

[Translate “KwaWingu Tours” into your language.](https://translate.wordpress.org/projects/wp-plugins/kwawingu-tours)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/kwawingu-tours/), check
out the [SVN repository](https://plugins.svn.wordpress.org/kwawingu-tours/), or 
subscribe to the [development log](https://plugins.trac.wordpress.org/log/kwawingu-tours/)
by [RSS](https://plugins.trac.wordpress.org/log/kwawingu-tours/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.15.1

 * WordPress.org review round 2. Activation now registers the tour and destination
   post types before it flushes rewrite rules, so their URLs work from the first
   request.
 * **Security: the booking, payment and inquiry rate limit keys on the connection
   address only.** Forwarding headers a visitor can set (`X-Forwarded-For`, `CF-
   Connecting-IP`) are no longer read. Sites behind their own proxy can supply the
   real address with the `kwawingu_tours_client_ip` filter.

#### 1.15.0

Brought up to date with the current KwaWingu Tours Developer API, checked call by
call against the API and live read-only requests.

 * **On-site booking books private and group trips.** Most safari catalogues sell
   PRIVATE trips on a date the guest picks, with no scheduled departures, and the
   form only offered departures. It now follows each tour’s booking models: a departure
   for joining tours, a start date for private and group trips, an accommodation
   level for tiered rate cards (e.g. Budget, Mid-range, Luxury), and an on-request
   note for tours that are only quoted.
 * **The guest pays the price they were shown.** The booking carries the `quoteId`
   of the live quote, and a price change while booking shows the new total instead
   of a generic error. Each attempt sends an `Idempotency-Key`, so a double click
   never books twice.
 * **Payment through your own gateway.** When your gateway has a payment page (Pesapal,
   DPO, PayPal), the guest is taken there; Snippe stays a phone prompt.
 * **Fix: private and group tours were shown as “Sold out”** on every grid and tour
   page (they have no scheduled departures by design).
 * **Fix: brand colours were never applied** (the profile fields are `brandPrimaryColor`/`
   brandAccentColor`).
 * **Fix: catalogues over 200 tours lost the rest at every sync**; over 100 tours
   lost live prices. Both are read in full now, and the sync never drafts a tour
   it could not see.
 * Availability Calendar and the departure picker read live availability (stop-sell
   dates and your minimum notice applied).
 * **Test mode.** Test keys (`kw_pk_test_`, `kw_sk_test_`) reach your private KwaWingu
   sandbox; the settings page and the booking form say so and list the test payment
   numbers, and a test-key sync never drafts live tours.
 * Current refusals: `402 plan_required`, `publishable_key_read_only` and `test_mode_unsupported`
   are reported to the site owner with the fix; notices link to Settings, API keys(
   or Billing) in your KwaWingu dashboard.
 * The settings page warns when Redirect or Widget would send guests to hosted booking
   pages that are switched off.
 * Uninstall also removes the stored brand and hosted-booking state.

#### 1.14.3

 * WordPress.org review round 1. Every plugin identifier now carries the full `kwawingu_tours_`
   prefix (options, transients, cron hooks, post meta, post types, admin-post actions,
   script/style handles, constants, JS globals); the old 3-character `kwt_` prefix
   is gone. Brand colours are now attached through `wp_add_inline_style()` on the
   block stylesheet instead of a hand-printed `<style>` tag, and the JSON-LD block
   is emitted with `wp_print_inline_script_tag()`.
 * **Security: the booking lookup and payment-intent proxy routes now require the
   per-booking portal token** (`X-Portal-Token`, issued once when the booking is
   created and validated by the KwaWingu API), in addition to the REST nonce. The
   deprecated ref+email booking lookup fallback is removed — without a token these
   routes answer 403 and point the guest at the “Manage your booking” link in their
   confirmation email. A payment intent is only created after a token-validated 
   lookup of the same booking proves ownership.

#### 1.14.2

 * **Destination cards now open the destination’s page on your hosted storefront**(`{
   hosted}/{operator}/destinations/{slug}`): what the place is, highlights, best
   months, the official park tariff on file and your tours that go there. They used
   to open the bare local `kwawingu_destination` post, which for most catalogue 
   entries was an empty page — so visitors left to search the web for the park instead.
   The sync keeps the API’s `slug` (`kwawingu_tours_slug`); a destination synced
   before this release links to the local post until the next sync runs.
 * WordPress.org submission hardening (Plugin Check clean, all categories): every
   block render template now guards against direct access; block render helpers 
   and template variables carry the full `kwawingu_tours_` prefix; API error messages
   are HTML-escaped when the exception is thrown; the Widget booking mode builds
   its `<script>` tag with core’s `wp_get_script_tag()`; `load_plugin_textdomain()`
   is gone (WordPress loads language packs itself since 4.6); uninstall also removes
   the recorded API status and the live-price caches; the release zip no longer 
   ships a `vendor/` directory — the plugin autoloads its own classes and has no
   runtime dependencies.

#### 1.14.1

Release follow-ups, found while capturing the WordPress.org screenshots from a live
install.

 * **Fix: every block button was invisible** (white text on a transparent background)
   and the brand colour never reached a block. The stylesheet set `--kwt-primary:
   var( --kwt-primary, … )` on the block roots — a custom property referencing itself
   is a cycle, which the browser treats as invalid — so “Book & pay”, “Estimate”,“
   Send inquiry” and the Book button had no background. Brand defaults are now plain
   values that your Branding colours override.
 * **Fix: the Inquiry Form had no styles and its spam-trap field was visible.** 
   A visitor who filled the stray box in had their inquiry silently dropped as a
   bot. The form is now styled like the booking form and the honeypot is off-screen.
 * **On-site booking polls with the guest’s portal token.** After “Book & pay” the
   form checks payment status with the `X-Portal-Token` the API returns when the
   booking is created — sent as a header, so it never lands in access logs — instead
   of the `?email=` lookup the API retires on 2027-07-01. The email lookup remains
   only as a fallback when no token was issued.
 * **Fix: the payment poll could never finish.** It compared the booking status 
   against `paid`/`confirmed`/`completed`, but the API’s status is upper-case and
   a booking is `CONFIRMED` the moment it is created, before any money. The poll
   now reads the balance against the total (exact minor units) and stops once a 
   payment has landed.
 * Translation template regenerated: 181 strings (it was empty), including the compiled
   block editor strings WordPress.org’s language packs are keyed on.
 * WordPress.org assets: ten screenshots, banners and icons.

#### 1.14.0

Found by running the plugin end-to-end against a real KwaWingu backend (WordPress
in Docker, every shortcode and block, the editor, the proxy, the paid gate). Nine
things did not work:

 * **Fix: no image was ever imported.** KwaWingu serves photos from Cloudflare Images(`
   imagedelivery.net/…/public`, no file extension) and `media_sideload_image()` 
   refuses a URL without one, so covers and galleries silently never reached the
   media library. Images are now downloaded and identified by their bytes.
 * **Fix: the Destinations Grid was always empty.** Nothing ever wrote a Destination
   post. Destinations are now synced from your catalog (`/site`) alongside tours.
 * **Fix: Tour Search never showed results.** The API returns `tours`, the block
   read `data`; results now also link to the synced tour page on your site.
 * **Fix: the interactive shortcodes were dead on classic themes.** `[kwawingu_search]`,`[
   kwawingu_calculator]`, `[kwawingu_booking_form]`, `[kwawingu_availability]` and`[
   kwawingu_inquiry]` rendered forms without their scripts, because WordPress only
   loads a block’s view script for the block.
 * **Fix: `[kwawingu_booking_form id=…]` and `[kwawingu_availability id=…]` ignored`
   id`** (and `slug`); the form bound to the page it sat on.
 * **Fix: the on-site form’s live price was never shown** — `POST /quote` needs 
   the private key, and the response field is `totalAmount`.
 * **Fix: the Trip Calculator showed the per-person figure as the total** and always
   labelled it TZS; it now shows `grandTotal` in your currency.
 * **Fix: the inquiry’s preferred date was dropped** (sent as `date`, the API reads`
   preferredDate`).
 * **Fix: listing all departures (`?tourSlug=`) returned a 502** — a WordPress REST
   quirk with `sanitize_title` as a sanitize callback.
 * Gallery block: a Tour Post ID control in the editor, so it can show a tour’s 
   gallery on any page.
 * Block titles now match the documentation (“KwaWingu Destinations Grid”, “KwaWingu
   On-site Booking”).
 * Calculator and search show the API’s visitor-safe message (“not available at 
   the moment”) instead of a generic error when the paid API is off.
 * `KWAWINGU_TOURS_SITE_BASE` constant to point a site at a staging/self-hosted 
   KwaWingu; proxy failures are written to the debug log when `WP_DEBUG` is on.

#### 1.13.0

 * **API refusals now say what to do — to the right person.** When the KwaWingu 
   Developer API refuses a request, wp-admin shows the site owner a notice naming
   the fix: enable the paid API add-on, correct the public key, or correct the operator
   slug. Visitors never see a status code or anything about plans and keys — interactive
   blocks show a quiet “not available at the moment” instead. The notice clears 
   itself on the next successful call.
 * **Rate limits and outages keep showing your prices.** If KwaWingu answers 429
   or 5xx (or cannot be reached), tour cards and tour pages keep the last live prices
   and availability the API returned (for up to a day) and retry a minute later,
   instead of dropping to the last synced values.
 * **Catalog sync errors** on the settings page use the same plain-language messages.
 * **Blocks are verified in CI**: a test now asserts every shortcode has a matching
   Gutenberg block with a `block.json` (API v3, editor script, server render) and
   a committed editor bundle, so a block can no longer silently vanish from the 
   inserter.
 * Tested up to WordPress 7.1.

#### 1.12.0

 * **Prices and availability are now read live.** Tour cards, tour pages and their
   structured data show the current price, currency and sold-out state on every 
   page view instead of whatever the last scheduled sync stored. If the API cannot
   be reached, the last synced values are shown — never an error or a blank price.
 * **Instant resync.** A new signed endpoint (`POST /wp-json/kwawingu/v1/resync`)
   lets KwaWingu tell your site to re-sync within seconds of you editing a tour.
   Copy the endpoint URL and signing secret from **Settings  KwaWingu Tours  Instant
   resync** into your KwaWingu dashboard.
 * Fix: changing the sync interval in settings now takes effect immediately. Previously
   the new interval was ignored until the plugin was deactivated and reactivated.
 * Fix: tour prices are read from the API’s `basePriceAdult` field, so synced prices
   are no longer always zero. Tour currency, category, gallery and rating fields
   are now mapped correctly too.
 * Prices render in the operator’s own currency rather than always TZS.

#### 1.11.0

 * Inquiry Form block (`kwawingu/inquiry-form`) and `[kwawingu_inquiry]` shortcode:
   visitors submit inquiries directly from your WordPress site; the operator gets
   an email notification and a Lead is captured in WordPress.
 * Contact page starter pattern updated to embed the Inquiry Form block.
 * Server-side proxy route `POST /wp-json/kwawingu/v1/inquiry` — nonce-guarded, 
   rate-limited, forwards via private API key to your KwaWingu inbox.

#### 1.10.0

 * Fix: interactive blocks (Search, Trip Calculator, Booking, Availability Calendar)
   now recover automatically on full-page-cached sites, where an expired security
   token previously broke them.
 * Release automation: publishing to the WordPress.org plugin directory on version
   tags.

#### 1.9.0

 * Testing: WordPress integration tests (wp-env) verifying block front-end render,
   CPT registration, and REST routes — run in CI.

#### 1.8.0

 * Operator notifications: get an email when a guest books on-site through your 
   site, and keep their details as a Lead in WordPress. (Guest confirmations are
   still sent by KwaWingu.)

#### 1.7.0

 * Availability Calendar block: a month grid of a tour’s departures with seats/sold-
   out status (and [kwawingu_availability] shortcode).

#### 1.6.0

 * Gallery: tour gallery images are imported into your media library and shown with
   a new Gallery block (and [kwawingu_gallery] shortcode).

#### 1.5.0

 * WordPress.org submission prep: refreshed readme (description, installation, FAQ,
   screenshots), brand assets (icon + banner), and translation (.pot) tooling.

#### 1.4.0

 * Testing: JS unit tests (Jest) for the booking payload, wired into CI alongside
   PHPUnit + coding standards + the block build.

#### 1.3.0

 * Block editor: every block now has a live preview + sidebar controls (limits, 
   filters, headings) in the WordPress editor.

#### 1.2.0

 * Front-end styles for all blocks (cards, grids, forms, reviews) using your brand
   colours.

#### 1.1.0

 * On-site booking now uses the live booking API: pick a real departure, see a live
   price, and book with correct guest details. Fixes a mismatched request that could
   prevent on-site bookings.

#### 1.0.0

 * On-site booking mode: book + pay (mobile money) without leaving your site.
 * Live blocks: Search, Trip Calculator, On-site Booking (via a secure server-side
   proxy — your API keys never reach the browser).
 * Internationalization (.pot) + text domain loading.
 * Hardening for WordPress.org: input/output security review, ABSPATH guards, blocking
   coding-standards check.

#### 0.3.0

 * SEO: JSON-LD (Product/AggregateRating) + Open Graph on tour pages.
 * Media: tour cover images are imported into your media library.
 * New blocks: Reviews, Destinations.
 * Widget booking mode (embed the KwaWingu booking widget).

#### 0.2.0

 * Blocks: Tours Grid, Tour Detail, Featured Tours, Book Button (+ shortcodes).
 * One-click setup wizard: auto-brand from your profile, scaffold pages, import 
   tours.
 * Redirect booking mode.
 * Sync safeguard: an empty catalog response no longer drafts your tours.

#### 0.1.0

 * Initial release: settings, API client, Tours/Destinations post types, and scheduled
   catalog sync.

## Meta

 *  Version **1.15.1**
 *  Last updated **2 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.1.5**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [booking](https://wordpress.org/plugins/tags/booking/)[safari](https://wordpress.org/plugins/tags/safari/)
   [Tour Operator](https://wordpress.org/plugins/tags/tour-operator/)[Tours](https://wordpress.org/plugins/tags/tours/)
   [travel](https://wordpress.org/plugins/tags/travel/)
 *  [Advanced View](https://wordpress.org/plugins/kwawingu-tours/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/kwawingu-tours/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/kwawingu-tours/reviews/)

## Contributors

 *   [ kwawingu ](https://profiles.wordpress.org/kwawingu/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/kwawingu-tours/)