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.
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.
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).
Eleven tour page designs, chosen per tour or site wide, on one shared foundation: 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 schema on tour pages. Those belong to an SEO plugin, and two sources for one signal is worse than one. When the optional Rank Math rating integration is enabled, Tripvance can enrich Rank Math’s existing tour schema with genuine approved review data.
The homepage is the one exception, and it can be switched off in Tripvance > Site pages > Homepage. An SEO plugin can only describe what it can read, and the homepage is assembled by Tripvance after that plugin has already decided what the page is: the questions and answers, the licence number, the featured tours and the site search are all on the page and none of them reach the graph. So Tripvance describes them itself, in the language each visitor is reading — inLanguage, this language’s tour links, this language’s site root — and describes nothing the page does not show.
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. 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. 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 site’s consent integration allows it; 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. The WordPress Consent API is supported when a consent manager configures opt-in mode. 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. Tripvance does not provide a cookie banner.
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.
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
-
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?
-
Turn on reviews under Tripvance Settings and let travellers leave rated reviews. Tripvance does not print a separate schema graph; with Rank Math active it can add the average rating and latest approved reviews to the schema Rank Math already builds for the tour. To make a tour eligible for product review rich results, set Rank Math Titles & Meta Post Types Tours Schema Type to Product. Google ultimately decides whether a rich result is shown, and nothing is added until real approved reviews exist.
-
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.
-
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 schema on tour pages, leaving those to Rank Math, Yoast or whichever you use. The homepage graph is the single exception; if your SEO plugin already publishes the same thing, untick it in Tripvance > Site pages > Homepage.
-
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. -
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
There are no reviews for this plugin.
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
1.42.1
Why Activity pages could render unstyled, and the Activity page on a phone. Nothing on a tour page changes, no meta key moves, and every activity, price, gallery and booking is where it was.
- The Activity stylesheet reaches the page. It was enqueued with two other handles named as dependencies, and WordPress prints nothing at all — with no notice and nothing in the log — when a named dependency is not registered. One handle removed by another plugin and the page shipped its full markup with no stylesheet. Both handles are now registered at the point of use and a handle that still cannot be found is dropped rather than allowed to take the page’s stylesheet down with it.
- The page no longer depends on a second file for its appearance. Every panel, card, cell rule and tinted block on it is drawn with custom properties declared in tokens.css, and a custom property with no value invalidates the whole declaration that reads it — so losing that one file left At a glance with no box, Highlights with no card and the panels with square corners, which is the page looking unstyled. activity.css now carries its own floor for those values, at zero specificity, so tokens.css, the site accent and the unified brand all still win when they are there.
- Assets are versioned by the file actually served. The version string stamped the readable source while the browser was given the .min built from it, so rebuilding the .min without touching its source changed the bytes at an address that had not changed and every cache kept the old copy. A .min that is empty or a tenth the size of its source — an interrupted build — is no longer served at all.
- The Activity hero starts below the theme’s header. A fixed header is painted over the top of the banner, and on a phone the breadcrumbs and part of the line above the title were underneath it. The overlap is measured from whatever is actually fixed or sticky at the top of the window, including the admin bar, so no theme’s height is written into the stylesheet and a theme whose header scrolls away is unchanged.
- The Activity page on a phone. One step tighter on the spacing scale the whole page is set with, reading type at phone proportions, At a glance as compact cells with no empty one at the end of a short row, the gallery two across instead of twelve full-width frames, the meeting point stacked so an address is not four lines of two words, and the running order’s clock column at the width of its badge rather than a tour’s.
- What to bring, Important information and the questions are headed like the rest of the page. They are drawn by the tour page’s section templates, whose title sets no colour, so they inherited the body grey and stood beside navy headings at a different size over a shorter accent rule.
- The mobile price bar cannot clip or cover. Its height is derived from its own parts and the safe area, and the page reserves exactly that much; the price never wraps or is cut, and a long button label ends in an ellipsis instead of past the card’s edge. The button’s label also stopped being given the icon’s line-height — an old first-child selector that matched the label on the one button with no icon.
1.42.0
The Activity page and a way out of a tour that should have been an activity. Nothing on a tour page changes, no meta key moves, and every tour, activity, price, itinerary and booking is where it was.
- The Activity hero is full width. The band reaches both edges of the screen while its words stay in the same column as the reading below them, and it sits against the site header instead of under a band of white. The photograph keeps its own proportions rather than being stretched to the height of the text beside it.
- The booking rail holds the booking card and nothing else. Meeting point, cancellation, important information and the questions were being drawn in a three-hundred-and-seventy pixel column beside the form; they are sections of the reading column now, at its full width, each drawn once. The card follows the reader on a wide screen and stacks normally on a phone.
- One spacing scale for the page. Six different margins between sections became three custom properties, and a section heading now sits closer to what it introduces than to the section above it.
- At a glance carries every fact, including when the activity runs, which had a card of its own. The strip wraps into counted columns instead of forcing every fact onto one row, so labels are read at their proper size rather than shrunk to fit.
- The gallery opens. “View photos” and every thumbnail open a viewer with the full-size picture, a counter, previous and next, Escape, arrow keys and a backdrop that closes it; the page behind does not scroll and focus returns where it was. Without JavaScript each frame is still a link to its own picture.
- Tour to Activity conversion. An unpublished tour can be copied into a new draft activity from the tours list or the Publish box: title, content, excerpt, featured image, gallery, destination and place terms, and every commercial and experience field that both post types share. The tour is never modified and no media is duplicated.
- The itinerary is converted rather than copied. A tour keeps its stops as days and an activity keeps them as moments of one occasion, so a copied row arrived as an empty schedule. Stops are now read through the itinerary layer’s own reader — structured, legacy text, or both — and written as schedule rows in order, with their times, titles, descriptions, locations and photographs. Anything with no field of its own is carried into the description rather than dropped, and whatever cannot be mapped is named in a notice on the new activity.
- Description and answer paragraphs are justified and set at a reading measure, ragged on a narrow column, inheriting the theme’s own type.
Earlier releases
In brief below. The full notes for every release, including these, are in
changelog.txt, which ships with the plugin.
- 1.41.0 — The tour editor answers as you type: a live status card that says the booking mode in words, completion counted on the six things a tour needs, and field search that reaches the itinerary.
- 1.40.2 — A styling pass over the itinerary: the thread runs to the last moment of the last day, and the descriptions are set at a reading size.
- 1.40.1 — A migration fix. Activation recorded the itinerary migration as finished before it had started; stranded sites are picked up automatically.
- 1.40.0 — The itinerary is written on cards. Existing tours move across automatically, and the old wptm_itinerary field is kept as the backup.
- 1.39.0 — An editor release: days and stops appear as editable cards straight away, and Activities use the same editor as Tours.
- 1.38.0 — A stability release: less loaded on a front-end request, a correct rate limiter under load, a System Status screen and a test suite.
- 1.37.0 — A tour is drawn day by day only when it says it lasts more than one day, so day trips are no longer announced as DAY 01, DAY 02.
- 1.36.0 — Day trips stop being announced as a run of days: a one-day itinerary reads as a timeline of times and stops on every layout.
- 1.35.2 — A stability release. Tours written by any earlier version open, save and render exactly as they did.