Descrición
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, a day by day itinerary, what is included and what is not, a meeting point, and questions and answers. 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, a day by day (or step by step) itinerary, 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 .
Capturas
Blocks
Este plugin proporciona 1 bloque.
- Tours Tour cards from your catalogue, as a grid or as the Moroccan Editorial Carousel, filtered by destination, type, category, duration or departure.
Instalación
- 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.
Preguntas frecuentes
-
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. -
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.
Comentarios
Non hai recensións para este plugin.
Colaboradores e desenvolvedores
“Tripvance” é un software de código aberto. As seguintes persoas colaboraron con este plugin.
Colaboradores
Traduce “Tripvance” ao teu idioma.
Interesado no desenvolvemento?
Revisa o código, bota unha ollada aorepositorio SVN, ou subscríbete ao log de desenvolvemento por RSS.
Rexistro de cambios
1.35.2
- The last Plugin Check warning cleared: the panel flags are read and sanitised in one statement, with the nonce the caller already verified named alongside it.
- An area you click in the section navigation keeps its mark while the page travels to it, instead of the mark walking through the areas in between.
1.35.1
- Two findings from Plugin Check cleared: the panel flags are sanitised where they are read, and the duplicate action states why it reads the tour id before checking its nonce.
- The last of the WordPress blue inside the Tripvance parts of the tour editor is gone: the section navigation, the readiness list, the switches and the pickers all use the plugin’s own green.
- changelog.txt rewritten as a plain list of releases rather than development notes.
1.35.0
- A stability release before this update goes out: no new features, and nothing that changes how anything is stored.
- A saved value a dropdown no longer offers — a layout from a theme that has gone, a value an import wrote — is kept instead of being quietly erased on the next save.
- A numbered question whose text starts with a number, “2- 4 hours of driving: is that right?”, is read as a question again rather than swallowed into the answer above it. Itineraries are unchanged: a figure in a line still never opens a day.
- Numbers that count something can no longer be saved below zero.
- The rich text fields’ labels point at the field they name, so clicking one puts the cursor in it.
- Bigger tap targets in the editor: removing a row, removing a photograph, switching a table to text and every row of the readiness list.
- Duplicated styling from the last four releases removed, and every rule on the tour screen scoped to that screen.
1.34.0
- The tour screen is a tour editor now, not a stack of grey boxes: warm paper behind, white cards with room to breathe, a deep green for what is chosen and a terracotta for what still wants filling in.
- Overview became two cards — Tour identity (destination, type, hero image, duration, short description) and Trip essentials (party size, difficulty, languages, departure and end point) — and Content is now Experience.
- The itinerary and its day cards are one Journey Builder: the text, then a card per day with its route, distances, transport, overnight, meals and named experiences, each opening and closing on its own. No second box to scroll to, and an Add a day button that writes the next day for you.
- Pricing opens with what the tour costs, over the fields that decide it.
- Tour media moved out of the sidebar into the tour itself, with the main image named and the gallery given room. The sidebar is two cards now: the sections, and where the tour stands.
- Layouts are chosen from miniatures rather than a dropdown, the way the settings screen already offered them.
1.33.0
- The section navigation no longer sits over the fields. It is a card in the column beside them — a list of the tour’s areas, each with a tick, a mark or an empty ring — so nothing on this screen can cover a box you are typing into. The column follows you down the page when the whole of it fits on your screen, and scrolls with the page when it does not.
- A bar over the title carries the state of the tour — its status, how much of it is filled in, when it was last saved — and Preview, Duplicate, Bookings and Update.
- Every box on the tour screen is a card now: an icon, a title and a line saying what the box is for. The headers are still WordPress’s own, so they sort, collapse and fold exactly as they did.
- Tour status and Tour readiness are one card instead of two.
Earlier releases
- Every release from 1.0.0 onwards is listed in the changelog.txt file shipped inside the plugin.