Tripvance -- WordPress 插件

开发者	abourri
更新时间	2026年9月13日 01:33
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

1.12.0

A fourth way to show your tours: the Moroccan Editorial Carousel, under Tripvance → Homepage → Featured tours layout. A warm editorial band rather than a grid — a small label between two fine rules, a heading set in two colours, a sentence under it, and the tours themselves as large photographs on a track a visitor can swipe, with a quiet round button at each edge. Four across on a wide screen, three on a large tablet, two on a small one and a little over one on a phone, so it is obvious there is more to see. Same tours, same order, same count as every other layout; nothing changes until you choose it.
The band is also a block and a shortcode. Choose it under Layout on the Tours block, on the tours card in the visual builder, or with [wptm_tours layout="moroccan-editorial"] — anywhere you already put a grid of tours. Its colours and decorations come from the Homepage screen, so a carousel dropped into a page looks like the same site rather than a second one; only the words belong to the page it is on.
Five backgrounds, and every colour is yours if you want it. Moroccan Editorial is warm ivory with terracotta and olive; there is also Clean (your theme's own page, only the type coloured), Warm Sand, Olive Mist and Terracotta Wash. Ten colour boxes sit under them with WordPress's own colour picker — background, heading, accent, body text, badge, price, arrows and button. Set one and it wins over the preset; clear it and the preset comes back. Every preset was measured rather than eyeballed: the smallest text on each reads at the ratio the accessibility guidelines ask for, and that is checked on every build.
A heading in two colours, without writing any HTML. Type the heading in one box — "Our Signature Journeys" — and the word or two you want set apart in the other — "Journeys". If those words are in the heading they are coloured where they stand; your own capitalisation wins.
Cards that do not look stamped out. Soft Organic gives each card uneven corners and a tilt of about half a degree, alternating along the row — enough to read as laid out by hand, not enough to read as crooked, and removed altogether on phones where a card is most of the screen wide. Standard Rounded is there for a site that would rather not. Four picture shapes: landscape, wider, square or upright.
Badges, from what you have already written. A card can carry the tour's own Badge field, its first tour category or its first tour type — and nothing at all if that is empty. Nothing is invented: a tour is a best seller because you wrote that it is, on the tour. The two accent colours alternate along the row, or you can pick one.
Optional Moroccan decoration: a geometric motif in one corner, a drawn flourish, a palm and kasbah line at the foot, or all three, at three strengths. They are drawn behind the words, never over them, and the two that need room step aside below tablet width. No image is fetched for any of it and no font is loaded — the type is still your theme's, as everywhere else in Tripvance.
An optional editorial aside beside the heading on wide screens, an optional button under the cards, the destination with a pin, the sentence cut to a length you choose, and the price exactly as every other listing shows it — your currency, your wording, your group rates, and "Price on request" where that is the answer.
It can move on its own if you want it to — off by default, with a Pause button beside it, stopping for good the moment a visitor touches it, and never starting at all for somebody whose device asks for less motion.

1.11.0

A colour choice for the Luxury Editorial experience, under Tripvance → Settings. Neutral is the black ink on warm white the experience has always been. Sand is a warmer, quieter version of it — stone paper, soft brown ink, a terracotta accent. Midnight turns the whole page over: cream text on near-black, which is what a great many of the agencies this experience is for actually look like. Your brand colour, if you have set one, is used in all three; the tone is the palette it sits in, not a replacement for it. No fonts are loaded by any of them: the type is still whatever your theme uses.
Every colour in all three tones is checked against what is actually painted behind it, on every luxury surface, at every size, on each build. Words on a dark band, words over a photograph, words on a filled button, the quiet greys in a heading — each is measured the way the accessibility guidelines ask, and the build stops if any of them falls short. Several that had been failing quietly are fixed in this release: the quotation's attribution line, the small print on a dark band, the label on the sound button, and the buttons in the header while it sits over the hero.
Words you want heard. Put asterisks around a word or two in a heading — Morocco, slowly — and they are set in italic, in your brand colour, on a line of their own when the heading is long. It works in the hero, in section headings, in the footer statement and on a collection or enquiry page. Write nothing between asterisks and nothing changes, so a price with an asterisk after it is left exactly as you typed it.
The full-bleed story can carry a film, with the same four controls the hero has: the address, the second to open at, whether to offer a sound button, and whether phones get it. It behaves the same way too — silent, behind your words, never fetched for a visitor who has asked for less motion or is on a slow or metered connection, and never at all without a photograph set behind it, because the photograph is what everybody else sees.
Heading position on Why choose us, Destinations and Explore the site: centred over columns of equal weight, or at the start of the line. The three came with that decision made for them; now it is yours.
Smaller corrections. The film settings on the full-bleed story are now reachable from its shortcode as well as from the block and the Homepage screen. A film set with no photograph tells you so in the page builder instead of quietly showing nothing. And the heading on a destination's introduction is printed exactly as typed, because that field belongs to both experiences and an asterisk in it is far more likely to be a footnote than a mark-up instruction.

1.10.0

A homepage of its own for the Luxury Editorial experience. Choosing it in Settings now lays the page out for you: the luxury sections come on in the order they were designed to be read in, and the standard ones step aside. Nothing is lost either way — switching back to Standard puts your old homepage back exactly as it was, down to the order of the rows and the styling choices, and switching to Luxury again finds that page as you left it. Upgrading changes nothing; only choosing does.
A cinematic hero that can carry a film. Paste a YouTube address or the address of a video from your media library into the hero's Video field. It plays silently behind your words, fills the screen at any shape without a black band at the edges, and opens at whatever second you choose so you can skip a slow first shot. A small button offers the sound to anybody who wants it — and only once the film is actually playing, so nobody is offered sound for a film that never arrived.
The film is careful with other people's data and attention. It is never fetched for a visitor whose device asks for less motion, never on a connection the browser reports as slow or metered, and not on phones unless you tick the box. It stops when it scrolls out of view and when the tab is in the background. Your photograph is what shows until the film is ready — and what shows instead of it in every case above — so choose it as carefully as the film.
Four new sections, all built for this experience rather than borrowed from the standard homepage. Why choose us: three or four reasons, numbered in the margin or set under a rule, written as sentences instead of badges with ticks. Destinations: the places you travel to as photographs, with the first given twice the room of the others, or as an even grid. Our purpose: why the agency exists, in one statement beside a photograph, with your commitments under it. Explore the site: cards you write yourself — a title, a line, a photograph and an address — for sending a reader to the pages that matter, rather than a taxonomy printed as a grid.
All four are also blocks and shortcodes, so they can be used on any page and not only the homepage; and on the Homepage screen each has a proper table you add rows to, with the media library behind the photograph field.
The Luxury Editorial preset is now made entirely of luxury sections. It used to borrow four rows from the standard homepage, which is why the two experiences never quite looked like different sites.

1.9.1

Choosing a photograph on a Journey collection or a destination now opens your media library. The field on those screens was a box asking for an address, because the picker it was meant to use only runs on the homepage and car-hire builders; it is now a real picker — choose, replace, remove, with the photograph shown — on every screen that has one. The address you may already have typed is kept and still works.
Photographs on a Journey collection are chosen, not typed. It was a text box expecting a list of numbers. It is now the media library, with thumbnails, one photograph removed at a time or all of them at once, and drag to set the order — with buttons beside each one for anybody not using a mouse. What is stored has not changed, so a gallery you have already built opens exactly as you left it.
Choosing journeys, destinations and journal stories is now a search box instead of a list of tick boxes. The list showed the first eighty and stopped, so an agency with more than eighty could not reach the rest — and worse, anything you had already chosen that fell outside those eighty was not on the screen, so saving the page quietly dropped it. The search reaches everything, keeps what you have already chosen whether or not it appears in the results, and stores the order you put them in. The same fix applies to the collection and interest rows on the Homepage screen, which stopped at forty.
Private enquiries are protected the way booking requests already were: the same hidden field a person never sees, the same check that the form was not filled in by a machine in under three seconds, and the same hourly and daily limit per visitor. A mistyped e-mail address gives the allowance straight back; a double click no longer files the enquiry twice.
An enquiry now sends two messages, and neither of them is the booking letter. You get "New private journey enquiry" with everything the traveller wrote and a link to it; the traveller gets a short acknowledgement that says a person will write back — and says in as many words that nothing is booked and nothing is payable. Both go through the same outbox as every other Tripvance message, so they are retried if your mail server is down, appear in the booking's own message history, and cannot be sent twice.
With the Standard experience selected, the Luxury framework now adds nothing at all: no taxonomies on the translation list, no fields on a term screen, no sections in the editor, no stylesheet in the page. Upgrading from 1.8.13 without turning it on changes nothing, and that is now checked registry by registry against 1.8.13 on every build.
The "Own a property" page starter is now "Own in Morocco", and its words no longer assume what you are offering. Pages you have already created are untouched.
Small corrections: the picture on a Journey collection or interest is now offered on those screens at all; the luxury pages carry no fixed styling in their markup beyond the values that genuinely differ per item; and the enquiry form's own working files are removed when the plugin is deleted.

1.9.0

A new Website experience setting, under Tripvance → Settings. Standard / tour operator is what you have now and stays selected; Luxury Editorial is for an agency that designs private journeys rather than selling places on a tour. Nothing on your site changes until you choose it, and choosing it back changes nothing you have written.
Journey collections. A themed way into your journeys — Wellbeing & Yoga, Food Lovers, Desert Journeys — with its own address and its own editorial page: a photograph across the screen, your introduction, the journeys you choose in the order you choose them, a long piece of writing, a composition of photographs, a quotation, the places they visit and one invitation at the end. A journey can belong to more than one, and nothing is duplicated: a collection is a way of filing the tours you already have.
Travel interests. What a journey is about — food, wellness, craftsmanship, architecture — used to work out related journeys, what to show on a destination page and what belongs together, so you are not maintaining the same list in three places.
A Luxury Journey page design for a tour. A magazine feature rather than a product page: the photograph, the story, why you love it, the facts stated quietly, the days as chapters — Day 01, Marrakech — instead of rows that open and close, where your travellers sleep, the moments they will remember, the gallery, and one way to start a conversation. Your existing page designs are untouched and still available.
An editorial layout for a destination, chosen on the destination itself, so the two or three places you have written about properly get a magazine page while the rest keep the listing they have.
Private enquiries. A journey can be sold as a booking, as a private enquiry or as a bespoke journey. The last two replace the booking form with ten short questions — who you are, roughly when, how many, what you are interested in, where you like to stay — and the answers arrive in the same Bookings screen as everything else, with a panel showing what the traveller said.
Fifteen new sections for the page builder and the block editor: editorial split, full-bleed story, overlapping editorial, journey spotlight, inspirational journeys, destination chapter, experience collection, editorial mosaic, quotation, travel designer, brand statement, journal stories, concierge invitation, and an optional minimal header and footer.
Seven new homepage sections and a Luxury Editorial homepage preset, on the Homepage screen you already use, with the same order and show/hide controls. Every new section starts switched off.
Nine choices that shape every luxury page at once — content width, section rhythm, photograph treatment, corner style, button style, heading scale, text width, overlay strength and motion. (A tenth, colour, arrived in 1.11.0.) No fonts are loaded: the text follows whatever your theme already uses.
Six page starters and an optional sample site you can add with one button and remove with another. Nothing you already have is renamed, changed or deleted by either.
Everything new is built for a phone first, reads correctly right to left in Arabic, works with Polylang, and stops moving entirely for a visitor who has asked their device for less motion.

1.8.13

Bookings dashboard, redrawn. The top of the screen now tells you the date and how many requests are waiting on you, with the search box beside it. Below it, two figures instead of six boxes: how many requests came in this week, whether that is more or fewer than the week before, and the shape of the last fourteen days as a small row of bars; and how many of this week's requests you have agreed, as a number, a percentage and a bar. The four states of the pipeline — pending, contacted, confirmed, cancelled — sit beside them as one strip, each in its own colour.
Answer a request without opening it. Every row on "Needs attention" and "Travelling today" now carries a WhatsApp button that opens the app with the traveller's name, the tour and the reference already typed, an e-mail button, and one button that moves the request on: "Mark contacted" on a new request, "Confirm" on one you have already spoken to. Declining and cancelling stay on the booking screen, where you can write down why.
Why a request needs attention is now marked as well as written, in three levels of urgency. "Most asked about this week" shows each tour with a bar for its share of the week. Every panel heading carries the number of rows under it, and an empty list says so in a quiet frame instead of a line of grey text.
The calendar has a key to the three colours, a "This month" button for getting back from wherever you have browsed to, and a count on any day with more than one departure.
The dashboard loads in a handful of database queries instead of several hundred on a site with a full book of bookings.
The dashboard works properly on a phone: the booking rows become blocks, the buttons take a full touch target, and nothing runs off the side of the screen. It reads correctly right to left in Arabic, including the "+6 vs last week" figure, which used to come out as "6+".
Tour cards, refined. The card on your landing pages, destination hubs, homepage grid and shortcodes and the card on your tour listing are now drawn as the same object: the same corner, the same lift, the same photograph shape (3:2, which is the shape your camera gives you — the card used to trim square and 3:2 photographs to 4:3), the same typography and the same shadow, which is now a contact line under a soft spread rather than one large blur.
Small marks on a card are quieter and the accent is used where it counts. A short rule in your accent colour sits before the place name, the pin that used to be there is gone, the badge and the duration chip are tags rather than lozenges with a shadow that holds them against a pale sky, and the clock and calendar marks are grey. "from" is now a small label above the price on every card, the price itself is a step larger, and "View tour" is underlined with one crisp line in your accent as the pointer draws it out.
The WhatsApp button on a card is a little smaller on a desktop, where it was a white disc on the corner of every photograph in the grid, and keeps its full size on a touch screen.

1.8.12

Preserve case in booking confirmation keys so success and validation messages work with persistent object caches.
Prevent caching of booking response pages and prevent their keys from being sent in Referer headers.
Apply the private-document cache and referrer protections to valid and invalid voucher requests.

1.8.11

Homepage "Why choose us": a third layout, "Numbered panels". The heading at the start of the section, then one outlined panel for each reason, each led by a small number in your own accent colour. It adds no background of its own and no new type sizes — it sits on the page's own ground and grows with the window exactly as the rest of the homepage does. The row works out its own column count, so two reasons and five reasons both come out right, and the layout reads the same in Arabic as in English.
Homepage "Featured tours": square photographs are shown whole. Tour photographs uploaded at 800×800 were being trimmed top and bottom to fit the card's wider frame, which cut off heads and horizons; the homepage grid now asks for a square frame. Other pages are unchanged.
Buttons: the label on a filled button is once again the colour chosen to sit on your accent — on sites with a dark accent colour it had been taking the page's dark text and was hard to read. The button also keeps a defined edge on photographs and on coloured bands, and answers a press instead of simply stopping.
Outlined buttons are drawn with one crisp line instead of one and a half, which looked slightly out of focus beside the filled button next to it.
Featured tour cards lifted twice on hover — once as a card and once as a list item — and now lift once, exactly as the same card does on every other page.
The photograph count on a destination tile is a small solid chip instead of a translucent one, which could leave white numerals on a pale sky.

1.8.9

Homepage "Featured tours" and the other homepage grids: a card is now as tall as the tour inside it. On themes that lay their content column out as a grid or a flex column with a minimum height — the usual way of holding the footer at the foot of a short page — the row of cards was stretched to fill that height, which pushed the price and "View tour" to the bottom and left a band of white inside every card. The rows now keep their own height on every theme.
Tour cards everywhere (featured grid, landing pages, destination hubs, tour and activity grids, the Tours block and [wptm_tours]): 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.
Tour page sidebar, "Need help?" and "Meeting point": the heading is set at a fixed size a little under the booking ticket's instead of growing with the width of the window while its column stays the same width — it was being set larger than the price beside it on a wide screen, and wrapping to two lines in French and Arabic. The badge, its mark, the row icons and the spacing come down with it, and the card's padding is now written in logical properties so the badge sits the same way in Arabic as in English.

1.8.8

Tour page: "Good to know" is a section of the reading column, after "What to bring" and before the prices, drawn as a quiet note with the editor's own lines; it is no longer a sidebar card.
Sidebar "Need help?": phone and e-mail as rows, then WhatsApp as a green button across the card, with the WhatsApp mark instead of a share icon.
Booking ticket: the WhatsApp button reads "Book via WhatsApp" (French, Spanish and Arabic included) and carries the WhatsApp mark, on the ticket, the closing band and the WhatsApp booking mode.
Booking ticket: the reassurance row shares its width between the promises it holds — two in halves, three in thirds — instead of leaving an empty third; a long label such as "Languages" no longer breaks inside the word beside a long value.
Screenshots and demo content refreshed.

1.8.7

Tour cards (homepage featured tours, landing pages, destination hubs, tour grids, activities): a calmer, more editorial card. The duration leaves the photograph and joins the next departure in one small line under the title; the place line is one line, cut short rather than wrapped; the title holds two lines so every foot in a row starts level; the price sits on a hairline with a lowercase "from", and "View tour" is a word with a rule under it rather than a jumping arrow.
Photos on tour cards, new in Settings > Tour listings and on by default: a strip of up to three gallery thumbnails along the foot of the card's picture, beside the card's own. Pointing at one (or tapping it) shows that photo in the card, so a visitor can look through a tour without opening it; a "+N" says how many more the tour page holds. The card stays one link; the thumbnails are buttons beside it. Nothing is drawn for a tour without a gallery, and nothing loads on a page without a card.
Related tours on the tour page: the place on one line, the title on two, the duration and the price on one rule and the group-rate note beneath it, the "View tour" line level across the row.
SalmaDesign booking panel: the note under the party size now states the tour's minimum group size ("Minimum 2 travellers") where one is set, and the field refuses fewer; the ceiling still binds through the field but is no longer announced as a demand. The "Confirmation by email" reassurance is no longer a default, and the shipped wording is left out even where it was once copied into Settings, as the archive sidebar already did.
Itinerary: a day's text fills its column on every layout instead of stopping at a reading measure and leaving a blank band beside it.
Homepage "Trusted by" strip: pressing a logo opens its link. A mouse press focused the link, which turned the strip into a scrollable list under the pointer before the click completed; the list form is now for keyboard focus only. The pointer over the strip still holds it still.

1.8.6

Homepage: the photo viewer and the "Read the full review" window now open in the centre of the screen on every theme. Both are native dialogs and relied on the browser to place them; a theme reset that clears margins or repositions the dialog element pushed them into the top corner of the page. Their placement is now written out in the plugin's own stylesheet, with a closed dialog kept hidden whatever the theme does to the element.
Coding standards: a duplicated key in the visual builder's script strings, translator notes on every string with a placeholder, and precise sniff annotations on the prepared queries and the two admin pages that restore their own title. No behaviour change.

1.8.5

Booking screen: a compact header with the tour thumbnail, reference, customer, travel date, the saved status and one primary Save booking; a selected-but-unsaved status is shown as a separate chip beside it.
"Shown to guest" and "Internal only" labels on the Trip details, Guest Pass details, internal notes and status-reason groups, decided from what the pass, voucher and messages actually print.
Guest Pass disclosures summarise their saved values (pickup time and place, guide, vehicle, the payment summary the pass shows, the emergency contact), name the fallback that filled them, and mark unsaved edits without recomputing the saved summary.
Compact photo pickers with empty-state prompts; fleet thumbnails beside the vehicle name and the crew vehicle select; "Preview saved Guest Pass" loads the existing staff preview on request, with a new-tab link kept; regenerate and revoke sit apart under Manage access.
Bookings list: customer name with e-mail and country, readable travel and submitted dates, a Travelers column, an "Open booking" row action, sensible column widths. Sorting, filters, search, pagination, bulk actions and Screen Options unchanged.
History as a compact timeline with operator, date and time, and folded long notes. Booking storage, status transitions, reservation checks, Guest Pass access rules and every independent action form are unchanged.
Homepage: destination and tour-type grids balance their columns to the number of tiles on desktop (no orphan tile under a full row), a six-photo gallery fills a three-by-three, the search button stays on one line and inside the bar, and the figures on the trust bar read as figures.
Tour pages: the long booking form drawn twice on a page (in the page and in the phone dialog) no longer repeats its element ids, so every label and error message reaches its own field; the dialog is closed from the first byte instead of being printed open and closed by the script; on the Immersive layout only the hero asks the browser to fetch it first; the ticket background is served at a fitting size when it comes from the media library; an empty highlights band is skipped; keyboard focus rings on FAQ questions and gallery thumbnails.

1.8.4

Display the existing secured Guest Pass link prominently above confirmed bookings, with copy, preview and the existing email action.
Keep disabled, revoked and unavailable passes explicit; preserve token generation, access rules and public Guest Pass rendering.
Refine booking request information and editable trip fields; add direct section navigation and nearby booking save buttons.
Organize Guest Pass fields into accessible disclosures with responsive field grids and shared native booking saves.
Improve booking panels and dashboard controls for mobile and RTL layouts.
Reveal invalid fields inside closed sections; fix clipboard fallback feedback and duplicate access confirmations.

1.8.3

Fix booking saves being intercepted by nested quote, payment, crew, referral and WhatsApp forms.
Keep each admin action on its existing handler with independent form ownership, nonce and permissions.
Add a clear Save booking button, saved/selected status guidance and operator-specific save feedback.
Show booking context and navigation; add dashboard search using the existing booking search.
Improve mobile admin fields and panels; retain status transitions, history, pricing and frontend layouts.
Do not record a successful status transition when the metadata write fails.

1.8.2

Refine booking price panels, information rows and mobile touch targets using existing site colors.
Shorten group-pricing explanations in English, French, Spanish and Arabic.
Keep totals visible and place additional pricing explanations in an accessible disclosure.
Preserve all advertised prices and existing booking calculations.

1.8.1

Clarify group-dependent starting prices without changing advertised amounts.
Show configured group rates and server-calculated booking totals in all booking forms.
Require price review before submission; reject unsupported group sizes without guessing.
Preserve per-person/per-group models, child pricing, extras, seasons and existing booking snapshots.
Add English, French, Spanish and Arabic pricing labels with WordPress/Polylang translation support.

1.8.0

Visual Builder 2.0: a live preview beside the settings on the homepage, car-hire and page builder screens, click-to-edit sections in the preview, a section navigator with drag-and-drop, duplicate, hide/show, delete and undo, desktop/tablet/mobile preview widths, and a categorised "Add section" panel. Storage and the front end are unchanged.

1.7.7

Full-width page template with no sidebar (default for pages made from a starter; hero and closing band edge to edge), layout and web-address settings in the page builder, and a "Search engines and sharing" panel — title, description, main phrase, summary, sharing picture — saved into Rank Math / Yoast / SEOPress when present, with a live SEO checklist.

1.7.6

Page builder for pages made from a starter: the same section-by-section form as the homepage, with add/move/remove, box lists for filters, media pickers, per-section Save, Preview and explicit Publish. Homepage layout table fixed, drag handles replaced by arrows, preview folded. Friendlier status wording.

1.7.5

Homepage and Site pages screens rebuilt on the shared page builder introduced for Car hire in 1.7.4: numbered panels with side navigation and status, a Save button and Preview link in every section (also on each language tab), cards for trust items, team and testimonials, media-library pickers for every picture, icon lists with preview, reorder arrows and descriptions in the layout table, WhatsApp number check, setup steps, and a clearer three-step page creator with language and status columns. Storage and rendering unchanged.

1.7.4

Car hire settings rebuilt for non-technical owners: a Save button and Preview link in every section that returns you to that section, numbered panels with side navigation and status, cards for the fleet, trust items and reviews, media-library pickers for every picture, an icon list with preview, a form picker for Contact Form 7 / WPForms / Gravity Forms / Forminator / Fluent Forms, reorder arrows for sections and rows, an unsaved-changes guard, and a fix so buttons can link to #wptm-cars-request. Storage and rendering unchanged.

1.7.3

Refined the navigation language switcher so its globe, label and caret align with neighbouring menu items and inherit the theme typography.

1.7.2

Car hire admin builder: setup checklist, collapsible sections, quick navigation, add/remove repeaters, media-library gallery adapter and a sticky save action.

1.7.1

Visual section controls: media thumbnails and picker, named content searches with pagination and page-language filtering, and native button link selection.
FAQ and reassurance row editors with icons, duplication, collapse, drag ordering, accessible move buttons and removal undo. Structured rows are explicitly versioned; legacy text stays unchanged until intentional editing and remains as a backup.
Content, Appearance and Advanced panels, visual choices for existing styles, and automatic/manual selection modes including safe empty manual selections.
Debounced read-only section previews retain the previous result during loading and errors, with retry and contextual empty states.
Tours now use the shared registry and controls while retaining their existing block name, attributes, shortcode and renderer.
Shared media/icon controls enhance compatible Homepage and Car Hire scalar fields. Library image alt text is retained.
Avoid an early-translation notice while Polylang inspects resource post types.
Rebuilt minified assets. Build script accepts an optional local ESBUILD executable.

1.7.0 Activities become products: an activity can carry its own price and take booking requests directly, through the same engine tours use.

Pricing panel on the activity editor: price, currency, per person / per group / on request, starting-price switch, an optional pre-promotion price shown struck through, and a price note. Stored under the tour meta keys the pricing engine already reads, so quotes, snapshots, seasons, extras and the currency formatter apply unchanged.
Booking panel: an on/off switch (off for every existing activity, so nothing changes without a decision), booking mode (site setting, form, WhatsApp, external URL), custom button text, booking instructions, minimum and maximum participants, minimum notice.
One booking engine. The booking handler, the date lookup and the live price preview accept any product type declared through the new wptm_booking_post_types / wptm_booking_product 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.
A redesigned activity page: price and button in the header, a sticky booking panel beside the content on wide screens, a price bar on phones, highlights and "good to know" sections (two new optional fields), the confirmation section a tour shows after a request, and the same booking.js driving the form. An activity with no price and no booking renders as before, in one column.
Site pages. A new Pages screen (Tripvance → Site pages) lists every page the plugin has a hand in and makes new ones from starters — About us, Destination guide, Tour collection, Activities, Contact and booking, Blank — opened straight in the WordPress editor as ordinary draft pages the owner writes the way they want. The sections they are built from are a new library, each a block (under "Tripvance" in the inserter, previewed live) and a shortcode for the classic editor or any page builder: [wptm_hero], [wptm_trust], [wptm_cta], [wptm_faq], [wptm_contact], [wptm_reviews], [wptm_guides], [wptm_destinations], [wptm_tour_types], beside the existing [wptm_tours] and [wptm_activities]. Drawn on the plugin's own tokens, RTL-ready, with the site accent. Filters wptm_sections, wptm_page_starters, wptm_page_starter_content; action wptm_page_created.
A calmer admin. One "Tripvance" menu with seven entries — Dashboard, Tours, Activities, Bookings, Operations, Site pages, Settings — instead of twenty-six entries under Tours plus a separate Activities menu. Every other screen keeps its address and lives in one of the groups: a row of tabs at the top of each Tripvance screen moves between the screens of its group, the sidebar stays on the group whichever screen is open, and the dashboard lists everything. Long settings screens gain an "On this page" row of section links. The classic menu is one setting away (Settings → Admin menu). New filters wptm_admin_menu_groups, wptm_admin_menu_untabbed, wptm_compact_admin_menu.
Card\activity() — the shared card, for activities — and a [wptm_activities] 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.
Standards pass on the front end. Every small label the modules print now clears WCAG AA contrast: the muted grey tokens were darkened from 3:1 to over 4.5:1 on white across tokens.css, tour.css, home.css and sections.css, and eyebrows and kickers that were set in the bright accent take a new --wptm-gold-text shade — 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 on its gallery and tour cards so a long page paints its first screen sooner.
An activity archive. With the archive switched on, /activities/ and each activity type's page are drawn by the plugin — 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 — instead of the theme's blog listing. Theme overrides: archive-wptm_activity.php, taxonomy-wptm_activity_type.php, tripvance/archive-activities.php. Breadcrumbs on an activity now run Home → Activities → Type → Activity rather than through Tours; new filter wptm_breadcrumb_trail.
SEO, without a competing schema. The page that follows a booking request (the one-use ?wptm_b= address) is noindex, follow through wp_robots 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> elements.
Faster pages. Every stylesheet and script ships with a minified copy (tools/minify.sh rebuilds them) and the plugin serves the .min file whenever it is current — 213 KB → 118 KB for the tour stylesheet before compression — falling back to the readable source under SCRIPT_DEBUG, when the copy is older than its source, or through wptm_use_minified_assets. Card\prime() 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.
Activities list in the admin gains Price and Booking columns, read the way the card reads them.
New decimal 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.

1.6.1 Hardening release for pricing, scheduled departures and the operations workflow.

Persists unambiguous pricing choices and scheduled mode for tours that already have departures during an idempotent schema-v5 upgrade, while preserving legacy data.
Keeps quote-only tours free of placeholder prices and uses the configured traveller rates consistently, including a neutral 100% child-rate default.
Filters scheduled choices to departures that are genuinely bookable, applies inherited capacity consistently and prevents overselling in both public and staff booking paths.
Serialises quote decisions and manual-ledger changes per booking, preserves one accepted offer and refuses mixed currencies or impossible refund totals.
Expands guide, driver and vehicle conflict checks across the full trip and allows staff check-in only on confirmed bookings during the trip dates.
Runs pending data migrations on activation and repairs missing tables without marking an incomplete upgrade as successful.

1.6.0 The operations release: a booking request now has a whole working life inside WordPress — quote, acceptance, payment tracking, confirmation, crew and vehicle assignment, the trip itself, completion and a review request. 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 — no Business API, no automatic sending, no delivery tracking. Money the customer agreed to

Quotes. A versioned offer per booking with its own private page at /quote/{id}?k={key}, a public note, what is included and excluded, an expiry date, and Accept and Decline buttons in the customer's own language. The accepted quote is a frozen snapshot: editing a tour's prices afterwards never changes what somebody already agreed to.
Manual payments. A ledger of what actually arrived — amount, currency, method, date, reference — with received, refunded and outstanding computed from the rows rather than typed. One currency per booking, enforced. A printable receipt.
Server-side pricing. Adult and child rates, party-size bands, seasonal rates and optional extras are calculated once, on the server, and the booking form asks for the figure rather than doing arithmetic in the browser. Per-group tours are one price for the party, never multiplied per traveller.
Payment instructions the agency writes once: bank transfer details, a PayPal.me link, cash on arrival, or anything else. Shown on the quote, the confirmation and the travel pass. No credentials of any kind are ever asked for or stored.

Getting the trip out of the door

Scheduled departures with real capacity. Seats are held atomically, so simultaneous requests cannot oversell a departure; cancelling releases them.
Guides, drivers and vehicles as records, with an assignment board that refuses to double-book somebody and warns before a licence expires.
An operations board of exceptions — what has not been done yet — and a printable departure manifest.
An outbox for every message the plugin sends: queued, retried, visible when it fails, and re-sendable by hand. A new request no longer carries a voucher or a pass; confirming the booking is what creates them, exactly once.

Guest Pass 2.0

The meeting point as structured facts: landmark, address, map link, coordinates you paste yourself, a photograph, and an honest answer about whether a vehicle can reach it. Nothing calls a geocoding service.
Two things the guest can press: "the pick-up is right" and "I have arrived", both timestamped and rate-limited.
A clear notice when the meeting point moves after they confirmed it.
Staff QR check-in from a scanner, a pasted link or a typed reference. A repeat scan of the same guest on the same day changes nothing, and staff without permission over that booking cannot check anybody in.

Partners, customers and what is working

Referral partners — riads, concierges, drivers — each with a code, a link, and a fixed or percentage commission calculated from the accepted quote. Commissions are tracked as due, approved and paid, with a date, a note, a monthly report and a CSV export. Commission data is never public.
A customer directory keyed by the normalised e-mail address, so one person is one row however they typed it: booking history, preferred language, an internal note and a review-request state. Built from existing bookings on demand.
First-party attribution: the referring host, the five UTM values, a partner code and the landing tour, captured only when a link actually carries them. No third-party analytics script, no identifier that follows anybody. An Insights screen shows the funnel, conversion rates, agreed and received money, outstanding balances, top tours and top partners. wptm_analytics_event is there for a site that wants to connect GA4 or anything else itself.
The WordPress privacy exporter and eraser now cover quotes, payments, the WhatsApp log, attribution and the customer record. Erasing closes every private link the person held.

Upgrading

Schema version 4, applied idempotently under its own option. Five tables are added (outbox, quotes, payments, assignments, customers) and the departures table gains an end time. Nothing existing is renamed, moved or deleted, and no data is destroyed on upgrade, deactivation or uninstall.
New capabilities *_wptm_resources and *_wptm_partners, granted to the roles that already manage bookings and filterable separately.
New options wptm_payments, wptm_whatsapp, wptm_quote_route. New private post types wptm_guide, wptm_driver, wptm_vehicle and wptm_partner, all out of REST, search, archives and sitemaps.
Plugin slug, text domain and every public URL are unchanged.

1.5.0 New: the Digital Guest Travel Pass.

Every confirmed booking gets its own private, mobile-first page at /trip/{reference}?k={key}: pickup time and meeting point with directions, the assigned guide, the vehicle, the itinerary as a timeline, a voucher QR, a payment summary, what to bring, an emergency contact, a WhatsApp button and a weather link. A cancelled booking keeps its pass and says so, without travel actions. Reads the booking's language (Polylang) and mirrors for Arabic.
Security: the reference in the address is for humans; access needs a 32-byte random key that is stored only as an HMAC under the site's AUTH_SALT and compared in constant time. A sealed copy (libsodium or OpenSSL, keyed from SECURE_AUTH_SALT) lets the booking screen re-send the same link; without either library the link is copyable once and can be regenerated. Regenerate and revoke from the booking; a deleted booking forgets its pass. Pending bookings are never served. Every pass answer is noindex, nofollow, no-store, private, DONOTCACHEPAGE.
The voucher QR is drawn by the plugin's own encoder (byte mode, level M, versions 1–10), never by a third-party service.
Tripvance → Settings → Guest Pass: enable, logo, company name, WhatsApp, emergency contact, footer, weather link template, and which sections to show. On each booking: a Guest Pass panel (status, view, copy link, send by e-mail, regenerate, revoke) and a Guest Pass details box (pickup, guide, vehicle, payment, emergency override).
Hooks: wptm_guest_pass_created, wptm_guest_pass_regenerated, wptm_guest_pass_revoked, wptm_guest_pass_view, wptm_guest_pass_data, wptm_guest_pass_sections, wptm_guest_pass_qr_payload, wptm_guest_pass_url, wptm_guest_pass_enabled, wptm_guest_pass_servable_statuses.
New option wptm_guest_pass; new booking meta _wptm_pass_hash, _wptm_pass_sealed, _wptm_pass_status, _wptm_pass_created, _wptm_pass_regenerated, _wptm_pass_details. Nothing existing is renamed or changed; the /trip/ rewrite rule is flushed once on the next wp-admin load.

Earlier releases For releases before 1.4.7, see changelog.txt in the plugin folder.

Tripvance

标签

下载

详情介绍:

安装:

屏幕截图:

常见问题:

更新日志: