Tripvance

Tripvance brings tours, activities and travel experiences to WordPress: a Tours post type, tour pages built from real fields, and a booking request form. It is a request and confirmation system: the agency answers each request. There is no payment processing. Tours Each tour has a gallery, a short description, highlights, an itinerary, what is included and what is not, a meeting point, and questions and answers. The itinerary is written a card at a time — press Add a day, give it a title and a description — and comes out in two shapes, picking the right one by itself: a run of numbered days for a trip of several days, and a timeline of times and stops for a day trip. A section with no data is not rendered, so a page never shows an empty heading. Tour layouts Seven layouts, each built for one kind of tour, all drawing the same content, prices and booking form: Salma (booking focused — gallery beside the two-step booking panel), Sara (marketplace product page with a price card that follows the reader), Atlas (multi-day — the route and the days across the page with a day index), Sahara (photo-first, no sidebar), Medina (compact, for city tours and short activities), Qamar (premium storytelling for private and luxury journeys) and Classic (simple and theme-friendly). Atlas has two styles (Clean, Zellige) and Sahara three gallery presentations (Cinematic, Immersive, Mosaic). The site picks a default and each tour can choose its own. Legacy layouts from earlier versions remain supported for existing tours. Tours are filed under destinations, tour types, departure points, trip lengths and categories, each with its own archive page and filters. Two kinds of travel business Tripvance ships two presentations of the same content, chosen under Settings → Website experience. Standard is what the plugin has always been: a catalogue with prices, availability and a booking form, and it is the default on every site. Luxury Editorial redraws the same tours, destinations and activities as a travel magazine, for a bespoke travel designer who sells a journey by describing it rather than by pricing it — journey collections, editorial destination pages, a page design with no price card, and a short private enquiry in place of a checkout. Switching between them changes nothing you have written, and there is no second catalogue to keep in step. Booking requests The form asks for a date, a party size and how to reach the traveller. By default it behaves as an enquiry system. If you enable seat-capacity enforcement, seats are held atomically against the departure while a request is open, so two simultaneous requests cannot both take the last seat. Requests are managed from a booking screen with a status workflow, internal notes and an operations dashboard. Transfers Private transfers (airport to hotel, city to city) are a post type of their own, at /transfers/{slug}/. Each transfer describes its route, pickup and drop-off, estimated duration, operating hours, minimum booking notice and practical information, and lists the Vehicle Types it offers with a price for each. Vehicle Types are reusable, customer-facing options (for example "Comfort minivan or similar") with a class, capacity, luggage, features and a picture; they are not public pages. A round trip is priced as two journeys in the same Vehicle Type. There is no distance-based or automatic pricing. The visitor chooses a Vehicle Type, a pickup date and time, passengers and luggage, and can add flight details. Capacity is checked in the browser and again on the server. The request becomes an ordinary booking record, with the same statuses, reservation ledger, messages, quotes and Guest Pass as a tour, and the price is stored with it when it arrives. In Operations, the Fleet holds the physical vehicles. A fleet vehicle can be linked to a Vehicle Type, and assigning one to a transfer booking warns when it does not match the requested type and is refused when it cannot carry the passengers. Fleet is optional: transfers can be booked without it. Privacy & Cookies An optional consent banner (off by default) with Necessary, Analytics, Marketing and Preferences categories holds back the scripts you place in it until the visitor accepts their category. It helps collect and honour consent; it does not by itself make a site legally compliant. Presentation Tour cards can carry a strip of gallery thumbnails along the foot of their picture: pointing at one, or tapping it, shows that photo in the card, so a visitor looks through a tour without opening it (Settings > Tour listings). Seven curated tour layouts, with style and gallery variants, chosen per tour or site wide, on one shared foundation (legacy layouts from earlier versions remain supported for existing tours): a sticky section navigation, a booking ticket beside the price, a route at a glance, an itinerary drawn as days or as a timeline, group rates, questions and answers, and reviews. The plugin inherits the theme's typography and loads no fonts of its own. Listing pages with filters, sorting and cards; a Tours block and a [wptm_tours] shortcode for a grid of tours anywhere, and [wptm_activities] for a grid of activities — each activity can carry its own price and take booking requests directly through the same request system as a tour; a homepage template assembled from your tours, destinations, activities and trust details; and a car hire template for the driving side of the business — the fleet, the services, the routes you cover and the prices you quote. Multilingual Tripvance uses the WordPress translation system throughout and is ready for community language packs from translate.wordpress.org. It also includes built-in French, Spanish and Arabic front-end fallbacks, with right-to-left layouts for Arabic. Polylang is supported properly, not nominally. Tours, activities and every taxonomy the plugin owns are registered as translatable. Tours, terms and the pages the plugin generates are given their language and linked to their translations, so a language switcher lands on the right page. A generated page is written in its own language, not in the language of whoever pressed the button. Booking requests record the language the traveller was reading, and the confirmation, the voucher and the reminder are all written in it. Wording you type yourself — the homepage, the car-hire page, the default inclusions — appears under Languages > String translations so it can differ per language. Addresses can be translated too, and are not by default. Switch on "Addresses per language" in the settings and a French page becomes /fr/circuits/ rather than /fr/tours/, with the destination, category, departure and trip length sections following it; the words come from the same translation catalogue. The addresses you already have keep working and redirect to the new ones. Leave it off and no address on the site changes, whatever language packs are installed. A site that generated its pages before adding a language can put them right from the settings screen: each page's title, starting wording and address go back into its own language, a page you have edited is left alone, and the previous address redirects. An optional language switcher goes into the theme's own menus — desktop header, mobile menu, footer, or a shortcode wherever you like — and each language links to the translation of the page the visitor is on: a French reader on an English tour lands on the French tour. Polylang decides which page that is and keeps printing the hreflang tags; Tripvance only draws the control, in the menu's own typography, with no flags, no external assets and no second translation system. Without Polylang the plugin runs unchanged. Search engines Tripvance prints no canonical tag, meta description or Open Graph markup, and no site-wide schema. Those belong to an SEO plugin, and two sources for one signal is worse than one. Tripvance provides limited Product structured data for eligible Tour and Activity pages, including accurate pricing and genuine on-site review aggregates. When Rank Math is active, Tripvance integrates with its structured-data graph to avoid duplicate Product entities. General SEO and site-wide Schema remain under the control of the site's SEO plugin. In practice: a price is included only when it is the price the page shows and a traveller can book (one Offer at the public "From" price — the fixed price, or the lowest valid Group Rate; nothing for a tour on request), and a rating only from approved reviews of that tour, when the page shows the same average and count. Nothing is added to the homepage, archives, taxonomy pages, FAQs or private views such as booking confirmations and Guest Passes. The setting is under Tripvance > Settings > Search result product data. Structured data makes a page eligible for rich results; search engines decide whether prices or review stars are shown, and it does not affect ranking. It also emits clean semantic markup, keeps taxonomy archives crawlable, marks empty ones as noindex, and keeps them out of the sitemap. Import Existing WooCommerce products can be imported as tours, with a dry run first that reports exactly what would happen and creates nothing.

2.8.10 Guided setup. Nothing changes on an existing site by updating: no address, price, currency, design or setting is touched, and the wizard never opens by itself.

• New: Setup wizard under Tripvance → Settings → Setup wizard — four short steps (currency, addresses, design, review) with Back, Continue and a way out; choices are kept between steps and saved only by Apply settings, in one write, verified before success is shown.
• A new installation is greeted once with "Welcome to Tripvance" (Start setup / Later). It replaces the setup guide's welcome notice; the guide itself stays under Settings.
• Currency: the currencies the settings already offer, with a price example in the plugin's own format. Nothing is converted, and the default cannot be changed from the wizard while a tour, activity or transfer without its own currency, or a booking without a stored one, depends on it.
• Addresses: the tour and activity address words, with a preview on your domain. Editable only on a new site with no tours, activities, transfers, bookings, tour terms or menu links, with pretty permalinks and without per-language addresses; checked on the server against pages, other post types and taxonomies, existing rewrite rules, reserved words and language codes. Rewrite rules are rebuilt once after a valid change. Everywhere else they are shown read-only.
• Design: the default tour design and activity layout as cards with the plugin's own miniatures; tours and activities with their own design keep it, and the review says how many follow the default.
• Fix: choosing a design in the setup guide on a site whose settings had never been saved switched the activities and other switches off.
• Addresses can be chosen only on a site recorded as a clean first installation at activation, and only until the setup is completed; updated, reactivated and emptied sites show them read-only. Custom addresses already saved are kept.
• The step indicator saves the open step like Back and Continue (also without JavaScript); a form from another or a duplicated tab no longer overwrites newer choices; a change made in Settings while the wizard is open is shown for review instead of being overwritten.
• The currency lock follows the price engine's own reading (missing, empty or invalid codes) and the payment ledger's (bookings with no snapshot, quote or revision).
• Fix: the Tripvance menu icon showed black until the page finished loading. It is now drawn by CSS in the admin colour scheme's colours from the first paint.
• Setup wizard: every change to a draft (Back, Continue, the step indicator, Apply settings) is read, checked and saved under a short lock, so two tabs pressing at once cannot overwrite each other; viewing a step no longer rewrites the draft.
• Setup wizard: a booking counts as priced in the default currency when its price snapshot is missing, damaged or has an unreadable currency, unless an accepted quote or a revision with a valid currency takes precedence.
• Operations: a clearer header with the two manifest buttons, a wrapping "On this page" bar that scrolls inside itself on phones, calmer empty states, and trip rows showing customer, crew and payment state, as cards on phones. Nothing it lists or checks has changed.

2.8.9 Site pages and the page builder. No page is deleted, recreated, published, added to a menu or made the front page by this update; existing content, IDs, addresses, templates, translations and SEO fields are untouched.

• Tour and activity editor: the title stays above every section; Inclusions in three groups (highlights, included / not included side by side, what to bring) with eight suggestions and "Show all suggestions"; a suggestion already in the list is marked and never added twice. No data changes.
• Fix: pages made from a starter lost characters — quotes in block settings became "u0022" and backslashes disappeared — because the markup was not slashed for wp_insert_post(). SEO titles and descriptions with a backslash were cut the same way.
• Fix: with JavaScript on, every page builder, homepage and car hire save went to a wrong address and failed ("could not reach the server"); the form's "action" field hid its address.
• Fix: an ordinary save no longer moves a page with its own template (a theme's, a landing page's) to the default one, and no longer reports a failure for a template the active theme does not list.
• New pages are written in the page's language, with the language chosen first; destinations and tour types are found by search in that language, checked on the server, cleared when the language changes; a page for the same starter, term and language is pointed out; typed values survive a failed attempt; a double click makes one page.
• Site pages list: search, kind, language and status filters and real pagination over every managed page (homepage and car hire with all translations, index, landing and starter pages), last modified, Polylang translations, the right editor per kind, and "Add to Site pages" for other pages with Tripvance sections.
• Page builder: Content and Page settings & SEO tabs, section summaries, Duplicate, keyboard moves, real statuses (draft, pending, private, scheduled, published), "Save draft" versus "Update the published page", save-then-publish, a non-blocking "Before publishing" check, and an optional visible page title.
• Starter FAQ answers and the call to action are now bracketed notes instead of promises about booking or payment.
• Site pages: Move to Trash from each page's ⋮ menu, with a confirmation and Undo; the front page and the posts page are protected, and nothing is ever deleted permanently.
• Fix: the builders no longer show the plain form (Order boxes) for a moment before the builder appears; a loading state is shown instead, and a clear notice with the plain form if the builder cannot start.
• Builders: an optional name for each section (shown in the editor only), a short summary on each section card, a focal point picked on the photograph (stored in the existing Focal point field, also new for the standard hero), and Copy style / Paste style between sections.
• Fix: builder buttons sometimes did not respond — a click with a little mouse movement started a drag of the whole row, and buttons were re-created under the pointer after typing. Only the handle drags now, and the list no longer re-creates its buttons.
• Fix: after undoing a removal, two settings panels could show at once.
• Our purpose: commitment columns get equal width; the larger photograph option now sets the commitments as aligned rows beside a half-width photograph instead of squeezing them.
• Section builder for the homepage and site pages: a section library with search and drawings, drag or keyboard reordering, "Add a section here", Content / Design / Spacing tabs, duplicate, hide, remove with undo, Undo/Redo, per-page design settings, starter layouts, templates, and JSON export/import. Unsaved homepages render exactly as before; the first save keeps a copy of the old settings.
• Custom HTML blocks are no longer limited to five, each with its own label and place; the old five slots keep their content, order, visibility and translations.
• Three call to action layouts (band, split with image, card) and per-section spacing and background.
• Homepage builder: grouped navigation in page order, find a section or setting, section summaries, keyboard moves, a preview that says which version it shows at true device widths, and the protected JSON save (it used to fall back to a plain POST).
• Our purpose: titles and sentences aligned across columns, and an optional larger photograph. Moroccan Editorial Carousel: the corner motif and the flourish are removed.

Bookings dashboard, bookings list and booking screen. No booking, price, payment, seat or status rule changes, and nothing is sent or changed by viewing or filtering.

• Dashboard: search, Add booking and a More actions menu; four figures — requests to answer, follow-ups due, trips today, trips tomorrow — each opening exactly the bookings it counts, in the site's time zone; Needs attention; upcoming trips; the calendar; the week's figures, sources and most requested trips folded away.
• Needs attention: stable reason keys and ranks (unconfirmed trip within a week, transfer without the driver or vehicle the agency keeps, payment claim to check, follow-up due, no reply, open balance before a trip), the most urgent first, one action that opens the right panel, further reasons behind a disclosure, and View all.
• Quick view from the list and the dashboard: a read-only side panel fetched per booking with a nonce and the capability on that booking; loading, failure and retry states; Escape, focus return and background scroll lock.
• Bookings list: Today, Tomorrow, Next 7 days, Follow-up due and Needs attention filters; tours, activities, transfers and custom trips; payment state (from the ledger's index, now also refreshed when a customer reports a payment or accepts a quote); the applied filters with Reset; search by phone number however it is written; a payment tag distinct from the status; compact cards on phones; All bookings returns to the filtered list.
• Booking screen: Save changes, and after a save one report of what was saved and what was not, with a link to the panel to correct; changed fields are marked until saved; clearer action labels (Record payment, Issue PDF, Preview draft PDF, Save assignments, Mark as sent, Retry sending, Email the guest link, Create quote draft).

Earlier versions The full history of every release is in changelog.txt, shipped with the plugin.