Linux 软件免费装
Banner图

Tripvance

开发者 abourri
更新时间 2026年10月20日 03:09
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

booking travel tours activities itinerary

下载

2.5.0 2.0.1 2.9.0 2.5.1 1.12.0 1.8.13 2.10.1 1.8.11 1.35.2 1.42.1 2.8.7 2.8.10

详情介绍:

Tripvance brings tours, activities and travel experiences to WordPress: a Tours post type, tour pages built from real fields, and a booking request form. It is a request and confirmation system: the agency answers each request. There is no payment processing. Tours Each tour has a gallery, a short description, highlights, an itinerary, what is included and what is not, a meeting point, and questions and answers. The itinerary is written a card at a time — press Add a day, give it a title and a description — and comes out in two shapes, picking the right one by itself: a run of numbered days for a trip of several days, and a timeline of times and stops for a day trip. A section with no data is not rendered, so a page never shows an empty heading. Tour layouts Seven layouts, each built for one kind of tour, all drawing the same content, prices and booking form: Salma (booking focused — gallery beside the two-step booking panel), Sara (marketplace product page with a price card that follows the reader), Atlas (multi-day — the route and the days across the page with a day index), Sahara (photo-first, no sidebar), Medina (compact, for city tours and short activities), Qamar (premium storytelling for private and luxury journeys) and Classic (simple and theme-friendly). Atlas has two styles (Clean, Zellige) and Sahara three gallery presentations (Cinematic, Immersive, Mosaic). The site picks a default and each tour can choose its own. Legacy layouts from earlier versions remain supported for existing tours. Tours are filed under destinations, tour types, departure points, trip lengths and categories, each with its own archive page and filters. Two kinds of travel business Tripvance ships two presentations of the same content, chosen under Settings → Website experience. Standard is what the plugin has always been: a catalogue with prices, availability and a booking form, and it is the default on every site. Luxury Editorial redraws the same tours, destinations and activities as a travel magazine, for a bespoke travel designer who sells a journey by describing it rather than by pricing it — journey collections, editorial destination pages, a page design with no price card, and a short private enquiry in place of a checkout. Switching between them changes nothing you have written, and there is no second catalogue to keep in step. Booking requests The form asks for a date, a party size and how to reach the traveller. By default it behaves as an enquiry system. If you enable seat-capacity enforcement, seats are held atomically against the departure while a request is open, so two simultaneous requests cannot both take the last seat. Requests are managed from a booking screen with a status workflow, internal notes and an operations dashboard. Transfers Private transfers (airport to hotel, city to city) are a post type of their own, at /transfers/{slug}/. Each transfer describes its route, pickup and drop-off, estimated duration, operating hours, minimum booking notice and practical information, and lists the Vehicle Types it offers with a price for each. Vehicle Types are reusable, customer-facing options (for example "Comfort minivan or similar") with a class, capacity, luggage, features and a picture; they are not public pages. A round trip is priced as two journeys in the same Vehicle Type. There is no distance-based or automatic pricing. A transfer can also list the stops on the way (Marrakech → Tizi n'Tichka → Ait Ben Haddou → Ouarzazate), each with an optional description and stop time, drawn on the page as a route line — typed by the agency, never looked up or drawn on a map — and its own questions and answers, shown as an accordion. The transfer page leads with the route, the duration and the starting price, then the vehicles and the request form, then the practical information, the questions and the photographs (with a viewer). The optional transfer list at /transfers/ and the homepage Transfers section show transport cards (route, duration, capacity and "from" price); the homepage section offers three layouts: Classic Cards, Route Focus and Premium Transport. The visitor chooses a Vehicle Type, a pickup date and time, passengers and luggage, and can add flight details. Capacity is checked in the browser and again on the server. The request becomes an ordinary booking record, with the same statuses, reservation ledger, messages, quotes and Guest Pass as a tour, and the price is stored with it when it arrives. In Operations, the Fleet holds the physical vehicles. A fleet vehicle can be linked to a Vehicle Type, and assigning one to a transfer booking warns when it does not match the requested type and is refused when it cannot carry the passengers. Fleet is optional: transfers can be booked without it. Privacy & Cookies An optional consent banner (off by default) with Necessary, Analytics, Marketing and Preferences categories holds back the scripts you place in it until the visitor accepts their category. It helps collect and honour consent; it does not by itself make a site legally compliant. Presentation Tour cards can carry a strip of gallery thumbnails along the foot of their picture: pointing at one, or tapping it, shows that photo in the card, so a visitor looks through a tour without opening it (Settings > Tour listings). Seven curated tour layouts, with style and gallery variants, chosen per tour or site wide, on one shared foundation (legacy layouts from earlier versions remain supported for existing tours): a sticky section navigation, a booking ticket beside the price, a route at a glance, an itinerary drawn as days or as a timeline, group rates, questions and answers, and reviews. The plugin inherits the theme's typography and loads no fonts of its own. Listing pages with filters, sorting and cards; a Tours block and a [wptm_tours] shortcode for a grid of tours anywhere, and [wptm_activities] for a grid of activities — each activity can carry its own price and take booking requests directly through the same request system as a tour; a homepage template assembled from your tours, destinations, activities and trust details; and a car hire template for the driving side of the business — the fleet, the services, the routes you cover and the prices you quote. Multilingual Tripvance uses the WordPress translation system throughout and is ready for community language packs from translate.wordpress.org. It also includes built-in French, Spanish and Arabic front-end fallbacks, with right-to-left layouts for Arabic. Polylang is supported properly, not nominally. Tours, activities and every taxonomy the plugin owns are registered as translatable. Tours, terms and the pages the plugin generates are given their language and linked to their translations, so a language switcher lands on the right page. A generated page is written in its own language, not in the language of whoever pressed the button. Booking requests record the language the traveller was reading, and the confirmation, the voucher and the reminder are all written in it. Wording you type yourself — the homepage, the car-hire page, the default inclusions — appears under Languages > String translations so it can differ per language. Addresses can be translated too, and are not by default. Switch on "Addresses per language" in the settings and a French page becomes /fr/circuits/ rather than /fr/tours/, with the destination, category, departure and trip length sections following it; the words come from the same translation catalogue. The addresses you already have keep working and redirect to the new ones. Leave it off and no address on the site changes, whatever language packs are installed. A site that generated its pages before adding a language can put them right from the settings screen: each page's title, starting wording and address go back into its own language, a page you have edited is left alone, and the previous address redirects. An optional language switcher goes into the theme's own menus — desktop header, mobile menu, footer, or a shortcode wherever you like — and each language links to the translation of the page the visitor is on: a French reader on an English tour lands on the French tour. Polylang decides which page that is and keeps printing the hreflang tags; Tripvance only draws the control, in the menu's own typography, with no flags, no external assets and no second translation system. Without Polylang the plugin runs unchanged. Search engines Tripvance prints no canonical tag, meta description or Open Graph markup, and no site-wide schema. Those belong to an SEO plugin, and two sources for one signal is worse than one. Tripvance provides limited Product structured data for eligible Tour and Activity pages, including accurate pricing and genuine on-site review aggregates. When Rank Math is active, Tripvance integrates with its structured-data graph to avoid duplicate Product entities. General SEO and site-wide Schema remain under the control of the site's SEO plugin. In practice: a price is included only when it is the price the page shows and a traveller can book (one Offer at the public "From" price — the fixed price, or the lowest valid Group Rate; nothing for a tour on request), and a rating only from approved reviews of that tour, when the page shows the same average and count. Nothing is added to the homepage, archives, taxonomy pages, FAQs or private views such as booking confirmations and Guest Passes. The setting is under Tripvance > Settings > Search result product data. Structured data makes a page eligible for rich results; search engines decide whether prices or review stars are shown, and it does not affect ranking. It also emits clean semantic markup, keeps taxonomy archives crawlable, marks empty ones as noindex, and keeps them out of the sitemap. Import Existing WooCommerce products can be imported as tours, with a dry run first that reports exactly what would happen and creates nothing.

安装:

  1. Upload the plugin folder to /wp-content/plugins/, or install it through Plugins → Add New.
  2. Activate it. Tripvance prepares its required database tables, options and capabilities, but creates no tours, terms, pages or demo content automatically.
  3. 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.
  4. Go to Tripvance → Settings to choose the booking behaviour, contact details and tour-page design. Currency is set on each tour's pricing fields.
  5. Add a tour under Tours → Add New.

屏幕截图:

  • The booking ticket, with the two-step request form.
  • The listing page with filters, sorting and tour cards.
  • The route at a glance and the itinerary.
  • The bookings dashboard in the admin.

升级注意事项:

2.10.1 4 cards per row; editable Luxury footer columns; Luxury directory pages and Morocco Trip Planner (search-ready), applied automatically. Compact cookie banner with a shorter default text; a calmer Bookings list. Luxury page starters removed; existing pages stay. 2.10.0 Backups and restores now carry activities, transfers and vehicle profiles. A backup made by this version (format 2) needs 2.10.0 or later to restore. 2.9.9 New: booking forms without a tour (shortcode, button design, printed booking slip) and a custom booking reference format. The Luxury footer can be hidden per page. The luxury demo makes no pages; its unpublished demo pages go to the Trash. 2.9.8 New optional Marketplace tour card style (Settings → Tour card style). Homepage article pictures are no longer cropped (16:9 frames). Existing sites keep their card style; no data changes. 2.9.7 The tour section bar (Highlights, Route, Description…) now stays exactly under the theme's menu while the page scrolls, whatever the theme's header does on the way down: no more bar hidden behind the menu, and no more gap between the two. No data or setting changes. 2.9.6 Activities and Transfers now show their names in Rank Math's Sitemap settings (they were listed with an empty label). No data, setting or address changes. 2.9.5 The cookie banner now speaks the page's language (French, Spanish, Arabic, English; per-language wording with Polylang), adds Global Privacy Control and Google Consent Mode v2, and a corner button to change one's choice. No data migration. 2.9.4 Security and stability release: safer Trip Builder requests on cached pages, rate limits that cannot be bypassed, formula-safe CSV exports and admin notices that cannot be spoofed. Settings now opens one group at a time. No data migration. 2.9.3 Listing banners reach both edges of the window and sit against the theme's header; the list view's filters lose their frame; the card WhatsApp button moves beside "View tour". No data or setting changes. 2.9.2 New Experium colour palette (one choice in Settings > Brand identity) and a new Panorama Slider homepage hero with up to ten photographs. The tour section bar and facts strip follow the theme's page colour; the homepage hero closes the gap under any theme header. 2.9.1 New Settings > Addresses & SEO: shared or translated URL bases per language (Polylang Free), with live preview, 301 redirects and restore. Updating changes no existing URL. 2.9.0 Transfers now include route stops, per-transfer FAQs, an updated page and photo viewer, improved archive cards, and three homepage layouts. Existing transfers, bookings, prices, URLs, and settings are preserved. The transfer archive remains opt-in. 2.8.12 Builder saves (Homepage, page builder, car hire) can no longer leave the Save button spinning: every outcome ends within 30 seconds with the button back, the edits kept and a clear message. No data, setting, SEO or address changes. 2.8.11 Tour pages follow the theme's content width (with a centred fallback when the theme gives none) and clear a fixed theme header; Site pages and the page builder buttons are aligned and steadier. No data, setting or address changes. 2.8.10 Adds an optional Setup wizard (currency, tour and activity addresses, default design). Updating changes no address, price, currency, design or setting. 2.8.9 Bookings dashboard, list and booking screen reworked (Quick view, quick filters, Needs attention, save report); site pages list and page builder fixes. No data migration. 2.8.8 Booking screen: a summary from saved data, one suggested next action, panels grouped into five sections, and a warning before unsaved changes are lost. No data, price, status, message or document behaviour changes. 2.8.7 Settings reorganised into one grouped navigation with a single Save button, plus fixes for a PHP warning in Settings, the System status layout and narrow-screen tables. No setting, data or booking behaviour changes. 2.8.6 Visual and admin workflow polish only. No booking, pricing, database schema, stored data or customer-facing workflow changes. 2.8.5 Prices per booking with documented revisions, a booking's own trip content, and PDF quotes, invoices and trip programmes kept as issued. Two new tables; existing bookings, prices, links and tokens are unchanged and nothing is repriced. 2.8.3 Bookings, price snapshots and notifications are confirmed as stored before success is shown; an unconfirmed save is held and settled later; repeated requests and mail retries follow the real booking state; the Guest Pass map prefers the booking's location. No data change. 2.8.2 Luxury enquiries confirm only stored requests and survive concurrent or interrupted submissions; the Guest Pass is clearer on screen and on paper. No data change. 2.8.1 Stabilisation before 3.0: booking requests from cached pages stay separate per visitor, repeated submissions resolve to one booking, expired forms keep what was typed, and interrupted e-mails are flagged instead of stuck. No data migration; existing bookings, prices and layouts are unchanged. 2.8.0 Curated tour layouts: Salma, Sara, Atlas, Sahara, Medina, Qamar and Classic, with Atlas styles and Sahara gallery variants. Older layout choices keep rendering as before; nothing needs re-saving. 2.7.0 Tour display stabilization across layouts: consistent cards, Highlights, navigation, booking components and empty states. Existing Tours, bookings, pricing and Group Rates remain compatible; nothing needs re-saving. 2.5.1 Hotfix for the Homepage FAQ section: equal card heights and no layout shifting when answers open. No data or settings changes.

常见问题:

Can travellers ask for a tailor-made trip?

Yes. Tripvance → Tailor-Made Requests → Settings has a "Create Trip Builder Page" button, or lets you choose an existing page; nothing is created until you press it. The page shows a step-by-step wizard (dates, length, interests, destinations, travel style, accommodation, travellers, budget, contact) whose steps and answers you manage on the same screen. Requests are private records with a TMR reference, separate from bookings, and "Create Draft Tour" starts a draft tour from one. The [tripvance_trip_builder] shortcode and the Trip Builder block place the wizard anywhere. An optional "Plan your own trip" call to action on tour pages is off by default.

Is there a setup guide?

Yes. After activation a dismissible welcome offers a step-by-step guide (Tripvance → Settings → Setup guide): tours, homepage and its preset, tour design, booking. Every step reads your site as it is and only offers what is missing; nothing is created or changed without a button pressed for it. The guide also offers demo content — sample tours, activities and destinations, every item marked as demo — with a one-click removal that never touches your own content. The guide can be restarted from Tripvance → Settings.

Is there a homepage?

Yes. Tripvance → Site pages → Homepage creates a page on the "Tripvance homepage" template and fills it from what the site already has. Its hero can be a classic image cover, a muted looping video with accessible playback and optional sound controls, a split featured-tour spotlight, layered floating image stories, or an animated travel-colour mesh. The same buttons, optional reassurance points and five tour-search designs adapt to every hero; search can be hidden entirely. The rest includes featured tours, destinations and tour types with their counts, a signature tour, activities, trust, "why choose us", articles and a final call to action. Sections can be switched off and reordered; a section with nothing to show is not printed. Setting the page as the site's front page is a separate, explicit button.

Is there a car hire page?

Yes. Tours → Car hire creates a page on the "Tripvance car hire page" template, built the same way as the homepage: sections you tick and order, a preset to arrange them, a preview before anything goes live. It holds a hero, a fleet with a filter by kind of vehicle, the services a driver is hired for, a table of routes with journey times and prices, your destinations and tours, the booking steps, trust details, a gallery, testimonials and questions. Only the vehicle's name is required; a cell left empty prints nothing and a section with nothing in it is not printed at all. Publishing the page is a separate, explicit button, and it is a normal page, so you add it to your menu yourself.

How do people ask for a quote on the car hire page?

Through the form plugin you already use. Paste its shortcode — Contact Form 7, WPForms, Forminator, whichever it is — into the Request form group on Tours → Car hire, and the form is printed in its own section, styled to match the page. Tripvance does not add a second enquiry system for cars: your form plugin already holds the fields, the address the mail goes to, the spam protection and the export, and duplicating that would only give you two places to check. Leave the shortcode empty and the section is not printed at all. The section answers to #wptm-cars-request, so a hero or call-to-action button can scroll straight to it.

Does it create pages or content when I activate it?

No. Activation only registers the post types and prepares the database. A notice then offers a starter kit, and nothing is created until you press the button. The starter kit's sample destinations are Moroccan examples; rename or delete any of them.

How do I get review stars in Google search results?

Tripvance cannot make stars appear; Google decides that. What it does is make a tour eligible: turn on reviews under Tripvance → Settings and let travellers leave rated reviews, and keep "Search result product data" switched on. Once the tour has approved rated reviews, their average and count — the same figures printed on the page — are added to the tour's Product data. With Rank Math active they go into the Product Rank Math already builds for the tour, or into one Product added to Rank Math's graph if it has none: Tripvance does not add a second Product when Rank Math already provides one for the current Tour or Activity. Ratings can be left out separately with "Include the average rating from approved reviews"; a site that had switched the earlier rating option off keeps it off. Ratings from other websites are never included, and activity pages, which do not display reviews, carry no rating.

Is there an activities page?

Optionally. Activities are pages of their own from the start; the listing at /activities/ and a page per activity type are switched on under Tripvance → Settings (activity archive). With it on, the plugin draws both — title, description, a row of type links, the activity cards with their prices, pagination — and a theme can replace either with archive-wptm_activity.php or taxonomy-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.css next to tour.min.css). Define SCRIPT_DEBUG 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 (use the corresponding paths for other CSS or JavaScript files); until then the edited file is served as it is, because a minified copy older than its source is never used.

Does this take payments?

No. It records booking requests and the agency confirms them. No payment gateway is included and none is required.

Can I send a quote, an invoice or a trip programme as a PDF?

Yes. Open a booking, set its price under Price & services if needed, and use the Documents panel: Preview gives a draft without a number, Issue gives the numbered document and keeps an unchangeable copy. PDFs are produced on your own server. Tripvance prints the details you give it; check that your invoices carry what the rules where you trade require.

Is Advanced Custom Fields required?

No. The plugin has its own fields and works without it. If ACF is installed the same fields are shown through ACF instead. The free version is enough; no premium field type is used.

Will it conflict with my SEO plugin?

It should not. The plugin outputs no canonical, meta description or Open Graph markup and no site-wide schema, leaving those to Rank Math, Yoast or whichever you use. Its only structured data is one Product on eligible Tour and Activity pages; with Rank Math it is merged into Rank Math's own graph, and with Rank Math the page builder no longer writes Rank Math's title, description or focus keyword. If another SEO plugin already publishes a Product for your tours, switch off "Search result product data" or use the wptm_product_schema_print filter.

Does it work with Polylang?

Yes, with the free version. Tours, activities, taxonomy terms and generated pages are assigned a language and linked to their translations, and each generated page is written in its own language. The homepage and the car hire page are created in every language at once and linked, so the language switcher and the hreflang tags are right from the start. The homepage's own wording gets a language tab per language in Tripvance > Site pages > Homepage: the same form, the source text above every box, and a box left empty falls back to the source language rather than leaving a hole. Booking mails, vouchers and reminders answer in the language the traveller booked in. Your other wording is still exposed in Languages > String translations. A language switcher can be switched on in Settings and printed in the theme's menus or through [wptm_language_switcher]; each language links to the real translation of the current page and never to a guessed address. Without Polylang nothing changes.

How do I change the addresses (URLs) of tours, activities and transfers?

In Tripvance > Settings > Addresses & SEO. Two structures are offered. Shared slugs use one base for every language (/tours/, /fr/tours/, /es/tours/; the language folders are Polylang's). Translated slugs give each language its own base (/tours/, /fr/circuits/, /es/tours/; activities: activities, activites, actividades; transfers: transfers, transferts, traslados), with Polylang Free. Choosing Translated slugs fills these words in; they are suggestions you can change, and any other language starts from the English word rather than an invented one. Translating a base translates the address only: a French address shows the French translation of a tour where one exists. A new site with Polylang already active is offered translated slugs in the Setup wizard. An existing site keeps exactly the addresses it has, through the update and afterwards, including when Polylang or a new language is added later, until an administrator changes them here. The screen shows the addresses each word produces as you type. Save changes checks every word first and saves nothing if one is refused (an empty or reserved word, a language code, or two Tripvance routes at one address); the error is shown beside the field. Going back to an earlier word is always possible: it simply becomes the live address again. After a save the screen lists every route that moved and checks it against the rebuilt rules. Back up your site before changing published addresses. Every previous base keeps answering with one permanent (301) redirect to the same tour, activity, transfer, list or term in the same language, so links and indexed pages keep working; several successive changes still take one hop, and a word that becomes active again stops redirecting. Unknown addresses keep answering 404; nothing is sent to the homepage or to another language. No post slug, title, content, ID, language, booking or SEO field is changed, and the plugin builds canonical, hreflang and sitemap addresses through WordPress's own functions, so Rank Math, Yoast and Polylang publish the new ones. Search rankings can fluctuate while search engines process the change; check your sitemap and Google Search Console. Restore Previous URL Configuration puts the previous bases back, with the same preview and redirects; it cannot restore content, rankings or links on other sites. If Polylang is switched off, the site keeps its default language's addresses and returns to the per-language ones when it is switched on again. Supported: language folders (/fr/, with or without the default language's folder), WordPress in a subdirectory, structures with or without a trailing slash. Not supported for changes (the current addresses are kept and the screen says why): plain permalinks, Polylang languages by domain, subdomain or content, and bases set by code through the wptm_rewrite_slugs or wptm_language_slugs filters. Where Polylang Pro is active, its own Translate slugs module owns translated bases and Tripvance offers shared slugs only. Multisite works per site but has not been tested.

Can I take booking requests for something that is not a tour?

Yes. Tripvance → Bookings → Booking forms makes a booking request form with no tour page behind it — an airport pick-up, a private dinner, a day with a driver. Give it a name, optionally a price, the largest party and the notice you need, and place it on any page with [tripvance_booking_form id="123"]: a button that opens the form in a window. Add display="inline" to show the form in the page instead. The button's words, icon, style (solid, outline, soft), shape (rounded, pill, square), size, width, alignment and colour are set on the form with a live preview, and one placement can change any of them in the shortcode (icon="calendar" style="outline"…). When a request is sent the traveller sees a booking slip print out of a small receipt printer: the reference, what was booked, the date, the party, the estimate and what happens next, with buttons to continue on WhatsApp, download the confirmation or print the slip.

Can I change the booking reference (WPT-2026-001)?

Yes, in Settings → Booking reference: your own letters and hyphens with {YYYY}, {YY}, {MM}, {DD} and {NUM}, and how many digits the number has — MTL-{YY}{MM}-{NUM} gives MTL-2610-0001. An example updates as you type. New requests use it; references already given keep theirs. The numbering starts again each year only when the year is part of the reference. Requests arrive in Bookings under the name you gave the form, with the same e-mails, statuses and documents as a tour booking.

Can two people book the last seat at once?

If seat-capacity enforcement is enabled, no. Tripvance obtains a departure lock and performs the capacity test as part of the reservation write, so only one request can take the final seat. Capacity enforcement is off by default because many agencies use the form as an enquiry system.

更新日志:

2.10.1 2.10.0 2.9.9 2.9.8 2.9.7 2.9.6 Earlier versions The full history, version by version, is in changelog.txt in the plugin folder.