Description
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.
A transfer can also list the stops on the way (Marrakech Tizi n’Tichka Ait Ben Haddou Ouarzazate), each with an optional description and stop time, drawn on the page as a route line — typed by the agency, never looked up or drawn on a map — and its own questions and answers, shown as an accordion. The transfer page leads with the route, the duration and the starting price, then the vehicles and the request form, then the practical information, the questions and the photographs (with a viewer). The optional transfer list at /transfers/ and the homepage Transfers section show transport cards (route, duration, capacity and «from» price); the homepage section offers three layouts: Classic Cards, Route Focus and Premium Transport.
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.
Privacy
Booking requests and operational records are stored in the site’s database. These can include names, email and WhatsApp/telephone numbers, country, travel dates, party sizes, pickup details, messages, quotes and records of payments received outside the site. Transfer requests can also include a drop-off address, pickup and return times, luggage and flight details. Notifications use wp_mail() and the mail provider configured by the site owner. Tripvance sends no telemetry to its developer and loads no remote fonts.
WordPress personal-data export and erasure tools are supported for bookings matched by email, including bookings in the trash; transfer bookings are exported with their route, pickup, drop-off, return and flight details. Erasure removes identifying booking fields, campaign attribution, email queue/history and free-text history notes, clears linked reservation emails and pickup details, and revokes private links. Non-identifying booking, quote and payment records are retained. For requests without an email address, the operator must identify the relevant records manually. Backups and mail already delivered by the site’s mail provider are outside this eraser.
Optional first-party campaign attribution uses the wptm_attr cookie for up to 30 days. It stores UTM values, referral code, referring host (not the full referring URL), first tour visited and timestamp. It is read or written only when the visitor has consented to analytics; without consent it is disabled and an existing cookie is expired on the next uncached page request. Booking totals and manually entered attribution remain available. Consent is taken from the WordPress Consent API when a consent manager configures opt-in mode, otherwise from the Analytics choice in Tripvance Privacy & Cookies when that module is switched on. Other integrations can supply the visitor’s consent through the wptm_attribution_consent filter. Do not return true globally as a substitute for visitor consent.
The optional Privacy & Cookies module (off by default) stores the visitor’s choice in one first-party cookie, wptm_consent, holding the accepted categories, the consent version and a timestamp.
Tailor-made trip requests store the name, email address and, when given, telephone, country and message a traveller enters, with their travel preferences. Nothing is sent or stored while they move between the wizard’s steps; the request is saved once, when they press Send. Requests are private, excluded from search, feeds, REST and sitemaps, and are covered by the WordPress export and erasure tools (erasure keeps the reference, dates, length and party size).
Issued quotes, invoices and trip programmes are stored in the site’s database as frozen copies of what they printed (the customer’s name, the billing details an operator entered, the trip and the prices), together with the PDF file as issued. They are never written to the uploads folder, and a customer can download one only when the agency shared it, through their own Guest Pass or quote link. Erasure keeps issued invoices, which are accounting records, and removes the booking’s quote and programme documents.
Anti-abuse counters use salted hashes of the requesting IP address with expiring transients. The raw IP is not stored in those counters. Private Guest Pass, quote and voucher links act as access keys and should be shared only with the intended traveller.
Third-party libraries
- TCPDF 6.11.4 by Nicola Asuni — https://tcpdf.org — LGPL-3.0-or-later (vendor/tcpdf/LICENSE.TXT). Bundled to produce PDF documents on the site’s own server; trimmed to the engine and two fonts.
- DejaVu Sans fonts — Bitstream Vera and Arev fonts licence, public-domain changes (vendor/tcpdf/fonts/DEJAVU-LICENSE.txt).
External services
No external service is required for the core booking workflow. Site owners choose the optional links, media and mail service they use and should reflect them in their privacy notice.
- WhatsApp: contact buttons open
wa.meafter a click and may include a prepared message. No WhatsApp API or automatic WhatsApp messaging is included. Terms: https://www.whatsapp.com/legal/terms-of-service ; Privacy: https://www.whatsapp.com/legal/privacy-policy . - YouTube and Vimeo: an operator-supplied video URL can be embedded through WordPress oEmbed; WordPress may request embed metadata and the visitor’s browser connects to the video host when displayed. In the Luxury Editorial experience, a YouTube address pasted into the Video field of the hero or the full-bleed story is embedded directly from www.youtube-nocookie.com and plays on its own, silently, as the background of that one section; nothing is requested from any video host on a site that has not supplied such an address, no script is loaded from a third party at any point, and the embed is never created for a visitor whose browser asks for reduced motion or reports a slow or metered connection. YouTube terms: https://www.youtube.com/t/terms ; Google privacy: https://policies.google.com/privacy ; Vimeo terms: https://vimeo.com/terms ; Vimeo privacy: https://vimeo.com/privacy .
- Google Maps and Search: optional meeting-point and weather links open after a click and include the selected place, coordinates or weather query. Terms: https://policies.google.com/terms ; Privacy: https://policies.google.com/privacy .
- External media: if an operator enters a remote image or direct video URL, the browser requests that host when the media is displayed. Use the WordPress media library to serve these assets from the site itself.
- External payment links: an operator may provide a PayPal or another payment link. The link opens its provider after a click; Tripvance does not process the payment or receive card details. PayPal terms: https://www.paypal.com/legalhub/useragreement-full ; Privacy: https://www.paypal.com/legalhub/privacy-full .
Screenshots
Blocks
This plugin provides 1 block.
- Tours Tour cards from your catalogue, as a grid or as the Moroccan Editorial Carousel, filtered by destination, type, category, duration or departure.
Installation
- Upload the plugin folder to
/wp-content/plugins/, or install it through Plugins Add New. - Activate it. Tripvance prepares its required database tables, options and capabilities, but creates no tours, terms, pages or demo content automatically.
- A one-time notice offers a starter kit (tour types, durations, sample destinations, a Destinations page, a Tour Types page and two landing pages). Create it in one click, or dismiss the notice and build your own structure. The same buttons stay under Tripvance Settings.
- Go to Tripvance Settings to choose the booking behaviour, contact details and tour-page design. Currency is set on each tour’s pricing fields.
- Add a tour under Tours Add New.
FAQ
-
Can travellers ask for a tailor-made trip?
-
Yes. Tripvance Tailor-Made Requests Settings has a «Create Trip Builder Page» button, or lets you choose an existing page; nothing is created until you press it. The page shows a step-by-step wizard (dates, length, interests, destinations, travel style, accommodation, travellers, budget, contact) whose steps and answers you manage on the same screen. Requests are private records with a TMR reference, separate from bookings, and «Create Draft Tour» starts a draft tour from one. The
[tripvance_trip_builder]shortcode and the Trip Builder block place the wizard anywhere. An optional «Plan your own trip» call to action on tour pages is off by default. -
Is there a setup guide?
-
Yes. After activation a dismissible welcome offers a step-by-step guide (Tripvance Settings Setup guide): tours, homepage and its preset, tour design, booking. Every step reads your site as it is and only offers what is missing; nothing is created or changed without a button pressed for it. The guide also offers demo content — sample tours, activities and destinations, every item marked as demo — with a one-click removal that never touches your own content. The guide can be restarted from Tripvance Settings.
-
Is there a homepage?
-
Yes. Tripvance Site pages Homepage creates a page on the «Tripvance homepage» template and fills it from what the site already has. Its hero can be a classic image cover, a muted looping video with accessible playback and optional sound controls, a split featured-tour spotlight, layered floating image stories, or an animated travel-colour mesh. The same buttons, optional reassurance points and five tour-search designs adapt to every hero; search can be hidden entirely. The rest includes featured tours, destinations and tour types with their counts, a signature tour, activities, trust, «why choose us», articles and a final call to action. Sections can be switched off and reordered; a section with nothing to show is not printed. Setting the page as the site’s front page is a separate, explicit button.
-
Is there a car hire page?
-
Yes. Tours Car hire creates a page on the «Tripvance car hire page» template, built the same way as the homepage: sections you tick and order, a preset to arrange them, a preview before anything goes live. It holds a hero, a fleet with a filter by kind of vehicle, the services a driver is hired for, a table of routes with journey times and prices, your destinations and tours, the booking steps, trust details, a gallery, testimonials and questions. Only the vehicle’s name is required; a cell left empty prints nothing and a section with nothing in it is not printed at all. Publishing the page is a separate, explicit button, and it is a normal page, so you add it to your menu yourself.
-
How do people ask for a quote on the car hire page?
-
Through the form plugin you already use. Paste its shortcode — Contact Form 7, WPForms, Forminator, whichever it is — into the Request form group on Tours Car hire, and the form is printed in its own section, styled to match the page. Tripvance does not add a second enquiry system for cars: your form plugin already holds the fields, the address the mail goes to, the spam protection and the export, and duplicating that would only give you two places to check. Leave the shortcode empty and the section is not printed at all. The section answers to
#wptm-cars-request, so a hero or call-to-action button can scroll straight to it. -
Does it create pages or content when I activate it?
-
No. Activation only registers the post types and prepares the database. A notice then offers a starter kit, and nothing is created until you press the button. The starter kit’s sample destinations are Moroccan examples; rename or delete any of them.
-
How do I get review stars in Google search results?
-
Tripvance cannot make stars appear; Google decides that. What it does is make a tour eligible: turn on reviews under Tripvance Settings and let travellers leave rated reviews, and keep «Search result product data» switched on. Once the tour has approved rated reviews, their average and count — the same figures printed on the page — are added to the tour’s Product data. With Rank Math active they go into the Product Rank Math already builds for the tour, or into one Product added to Rank Math’s graph if it has none: Tripvance does not add a second Product when Rank Math already provides one for the current Tour or Activity. Ratings can be left out separately with «Include the average rating from approved reviews»; a site that had switched the earlier rating option off keeps it off. Ratings from other websites are never included, and activity pages, which do not display reviews, carry no rating.
-
Is there an activities page?
-
Optionally. Activities are pages of their own from the start; the listing at
/activities/and a page per activity type are switched on under Tripvance Settings (activity archive). With it on, the plugin draws both — title, description, a row of type links, the activity cards with their prices, pagination — and a theme can replace either witharchive-wptm_activity.phportaxonomy-wptm_activity_type.php. The[wptm_activities]shortcode and the Activities block put the same cards on any page. -
My day trip shows DAY 01, DAY 02… but it is one day
-
On Automatic this should not happen: a tour is drawn day by day only when it says it lasts more than one day — more than one day, at least one night, a multi-day duration preset, or an overnight written on one of its days. Check those four first, because one of them is what is claiming the days. Otherwise set Itinerary format to «Single day / Timeline» on that tour and the choice is final. Fill in the Time field at the top of each stop’s card if you have one and it leads the stop on the page; a stop with no time still reads perfectly by its title.
-
I set Itinerary format by hand. Will the plugin overrule me?
-
No. Automatic only decides for tours that have not chosen, and a tour that has chosen keeps that choice whatever its duration says.
-
The stylesheets are minified. How do I read the source?
-
The readable files sit beside the minified ones (
assets/css/tour.cssnext totour.min.css). DefineSCRIPT_DEBUGas true in wp-config.php and the readable files are served instead, as WordPress does for its own. The minified copies are built with esbuild 0.25.9. To rebuild a file, runnpx --yes esbuild@0.25.9 assets/css/tour.css --minify --outfile=assets/css/tour.min.css(use the corresponding paths for other CSS or JavaScript files); until then the edited file is served as it is, because a minified copy older than its source is never used. -
Does this take payments?
-
No. It records booking requests and the agency confirms them. No payment gateway is included and none is required.
-
Can I send a quote, an invoice or a trip programme as a PDF?
-
Yes. Open a booking, set its price under Price & services if needed, and use the Documents panel: Preview gives a draft without a number, Issue gives the numbered document and keeps an unchangeable copy. PDFs are produced on your own server. Tripvance prints the details you give it; check that your invoices carry what the rules where you trade require.
-
Is Advanced Custom Fields required?
-
No. The plugin has its own fields and works without it. If ACF is installed the same fields are shown through ACF instead. The free version is enough; no premium field type is used.
-
Will it conflict with my SEO plugin?
-
It should not. The plugin outputs no canonical, meta description or Open Graph markup and no site-wide schema, leaving those to Rank Math, Yoast or whichever you use. Its only structured data is one Product on eligible Tour and Activity pages; with Rank Math it is merged into Rank Math’s own graph, and with Rank Math the page builder no longer writes Rank Math’s title, description or focus keyword. If another SEO plugin already publishes a Product for your tours, switch off «Search result product data» or use the
wptm_product_schema_printfilter. -
Does it work with Polylang?
-
Yes, with the free version. Tours, activities, taxonomy terms and generated pages are assigned a language and linked to their translations, and each generated page is written in its own language. The homepage and the car hire page are created in every language at once and linked, so the language switcher and the hreflang tags are right from the start. The homepage’s own wording gets a language tab per language in Tripvance > Site pages > Homepage: the same form, the source text above every box, and a box left empty falls back to the source language rather than leaving a hole. Booking mails, vouchers and reminders answer in the language the traveller booked in. Your other wording is still exposed in Languages > String translations. A language switcher can be switched on in Settings and printed in the theme’s menus or through
[wptm_language_switcher]; each language links to the real translation of the current page and never to a guessed address. Without Polylang nothing changes. -
How do I change the addresses (URLs) of tours, activities and transfers?
-
In Tripvance > Settings > Addresses & SEO. Two structures are offered. Shared slugs use one base for every language (/tours/, /fr/tours/, /es/tours/; the language folders are Polylang’s). Translated slugs give each language its own base (/tours/, /fr/circuits/, /es/tours/; activities: activities, activites, actividades; transfers: transfers, transferts, traslados), with Polylang Free. Choosing Translated slugs fills these words in; they are suggestions you can change, and any other language starts from the English word rather than an invented one. Translating a base translates the address only: a French address shows the French translation of a tour where one exists.
A new site with Polylang already active is offered translated slugs in the Setup wizard. An existing site keeps exactly the addresses it has, through the update and afterwards, including when Polylang or a new language is added later, until an administrator changes them here.
The screen shows the addresses each word produces as you type. Save changes checks every word first and saves nothing if one is refused (an empty or reserved word, a language code, or two Tripvance routes at one address); the error is shown beside the field. Going back to an earlier word is always possible: it simply becomes the live address again. After a save the screen lists every route that moved and checks it against the rebuilt rules. Back up your site before changing published addresses.
Every previous base keeps answering with one permanent (301) redirect to the same tour, activity, transfer, list or term in the same language, so links and indexed pages keep working; several successive changes still take one hop, and a word that becomes active again stops redirecting. Unknown addresses keep answering 404; nothing is sent to the homepage or to another language. No post slug, title, content, ID, language, booking or SEO field is changed, and the plugin builds canonical, hreflang and sitemap addresses through WordPress’s own functions, so Rank Math, Yoast and Polylang publish the new ones. Search rankings can fluctuate while search engines process the change; check your sitemap and Google Search Console.
Restore Previous URL Configuration puts the previous bases back, with the same preview and redirects; it cannot restore content, rankings or links on other sites. If Polylang is switched off, the site keeps its default language’s addresses and returns to the per-language ones when it is switched on again.
Supported: language folders (/fr/, with or without the default language’s folder), WordPress in a subdirectory, structures with or without a trailing slash. Not supported for changes (the current addresses are kept and the screen says why): plain permalinks, Polylang languages by domain, subdomain or content, and bases set by code through the wptm_rewrite_slugs or wptm_language_slugs filters. Where Polylang Pro is active, its own Translate slugs module owns translated bases and Tripvance offers shared slugs only. Multisite works per site but has not been tested.
-
Can I take booking requests for something that is not a tour?
-
Yes. Tripvance Bookings Booking forms makes a booking request form with no tour page behind it — an airport pick-up, a private dinner, a day with a driver. Give it a name, optionally a price, the largest party and the notice you need, and place it on any page with
[tripvance_booking_form id="123"]: a button that opens the form in a window. Adddisplay="inline"to show the form in the page instead. The button’s words, icon, style (solid, outline, soft), shape (rounded, pill, square), size, width, alignment and colour are set on the form with a live preview, and one placement can change any of them in the shortcode (icon="calendar" style="outline"…). When a request is sent the traveller sees a booking slip print out of a small receipt printer: the reference, what was booked, the date, the party, the estimate and what happens next, with buttons to continue on WhatsApp, download the confirmation or print the slip. -
Can I change the booking reference (WPT-2026-001)?
-
Yes, in Settings Booking reference: your own letters and hyphens with {YYYY}, {YY}, {MM}, {DD} and {NUM}, and how many digits the number has — MTL-{YY}{MM}-{NUM} gives MTL-2610-0001. An example updates as you type. New requests use it; references already given keep theirs. The numbering starts again each year only when the year is part of the reference. Requests arrive in Bookings under the name you gave the form, with the same e-mails, statuses and documents as a tour booking.
-
Can two people book the last seat at once?
-
If seat-capacity enforcement is enabled, no. Tripvance obtains a departure lock and performs the capacity test as part of the reservation write, so only one request can take the final seat. Capacity enforcement is off by default because many agencies use the form as an enquiry system.
Reviews
Contributors & Developers
“Tripvance” is open source software. The following people have contributed to this plugin.
Contributors
“Tripvance” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “Tripvance” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
2.10.1
- New: Settings Cards per row — 3 (as before) or 4. Applies to the homepage, the tour and activity listings, destination hubs, landing pages, the car-hire and transfer homepage grids and the shortcodes’ default. Four only where the list is wide enough: a quarter of the row, never under 200px, so a narrow column shows three or two; cards in a row of four use slightly smaller type and padding.
- New: Settings Footer link columns (Luxury Editorial). Add, remove, reorder and rename columns and their links, and choose the footer row each stands in. A page of the site can be linked as a path (/about-us). «Restore the default columns» puts the defaults back.
- Changed: the Luxury footer’s email, phone and WhatsApp now sit together in one Contact column, followed by Support (About us, Contact, FAQs) and Legal (Legal Notice, Privacy Policy, Cookie Policy). The top row gains Booking Information (Booking Terms and Conditions, Cancellation and Refund Policy), which takes the place of the footer menu; the menu shows again when no top-row column is set. Default wording is translated (French, Spanish, Arabic); your own wording prints as typed.
- Changed: the Destinations, Departure points, Tour types and Trip lengths pages are redesigned. Destinations and departure points: one card per place — photograph, number of tours, name, description — in three or four columns at the theme’s wide width, two on a tablet, one on a phone. Tour types and trip lengths: a section per type with its description and «View all», then its tours as the site’s own tour cards (a swipeable strip on phones). With Luxury Editorial the pages take its square frames and quieter type.
- Fixed: the Destinations page showed five places and a «View all destinations» card that led to a 404 when the destination index is off (the default). It now lists every destination unless that index is on.
- New: with Luxury Editorial on, Tripvance makes the Destinations, Tour types and Departure points pages if the site does not have them, and updates the ones it already has (Trip lengths too): each opens with the page title over the photograph of the place with the most tours, and ends with an invitation to plan a journey, on the full-width template. Runs once, on the first admin visit; only the [wptm_terms] shortcode on the page is changed, any text around it stays, and a page you delete afterwards is not made again.
- Changed: the cookie banner takes less room in all three layouts — smaller padding and buttons, Reject and Accept side by side at one size with Manage preferences beside or under them, and «Continue without accepting» on the title’s line instead of a strip of its own. The default text is shorter in English, French, Spanish and Arabic; text you typed in the settings is kept.
- Changed: Luxury homepage, Our purpose (framed portrait): the photograph now stands on its own, without the outline behind it, the white border or the shadow. Everything else in the section is unchanged.
- Fixed: the destination and tour type index pages (/tours/destination/, /tours/type/) could show the code of an unrelated article — its styles printed as text — under the heading. They now open with one short line in the page language, count «8 destinations» rather than «8 sections», and show each place’s photograph: the image set on the destination, or else the photograph of its newest tour. Sites are fixed by the update itself.
- Fixed: on multilingual sites (Polylang) the destination and tour type index pages now open in every language at their own address (/fr/tours/destination/ and so on) with the heading, counts and line in that language; before, only the default language worked, and one language could show the homepage instead. The language switcher and search engines are pointed at the right page in each language.
- Fixed: the Destinations, Departure points, Tour types and Trip lengths pages made in French, Spanish or Arabic took English titles and introductions on sites without a language pack. They are now made in their language, and pages made before keep any wording you changed while the rest is put into their language once, after the update.
- Fixed: on archive and listing pages, a few places read the page as the post with the same number — a page title, a homepage check, SEO fields. They now only ever read a real post.
- Improved for search engines: the index pages carry a description and a canonical address and are listed in the site’s sitemap. With no SEO plugin, tours, activities and transfers get a meta description from their summary, destination and type pages from their description, and the tour archive and its destination and type pages a canonical address. With Rank Math or Yoast, their settings stay in charge.
- Changed: Bookings list — softer table with rounded corners, the guest’s initials beside the name, and Today / Tomorrow / In 5 days under travel dates coming up in the next two weeks; on phones the status views scroll in one line and the filters pair up. The booking screen’s section tabs are one bar and the header is shorter.
- New: with Luxury Editorial on, the Trip Builder (Plan your journey) takes the Luxury look: a deep ink opening with the title in serif capitals and the three promises as one tagline, a square paper form edged in terracotta, warm stone greys and sand, square fields and choices, small-capital labels and buttons. Sites already on Luxury get it with this update; nothing to switch on. The accent colour chosen in Tripvance settings still replaces terracotta.
- New: on Luxury Editorial the Trip Builder is the Morocco Trip Planner, written for search: the name as its heading (h1 on the full-width page) and in a new page’s title and address, an introduction and a three-step «How the trip planner works» section under the form, and a title tag and meta description used wherever the page has none of its own in Rank Math, Yoast or the page settings. Its opening band is one flat colour, the Luxury footer’s own, reaching both edges of the window and meeting the site’s menu with no gap; the planner page moves to the full-width template once if it was on the theme’s default one. A page still titled «Plan Your Trip» is renamed once; a published page keeps its address. Your own wording in the Trip Builder settings is always kept.
- Changed: the Morocco Trip Planner’s opening shortens to its title once the traveller moves past the first question, and the section under the form steps aside, so every next step starts on the first screen; chosen answers take a terracotta frame on sand, picture choices darken gently, the summary reads like a travel notebook, and on phones the Previous/Continue bar stays at the foot of the screen.
- Changed: the Luxury footer’s hairlines run edge to edge. The «Privacy» link at the end of the copyright line is gone (Privacy Policy is in the Legal column); in its place, an optional small image — Settings Footer badge — shown at 32px high (26px on phones), original file, so an animated GIF stays animated.
- Changed: in the Luxury footer the social addresses are no longer a column of links; they are a row of round line icons (Instagram, Facebook, YouTube, TikTok, X) under the paragraph about the agency.
- New: Settings Brand mark (Luxury): a small emblem (SVG, PNG or GIF, original file) used as the marker of the steps under the Morocco Trip Planner, about 26px high; without one, a small diamond in the accent colour. The line above that section is gone.
- Removed: the six Luxury page starters (Inspirational journeys, One collection, Destinations, Our purpose, About us, Own in Morocco) from Tours Pages. Pages already made from them are not touched, and the luxury sections stay available in the page builder.
2.10.0
- New: Tours Import and export backs up and restores activities, transfers and the vehicle profiles transfers are priced against, in the same file as tours. Vehicles are matched by their reference code, then their slug, so a transfer keeps its prices on another site.
- Fixed: a backup was refused on hosts whose file-type check reports JSON as plain text. The file’s content is still checked before anything is read.
- Fixed: restoring a backup on another site no longer copies gallery IDs that point at the wrong photographs, and text containing a backslash keeps it.
- Fixed: the REST import endpoint failed because the export module it relies on was not loaded.
- Changed: the WooCommerce importer only appears when WooCommerce is active; restore has its own choice of what to do with items already on the site; the screen is laid out in three panels.
2.9.9
- New: Booking forms (Tripvance Bookings Booking forms). A booking request form that needs no tour or activity: give it a name, optionally a price, the largest party and the notice needed, and place it with
[tripvance_booking_form id="…"]— a button that opens the form in a window, or the form in the page withdisplay="inline". Requests go through the same checks, e-mails and documents as a tour’s and show in Bookings under the form’s name; the visitor stays on the page the form was on. - New: booking forms have a button design — icon and its side, style, shape, size, width, alignment and colour, previewed live on the form’s screen and overridable per shortcode — and answer a request with a printed booking slip (sending printing received) that works on phones and desktops, right-to-left pages, night mode and reduced motion.
- New: Settings Booking reference — choose the shape of booking references (letters, year, month, day, number, digits) instead of WPT-2026-001; the tour code on the booking ticket takes the same letters. Existing references are unchanged.
- Changed: the window showing the booking slip has no title bar, so the slip and its buttons need less scrolling; both windows close with the same plain cross, and the slip’s buttons sit in two tidy rows (WhatsApp, then Download and Print).
- Performance: a booking form adds only its own small stylesheet to the head of the page it is on; the form’s styles and scripts load deferred, and pages without a booking form load nothing new.
- New: «Hide the Tripvance footer on this page» — a box beside the editor and in the page builder’s layout panel, shown while the Luxury footer is on. The theme’s own footer is not affected.
- Changed: the Luxury sample content no longer creates the About Us, Our Purpose and Inspirational Journeys pages. On update, those pages are moved to the Trash if they are still unpublished drafts; a demo page you published is kept.
2.9.8
- New: a third tour card style, Marketplace (Settings Essentials Tour card style), for browsing tours the way travel marketplaces present them: a square photograph with its own rounded corner and, under it on the page’s colour, the place in a small grey tag, a large title, the rating (only when the tour has approved reviews), the duration and the price as one line («From €240 per person»). The whole card stays one link to the tour. On phones the cards become a row you swipe. Boxed stays the default and Open is unchanged; existing sites look exactly as before until Marketplace is chosen.
- Fixed: the homepage Travel Guides section cut the sides (or top and bottom) off article pictures. Frames were 3:2, 4:3, 16:10 or 2:1 depending on the layout, and in Editorial and Panorama rows the frame also stretched to the height of the text beside it. Every layout now uses a 16:9 frame that keeps its shape, so a 1200×675 featured image shows in full; pictures in other shapes still fill the frame neatly.
2.9.7
- Fixed: on themes whose header changes as the page scrolls, the tour’s section bar either disappeared behind the menu (a header that becomes fixed only after scrolling was measured as nothing) or stuck with a gap under it through which the page showed (a header that drops its logo row was measured at its taller height). The header is now followed while the page scrolls and for a moment after, so the bar sits right under it at every point — including headers that slide away on the way down and back on the way up.
- Fixed: the booking column on tour pages and the list-view column on tour listings follow the same measurement, so they too stay under the menu.
- Fixed: a theme wrapper with overflow hidden could stop the section bar from sticking on one-column (phone) views; it is now repaired for the bar as it already was for the two-column booking panel.
2.9.6
- Fixed: in Rank Math Sitemap Settings the Activities and Transfers tabs had no name. Rank Math reads the names of the public post types once, early in WordPress’s start-up, and keeps them; the two types were registered after that moment. They are now registered right after Tours, so Rank Math (and any SEO plugin that reads post types early) sees their names. Addresses, sitemaps and settings are unchanged.
Earlier versions
The full history, version by version, is in changelog.txt in the plugin folder.