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, 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.<\/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 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, 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.<\/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 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 Activities become products: an activity can carry its own price and take booking requests directly, through the same engine tours use.<\/p>\n\n Hardening release for pricing, scheduled departures and the operations workflow.<\/p>\n\n The operations release: a booking request now has a whole working life inside WordPress \u2014 quote, acceptance, payment tracking, confirmation, crew and vehicle assignment, the trip itself, completion and a review request.<\/p>\n\n No payment gateway is added, and none is planned. Money moves outside the website by bank transfer, a PayPal link, cash or whatever the agency has arranged; the plugin records what arrived. WhatsApp is a click-to-chat link and a copy button \u2014 no Business API, no automatic sending, no delivery tracking.<\/p>\n\n Money the customer agreed to<\/strong><\/p>\n\n Getting the trip out of the door<\/strong><\/p>\n\n Guest Pass 2.0<\/strong><\/p>\n\n Partners, customers and what is working<\/strong><\/p>\n\n Upgrading<\/strong><\/p>\n\n New: the Digital Guest Travel Pass.<\/p>\n\n For releases before 1.4.7, see changelog.txt in the plugin folder.<\/p>","raw_excerpt":"Tours, activities and travel experiences for WordPress: tour pages, itineraries and booking requests. No standalone schema graph; SEO-plugin friendly.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/362349","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=362349"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/abourri"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=362349"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=362349"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=362349"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=362349"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=362349"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=362349"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}[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>\nThe 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.8.11<\/h4>\n\n
\n
1.8.9<\/h4>\n\n
\n
[wptm_tours]<\/code>): the strip of gallery thumbnails is placed against its own card instead of against whatever the theme happened to have positioned; the card fills its slot as a flex child rather than through a chain of percentage heights; the photograph keeps its box on themes that force every image to its natural height; and a clearfix or decoration a theme hangs on the article, the list item or the link no longer adds height to the card.<\/li>\n1.8.8<\/h4>\n\n
\n
1.8.7<\/h4>\n\n
\n
1.8.6<\/h4>\n\n
\n
1.8.5<\/h4>\n\n
\n
1.8.4<\/h4>\n\n
\n
1.8.3<\/h4>\n\n
\n
1.8.2<\/h4>\n\n
\n
1.8.1<\/h4>\n\n
\n
1.8.0<\/h4>\n\n
\n
1.7.7<\/h4>\n\n
\n
1.7.6<\/h4>\n\n
\n
1.7.5<\/h4>\n\n
\n
1.7.4<\/h4>\n\n
\n
1.7.3<\/h4>\n\n
\n
1.7.2<\/h4>\n\n
\n
1.7.1<\/h4>\n\n
\n
1.7.0<\/h4>\n\n
\n
wptm_booking_post_types<\/code> \/ wptm_booking_product<\/code> filters; a request from an activity is validated, priced, held in the reservation ledger, mailed and listed with the tour bookings, and a minimum-party rule is enforced server-side through wptm_booking_validate<\/code>.<\/li>\n[wptm_hero]<\/code>, [wptm_trust]<\/code>, [wptm_cta]<\/code>, [wptm_faq]<\/code>, [wptm_contact]<\/code>, [wptm_reviews]<\/code>, [wptm_guides]<\/code>, [wptm_destinations]<\/code>, [wptm_tour_types]<\/code>, beside the existing [wptm_tours]<\/code> and [wptm_activities]<\/code>. Drawn on the plugin's own tokens, RTL-ready, with the site accent. Filters wptm_sections<\/code>, wptm_page_starters<\/code>, wptm_page_starter_content<\/code>; action wptm_page_created<\/code>.<\/li>\nwptm_admin_menu_groups<\/code>, wptm_admin_menu_untabbed<\/code>, wptm_compact_admin_menu<\/code>.<\/li>\nCard\\activity()<\/code> \u2014 the shared card, for activities \u2014 and a [wptm_activities]<\/code> shortcode (destination, place, type, ids, count, order, columns, bookable). The homepage activities section shows duration and price where set; the booking list filter offers bookable activities under the tours.<\/li>\n--wptm-gold-text<\/code> shade \u2014 the same hue, darkened until it passes, derived from the site accent where the browser can mix colours. One shared focus ring and a reduced-motion switch for every module, a fuller print stylesheet for the activity page, and content-visibility<\/code> on its gallery and tour cards so a long page paints its first screen sooner.<\/li>\n\/activities\/<\/code> and each activity type's page are drawn by the plugin \u2014 title, lead, count, a row of type links with the current one marked, the activity cards (h2 each, first row eager), pagination and an empty state \u2014 instead of the theme's blog listing. Theme overrides: archive-wptm_activity.php<\/code>, taxonomy-wptm_activity_type.php<\/code>, tripvance\/archive-activities.php<\/code>. Breadcrumbs on an activity now run Home \u2192 Activities \u2192 Type \u2192 Activity rather than through Tours; new filter wptm_breadcrumb_trail<\/code>.<\/li>\n?wptm_b=<\/code> address) is noindex, follow<\/code> through wp_robots<\/code> and Rank Math's filter, so a confirmation is never indexed as a copy of the tour. The activity hero is preloaded like the tour hero. The hero section defaults to an h2 title, since the theme usually prints the page title as the h1. Card images carry the alt text written in the media library when there is one. Guide and review dates are <time><\/code> elements.<\/li>\ntools\/minify.sh<\/code> rebuilds them) and the plugin serves the .min<\/code> file whenever it is current \u2014 213 KB \u2192 118 KB for the tour stylesheet before compression \u2014 falling back to the readable source under SCRIPT_DEBUG<\/code>, when the copy is older than its source, or through wptm_use_minified_assets<\/code>. Card\\prime()<\/code> warms posts, meta, terms and featured images for a row of cards in three queries and is used by the shortcode grids, the hub, landing and car-hire pages, the sections library and the activity page; the related-activities scorer reads candidate meta in one query instead of one per candidate.<\/li>\ndecimal<\/code> field type in the native form helper. New strings on the registry with French, Spanish and Arabic tables. No migration, no change to tours, URLs, relationships or existing data.<\/li>\n<\/ul>\n\n1.6.1<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
\n
\n
\n
wptm_analytics_event<\/code> is there for a site that wants to connect GA4 or anything else itself.<\/li>\n\n
*_wptm_resources<\/code> and *_wptm_partners<\/code>, granted to the roles that already manage bookings and filterable separately.<\/li>\n1.5.0<\/h4>\n\n
\n
Earlier releases<\/h4>\n\n