Take this first if Activity pages look unstyled: the stylesheet could be silently not printed, and its panels lost their appearance when a second file was missing. Both fixed. The hero no longer starts under a fixed header, and the page is retuned for phones. No Tour or data changes.<\/p>","1.42.0":"
The Activity page, rebuilt around its reading column: a full-width hero, one glance strip, and the meeting point, cancellation and questions moved out of the booking rail. The gallery opens in a viewer. Tours can be converted into draft Activities without retyping. No Tour output changes.<\/p>","1.41.0":"
A tour editor pass. The status card printed the raw booking mode and answered from the last save; both are fixed, and it now follows the form as you type. Completion counts the six things a tour genuinely needs. No stored value, meta key or front-end output changes.<\/p>","1.40.2":"
A styling pass over the itinerary. The thread now runs to the last moment of the last day instead of stopping short, and descriptions are set at a reading size: justified on a wide screen, ragged on a phone. No markup, colour, stored value or behaviour changes.<\/p>","1.40.1":"
A migration fix, and the reason to take this first if you are on 1.40.0. Activation recorded the itinerary migration as finished before it had started, so some sites kept their itineraries in the old text field. Those sites are picked up and finished automatically.<\/p>","1.40.0":"
The itinerary is written on cards: add a day, type a title and a description. Existing tours move across automatically on the first admin page load, and the old wptm_itinerary field is kept untouched as the backup. Nothing on the front of the site changes.<\/p>","1.39.0":"
An editor release. A day or a stop is added as an editable card straight away, the completeness meter answers as you type, and Activities now use the same editor as Tours. Nothing on the front of the site changes and no meta key moves.<\/p>","1.38.0":"
A stability release. No feature or stored value changes. Underneath: less loaded on a front-end request, a rate limiter that counts correctly under concurrent submissions, a new System Status screen, and a test suite behind the booking engine.<\/p>","1.37.0":"
Finishes what 1.36.0 started. 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. The itinerary is now one thread down the page. No stored value changes.<\/p>","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, including Luxury. Nothing is converted or deleted, and an Itinerary format setting covers the tours the rule gets wrong.<\/p>","1.35.2":"
A stability release. Nothing about how tours are stored has changed, and tours written by any earlier version open, save and render exactly as they did. Recommended before updating anything else.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3688981,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3688981,"resolution":"256x256","location":"assets","locale":"","width":1254,"height":1254}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3688981,"resolution":"1544x500","location":"assets","locale":"","width":2203,"height":714},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3689012,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"tripvance\/tours":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"tripvance\/tours","title":"Tours","category":"tripvance","icon":"location-alt","description":"Tour cards from your catalogue, as a grid or as the Moroccan Editorial Carousel, filtered by destination, type, category, duration or departure.","keywords":["tours","travel","booking"],"textdomain":"tripvance","editorScript":"wptm-sections-block","style":"wptm-card","supports":{"html":false,"align":["wide","full"]},"attributes":{"destination":{"type":"string","default":""},"type":{"type":"string","default":""},"category":{"type":"string","default":""},"duration":{"type":"string","default":""},"departure":{"type":"string","default":""},"ids":{"type":"string","default":""},"count":{"type":"number","default":6},"order":{"type":"string","default":"featured"},"columns":{"type":"number","default":3},"excerpt":{"type":"boolean","default":true},"heading":{"type":"string","default":"h3"},"selectionMode":{"type":"string","default":""},"layout":{"type":"string","default":"cards"},"eyebrow":{"type":"string","default":""},"title":{"type":"string","default":""},"highlight":{"type":"string","default":""},"subtitle":{"type":"string","default":""},"cta_label":{"type":"string","default":""},"cta_url":{"type":"string","default":""}},"editorStyle":"wptm-section-editor"}},"tagged_versions":["1.12.0","1.35.2","1.42.1","1.8.11","1.8.13"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3688981,"resolution":"1","location":"assets","locale":"","width":1440,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3688981,"resolution":"2","location":"assets","locale":"","width":1440,"height":890},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3688981,"resolution":"3","location":"assets","locale":"","width":1440,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3688981,"resolution":"4","location":"assets","locale":"","width":1440,"height":580},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3688981,"resolution":"5","location":"assets","locale":"","width":1440,"height":835},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3688981,"resolution":"6","location":"assets","locale":"","width":1440,"height":900},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3688981,"resolution":"7","location":"assets","locale":"","width":1440,"height":900}},"screenshots":{"1":"A tour page: gallery, rating, section navigation and the booking ticket.","2":"The booking ticket, with the two-step request form.","3":"The listing page with filters, sorting and tour cards.","4":"The route at a glance and the itinerary.","5":"The bookings dashboard in the admin."}},"plugin_section":[],"plugin_tags":[14615,269,125417,17227,249],"plugin_category":[39,40],"plugin_contributors":[278217],"plugin_business_model":[],"class_list":["post-362349","plugin","type-plugin","status-publish","hentry","plugin_tags-activities","plugin_tags-booking","plugin_tags-itinerary","plugin_tags-tours","plugin_tags-travel","plugin_category-business","plugin_category-calendar-and-events","plugin_contributors-abourri","plugin_committers-abourri"],"banners":{"banner":"https:\/\/ps.w.org\/tripvance\/assets\/banner-772x250.png?rev=3689012","banner_2x":"https:\/\/ps.w.org\/tripvance\/assets\/banner-1544x500.png?rev=3688981","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/tripvance\/assets\/icon-128x128.png?rev=3688981","icon_2x":"https:\/\/ps.w.org\/tripvance\/assets\/icon-256x256.png?rev=3688981","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/tripvance\/assets\/screenshot-1.png?rev=3688981","caption":"A tour page: gallery, rating, section navigation and the booking ticket."},{"src":"https:\/\/ps.w.org\/tripvance\/assets\/screenshot-2.png?rev=3688981","caption":"The booking ticket, with the two-step request form."},{"src":"https:\/\/ps.w.org\/tripvance\/assets\/screenshot-3.png?rev=3688981","caption":"The listing page with filters, sorting and tour cards."},{"src":"https:\/\/ps.w.org\/tripvance\/assets\/screenshot-4.png?rev=3688981","caption":"The route at a glance and the itinerary."},{"src":"https:\/\/ps.w.org\/tripvance\/assets\/screenshot-5.png?rev=3688981","caption":"The bookings dashboard in the admin."},{"src":"https:\/\/ps.w.org\/tripvance\/assets\/screenshot-6.png?rev=3688981","caption":""},{"src":"https:\/\/ps.w.org\/tripvance\/assets\/screenshot-7.png?rev=3688981","caption":""}],"raw_content":"\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.<\/p>\n\n
Tours<\/strong><\/p>\n\n 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 \u2014 press Add a day, give it a title and a description \u2014 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.<\/p>\n\n Tours are filed under destinations, tour types, departure points, trip lengths and categories, each with its own archive page and filters.<\/p>\n\n Two kinds of travel business<\/strong><\/p>\n\n Tripvance ships two presentations of the same content, chosen under Settings \u2192 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 \u2014 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.<\/p>\n\n Booking requests<\/strong><\/p>\n\n 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.<\/p>\n\n Requests are managed from a booking screen with a status workflow, internal notes and an operations dashboard.<\/p>\n\n Presentation<\/strong><\/p>\n\n 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).<\/p>\n\n 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.<\/p>\n\n Listing pages with filters, sorting and cards; a Tours block and a Multilingual<\/strong><\/p>\n\n 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.<\/p>\n\n 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 \u2014 the homepage, the car-hire page, the default inclusions \u2014 appears under Languages > String translations so it can differ per language.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n An optional language switcher goes into the theme's own menus \u2014 desktop header, mobile menu, footer, or a shortcode wherever you like \u2014 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.<\/p>\n\n Without Polylang the plugin runs unchanged.<\/p>\n\n Search engines<\/strong><\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n It also emits clean semantic markup, keeps taxonomy archives crawlable, marks empty ones as noindex, and keeps them out of the sitemap.<\/p>\n\n Import<\/strong><\/p>\n\n Existing WooCommerce products can be imported as tours, with a dry run first that reports exactly what would happen and creates nothing.<\/p>\n\n 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 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.<\/p>\n\n Optional first-party campaign attribution uses the 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.<\/p>\n\n 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.<\/p>\n\n Yes. After activation a dismissible welcome offers a step-by-step guide (Tripvance \u2192 Settings \u2192 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 \u2014 sample tours, activities and destinations, every item marked as demo \u2014 with a one-click removal that never touches your own content. The guide can be restarted from Tripvance \u2192 Settings.<\/p><\/dd>\n Yes. Tripvance \u2192 Site pages \u2192 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.<\/p><\/dd>\n Yes. Tours \u2192 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.<\/p><\/dd>\n Through the form plugin you already use. Paste its shortcode \u2014 Contact Form 7, WPForms, Forminator, whichever it is \u2014 into the Request form group on Tours \u2192 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 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.<\/p><\/dd>\n Turn on reviews under Tripvance \u2192 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 \u2192 Titles & Meta \u2192 Post Types \u2192 Tours \u2192 Schema Type to Product. Google ultimately decides whether a rich result is shown, and nothing is added until real approved reviews exist.<\/p><\/dd>\n Optionally. Activities are pages of their own from the start; the listing at On Automatic this should not happen: a tour is drawn day by day only when it says it lasts more than one day \u2014 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.<\/p><\/dd>\n No. Automatic only decides for tours that have not chosen, and a tour that has chosen keeps that choice whatever its duration says.<\/p><\/dd>\n The readable files sit beside the minified ones ( No. It records booking requests and the agency confirms them. No payment gateway is included and none is required.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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 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.<\/p><\/dd>\n\n<\/dl>\n\n\n 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.<\/p>\n\n 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.<\/p>\n\n In brief below. The full notes for every release, including these, are in\nchangelog.txt, which ships with the plugin.<\/p>\n\n[wptm_tours]<\/code> shortcode for a grid of tours anywhere, and [wptm_activities]<\/code> for a grid of activities \u2014 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 \u2014 the fleet, the services, the routes you cover and the prices you quote.<\/p>\n\nPrivacy<\/h3>\n\n
wp_mail()<\/code> and the mail provider configured by the site owner. Tripvance sends no telemetry to its developer and loads no remote fonts.<\/p>\n\nwptm_attr<\/code> 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<\/code> filter. Do not return true globally as a substitute for visitor consent. Tripvance does not provide a cookie banner.<\/p>\n\nExternal services<\/h3>\n\n
\n
wa.me<\/code> after 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 .<\/li>\n\n
\/wp-content\/plugins\/<\/code>, or install it through Plugins \u2192 Add New.<\/li>\n\n
Is there a setup guide?<\/h3><\/dt>\n
Is there a homepage?<\/h3><\/dt>\n
Is there a car hire page?<\/h3><\/dt>\n
How do people ask for a quote on the car hire page?<\/h3><\/dt>\n
#wptm-cars-request<\/code>, so a hero or call-to-action button can scroll straight to it.<\/p><\/dd>\nDoes it create pages or content when I activate it?<\/h3><\/dt>\n
How do I get review stars in Google search results?<\/h3><\/dt>\n
Is there an activities page?<\/h3><\/dt>\n
\/activities\/<\/code> and a page per activity type are switched on under Tripvance \u2192 Settings (activity archive). With it on, the plugin draws both \u2014 title, description, a row of type links, the activity cards with their prices, pagination \u2014 and a theme can replace either with archive-wptm_activity.php<\/code> or taxonomy-wptm_activity_type.php<\/code>. The [wptm_activities]<\/code> shortcode and the Activities block put the same cards on any page.<\/p><\/dd>\nMy day trip shows DAY 01, DAY 02\u2026 but it is one day<\/h3><\/dt>\n
I set Itinerary format by hand. Will the plugin overrule me?<\/h3><\/dt>\n
The stylesheets are minified. How do I read the source?<\/h3><\/dt>\n
assets\/css\/tour.css<\/code> next to tour.min.css<\/code>). Define SCRIPT_DEBUG<\/code> as 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, run npx --yes esbuild@0.25.9 assets\/css\/tour.css --minify --outfile=assets\/css\/tour.min.css<\/code> (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.<\/p><\/dd>\nDoes this take payments?<\/h3><\/dt>\n
Is Advanced Custom Fields required?<\/h3><\/dt>\n
Will it conflict with my SEO plugin?<\/h3><\/dt>\n
Does it work with Polylang?<\/h3><\/dt>\n
[wptm_language_switcher]<\/code>; each language links to the real translation of the current page and never to a guessed address. Without Polylang nothing changes.<\/p><\/dd>\nCan two people book the last seat at once?<\/h3><\/dt>\n
1.42.1<\/h4>\n\n
\n
1.42.0<\/h4>\n\n
\n
Earlier releases<\/h4>\n\n
\n