Title: Tripvance Author: abourri Published: 9 سپتامبر 2026 Last modified: 12 سپتامبر 2026 --- جستجوی افزونه‌ها ![](https://ps.w.org/tripvance/assets/banner-772x250.png?rev=3689012) ![](https://ps.w.org/tripvance/assets/icon-256x256.png?rev=3688981) # Tripvance توسط [abourri](https://profiles.wordpress.org/abourri/) [دانلود](https://downloads.wordpress.org/plugin/tripvance.1.12.0.zip) * [جزئیات](https://fa.wordpress.org/plugins/tripvance/#description) * [نقد و بررسی‌ها](https://fa.wordpress.org/plugins/tripvance/#reviews) * [نصب](https://fa.wordpress.org/plugins/tripvance/#installation) * [توسعه](https://fa.wordpress.org/plugins/tripvance/#developers) [پشتیبانی](https://wordpress.org/support/plugin/tripvance/) ## توضیحات Tripvance brings tours, activities and travel experiences to WordPress: a Tours post type, tour pages built from real fields, and a booking request form. It is a request and confirmation system: the agency answers each request. There is no payment processing. **Tours** Each tour has a gallery, a short description, highlights, a day by day itinerary, what is included and what is not, a meeting point, and questions and answers. A section with no data is not rendered, so a page never shows an empty heading. Tours are filed under destinations, tour types, departure points, trip lengths and categories, each with its own archive page and filters. **Two kinds of travel business** Tripvance ships two presentations of the same content, chosen under Settings Website experience. Standard is what the plugin has always been: a catalogue with prices, availability and a booking form, and it is the default on every site. Luxury Editorial redraws the same tours, destinations and activities as a travel magazine, for a bespoke travel designer who sells a journey by describing it rather than by pricing it — journey collections, editorial destination pages, a page design with no price card, and a short private enquiry in place of a checkout. Switching between them changes nothing you have written, and there is no second catalogue to keep in step. **Booking requests** The form asks for a date, a party size and how to reach the traveller. By default it behaves as an enquiry system. If you enable seat-capacity enforcement, seats are held atomically against the departure while a request is open, so two simultaneous requests cannot both take the last seat. Requests are managed from a booking screen with a status workflow, internal notes and an operations dashboard. **Presentation** Tour cards can carry a strip of gallery thumbnails along the foot of their picture: pointing at one, or tapping it, shows that photo in the card, so a visitor looks through a tour without opening it (Settings > Tour listings). Eleven tour page designs, chosen per tour or site wide, on one shared foundation: a sticky section navigation, a booking ticket beside the price, a route at a glance, a day by day (or step by step) itinerary, group rates, questions and answers, and reviews. The plugin inherits the theme’s typography and loads no fonts of its own. Listing pages with filters, sorting and cards; a Tours block and a `[wptm_tours]` shortcode for a grid of tours anywhere, and `[wptm_activities]` for a grid of activities— each activity can carry its own price and take booking requests directly through the same request system as a tour; a homepage template assembled from your tours, destinations, activities and trust details; and a car hire template for the driving side of the business — the fleet, the services, the routes you cover and the prices you quote. **Multilingual** Tripvance uses the WordPress translation system throughout and is ready for community language packs from translate.wordpress.org. It also includes built-in French, Spanish and Arabic front-end fallbacks, with right-to-left layouts for Arabic. Polylang is supported properly, not nominally. Tours, activities and every taxonomy the plugin owns are registered as translatable. Tours, terms and the pages the plugin generates are given their language and linked to their translations, so a language switcher lands on the right page. A generated page is written in its own language, not in the language of whoever pressed the button. Booking requests record the language the traveller was reading, and the confirmation, the voucher and the reminder are all written in it. Wording you type yourself — the homepage, the car-hire page, the default inclusions — appears under Languages > String translations so it can differ per language. Addresses can be translated too, and are not by default. Switch on “Addresses per language” in the settings and a French page becomes /fr/circuits/ rather than /fr/ tours/, with the destination, category, departure and trip length sections following it; the words come from the same translation catalogue. The addresses you already have keep working and redirect to the new ones. Leave it off and no address on the site changes, whatever language packs are installed. A site that generated its pages before adding a language can put them right from the settings screen: each page’s title, starting wording and address go back into its own language, a page you have edited is left alone, and the previous address redirects. An optional language switcher goes into the theme’s own menus — desktop header, mobile menu, footer, or a shortcode wherever you like — and each language links to the translation of the page the visitor is on: a French reader on an English tour lands on the French tour. Polylang decides which page that is and keeps printing the hreflang tags; Tripvance only draws the control, in the menu’s own typography, with no flags, no external assets and no second translation system. Without Polylang the plugin runs unchanged. **Search engines** Tripvance prints no canonical tag, meta description or Open Graph markup, and no schema on tour pages. Those belong to an SEO plugin, and two sources for one signal is worse than one. When the optional Rank Math rating integration is enabled, Tripvance can enrich Rank Math’s existing tour schema with genuine approved review data. The homepage is the one exception, and it can be switched off in Tripvance > Site pages > Homepage. An SEO plugin can only describe what it can read, and the homepage is assembled by Tripvance after that plugin has already decided what the page is: the questions and answers, the licence number, the featured tours and the site search are all on the page and none of them reach the graph. So Tripvance describes them itself, in the language each visitor is reading — inLanguage, this language’s tour links, this language’s site root — and describes nothing the page does not show. It also emits clean semantic markup, keeps taxonomy archives crawlable, marks empty ones as noindex, and keeps them out of the sitemap. **Import** Existing WooCommerce products can be imported as tours, with a dry run first that reports exactly what would happen and creates nothing. ### Privacy Booking requests and operational records are stored in the site’s database. These can include names, email and WhatsApp/telephone numbers, country, travel dates, party sizes, pickup details, messages, quotes and records of payments received outside the site. Notifications use `wp_mail()` and the mail provider configured by the site owner. Tripvance sends no telemetry to its developer and loads no remote fonts. WordPress personal-data export and erasure tools are supported for bookings matched by email, including bookings in the trash. Erasure removes identifying booking fields, campaign attribution, email queue/history and free-text history notes, clears linked reservation emails and pickup details, and revokes private links. Non-identifying booking, quote and payment records are retained. For requests without an email address, the operator must identify the relevant records manually. Backups and mail already delivered by the site’s mail provider are outside this eraser. Optional first-party campaign attribution uses the `wptm_attr` cookie for up to 30 days. It stores UTM values, referral code, referring host (not the full referring URL), first tour visited and timestamp. It is read or written only when the site’s consent integration allows it; without consent it is disabled and an existing cookie is expired on the next uncached page request. Booking totals and manually entered attribution remain available. The WordPress Consent API is supported when a consent manager configures opt-in mode. Other integrations can supply the visitor’s consent through the `wptm_attribution_consent` filter. Do not return true globally as a substitute for visitor consent. Tripvance does not provide a cookie banner. Anti-abuse counters use salted hashes of the requesting IP address with expiring transients. The raw IP is not stored in those counters. Private Guest Pass, quote and voucher links act as access keys and should be shared only with the intended traveller. ### External services No external service is required for the core booking workflow. Site owners choose the optional links, media and mail service they use and should reflect them in their privacy notice. * WhatsApp: contact buttons open `wa.me` 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 . * YouTube and Vimeo: an operator-supplied video URL can be embedded through WordPress oEmbed; WordPress may request embed metadata and the visitor’s browser connects to the video host when displayed. In the Luxury Editorial experience, a YouTube address pasted into the Video field of the hero or the full-bleed story is embedded directly from www.youtube-nocookie.com and plays on its own, silently, as the background of that one section; nothing is requested from any video host on a site that has not supplied such an address, no script is loaded from a third party at any point, and the embed is never created for a visitor whose browser asks for reduced motion or reports a slow or metered connection. YouTube terms: https://www.youtube.com/t/terms ; Google privacy: https://policies.google.com/ privacy ; Vimeo terms: https://vimeo.com/terms ; Vimeo privacy: https://vimeo. com/privacy . * Google Maps and Search: optional meeting-point and weather links open after a click and include the selected place, coordinates or weather query. Terms: https:// policies.google.com/terms ; Privacy: https://policies.google.com/privacy . * External media: if an operator enters a remote image or direct video URL, the browser requests that host when the media is displayed. Use the WordPress media library to serve these assets from the site itself. * External payment links: an operator may provide a PayPal or another payment link. The link opens its provider after a click; Tripvance does not process the payment or receive card details. PayPal terms: https://www.paypal.com/legalhub/useragreement- full ; Privacy: https://www.paypal.com/legalhub/privacy-full . ## عکس‌های صفحه [⌊A tour page: gallery, rating, section navigation and the booking ticket.⌉⌊A tour page: gallery, rating, section navigation and the booking ticket.⌉[ A tour page: gallery, rating, section navigation and the booking ticket. [⌊The booking ticket, with the two-step request form.⌉⌊The booking ticket, with the two-step request form.⌉[ The booking ticket, with the two-step request form. [⌊The listing page with filters, sorting and tour cards.⌉⌊The listing page with filters, sorting and tour cards.⌉[ The listing page with filters, sorting and tour cards. [⌊The route at a glance and the itinerary.⌉⌊The route at a glance and the itinerary .⌉[ The route at a glance and the itinerary. [⌊The bookings dashboard in the admin.⌉⌊The bookings dashboard in the admin.⌉[ The bookings dashboard in the admin. [[ [[ ## بلوک‌ها این افزونه 1 بلوک ارائه می‌دهد. * Tours Tour cards from your catalogue, as a grid or as the Moroccan Editorial Carousel, filtered by destination, type, category, duration or departure. ## نصب 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. ## سوالات متداول ### Is there a setup guide? Yes. After activation a dismissible welcome offers a step-by-step guide (Tripvance Settings Setup guide): tours, homepage and its preset, tour design, booking. Every step reads your site as it is and only offers what is missing; nothing is created or changed without a button pressed for it. The guide also offers demo content — sample tours, activities and destinations, every item marked as demo — with a one- click removal that never touches your own content. The guide can be restarted from Tripvance Settings. ### Is there a homepage? Yes. Tripvance Site pages Homepage creates a page on the “Tripvance homepage” template and fills it from what the site already has. Its hero can be a classic image cover, a muted looping video with accessible playback and optional sound controls, a split featured-tour spotlight, layered floating image stories, or an animated travel-colour mesh. The same buttons, optional reassurance points and five tour- search designs adapt to every hero; search can be hidden entirely. The rest includes featured tours, destinations and tour types with their counts, a signature tour, activities, trust, “why choose us”, articles and a final call to action. Sections can be switched off and reordered; a section with nothing to show is not printed. Setting the page as the site’s front page is a separate, explicit button. ### Is there a car hire page? Yes. Tours Car hire creates a page on the “Tripvance car hire page” template, built the same way as the homepage: sections you tick and order, a preset to arrange them, a preview before anything goes live. It holds a hero, a fleet with a filter by kind of vehicle, the services a driver is hired for, a table of routes with journey times and prices, your destinations and tours, the booking steps, trust details, a gallery, testimonials and questions. Only the vehicle’s name is required; a cell left empty prints nothing and a section with nothing in it is not printed at all. Publishing the page is a separate, explicit button, and it is a normal page, so you add it to your menu yourself. ### How do people ask for a quote on the car hire page? Through the form plugin you already use. Paste its shortcode — Contact Form 7, WPForms, Forminator, whichever it is — into the Request form group on Tours Car hire, and the form is printed in its own section, styled to match the page. Tripvance does not add a second enquiry system for cars: your form plugin already holds the fields, the address the mail goes to, the spam protection and the export, and duplicating that would only give you two places to check. Leave the shortcode empty and the section is not printed at all. The section answers to `#wptm-cars-request`, so a hero or call-to-action button can scroll straight to it. ### Does it create pages or content when I activate it? No. Activation only registers the post types and prepares the database. A notice then offers a starter kit, and nothing is created until you press the button. The starter kit’s sample destinations are Moroccan examples; rename or delete any of them. ### How do I get review stars in Google search results? Turn on reviews under Tripvance Settings and let travellers leave rated reviews. Tripvance does not print a separate schema graph; with Rank Math active it can add the average rating and latest approved reviews to the schema Rank Math already builds for the tour. To make a tour eligible for product review rich results, set Rank Math Titles & Meta Post Types Tours Schema Type to Product. Google ultimately decides whether a rich result is shown, and nothing is added until real approved reviews exist. ### Is there an activities page? Optionally. Activities are pages of their own from the start; the listing at `/activities/` and a page per activity type are switched on under Tripvance Settings (activity archive). With it on, the plugin draws both — title, description, a row of type links, the activity cards with their prices, pagination — and a theme can replace either 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. ### 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. ### Is Advanced Custom Fields required? No. The plugin has its own fields and works without it. If ACF is installed the same fields are shown through ACF instead. The free version is enough; no premium field type is used. ### Will it conflict with my SEO plugin? It should not. The plugin outputs no canonical, meta description or Open Graph markup, and no schema on tour pages, leaving those to Rank Math, Yoast or whichever you use. The homepage graph is the single exception; if your SEO plugin already publishes the same thing, untick it in Tripvance > Site pages > Homepage. ### Does it work with Polylang? Yes, with the free version. Tours, activities, taxonomy terms and generated pages are assigned a language and linked to their translations, and each generated page is written in its own language. The homepage and the car hire page are created in every language at once and linked, so the language switcher and the hreflang tags are right from the start. The homepage’s own wording gets a language tab per language in Tripvance > Site pages > Homepage: the same form, the source text above every box, and a box left empty falls back to the source language rather than leaving a hole. Booking mails, vouchers and reminders answer in the language the traveller booked in. Your other wording is still exposed in Languages > String translations. A language switcher can be switched on in Settings and printed in the theme’s menus or through `[wptm_language_switcher]`; each language links to the real translation of the current page and never to a guessed address. Without Polylang nothing changes. ### Can two people book the last seat at once? If seat-capacity enforcement is enabled, no. Tripvance obtains a departure lock and performs the capacity test as part of the reservation write, so only one request can take the final seat. Capacity enforcement is off by default because many agencies use the form as an enquiry system. ## نقد و بررسی‌ها نقد و بررسی‌ای برای این افزونه یافت نشد. ## توسعه دهندگان و همکاران “Tripvance” نرم افزار متن باز است. افراد زیر در این افزونه مشارکت کرده‌اند. مشارکت کنندگان * [ abourri ](https://profiles.wordpress.org/abourri/) [ترجمه “Tripvance” به زبان شما.](https://translate.wordpress.org/projects/wp-plugins/tripvance) ### علاقه‌ مند به توسعه هستید؟ [کد را مرور کنید](https://plugins.trac.wordpress.org/browser/tripvance/)، [مخزن SVN](https://plugins.svn.wordpress.org/tripvance/) را بررسی کنید، یا از طریق [RSS](https://plugins.trac.wordpress.org/log/tripvance/?limit=100&mode=stop_on_copy&format=rss) در [گزارش توسعه](https://plugins.trac.wordpress.org/log/tripvance/) مشترک شوید. ## گزارش تغییرات #### 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 … ## اطلاعات * نگارش **1.12.0** * آخرین به‌روزرسانی **4 ساعت پیش** * نصب‌های فعال **کمتر از 10** * نگارش وردپرس ** 6.3 یا بالاتر ** * آزمایش‌شده تا **7.1** * نگارش PHP ** 7.4 یا بالاتر ** * زبان * [English (US)](https://wordpress.org/plugins/tripvance/) * برچسب * [activities](https://fa.wordpress.org/plugins/tags/activities/)[booking](https://fa.wordpress.org/plugins/tags/booking/) [itinerary](https://fa.wordpress.org/plugins/tags/itinerary/)[Tours](https://fa.wordpress.org/plugins/tags/tours/) [travel](https://fa.wordpress.org/plugins/tags/travel/) * [نمایش پیشرفته](https://fa.wordpress.org/plugins/tripvance/advanced/) ## امتیازها هنوز هیچ نقدی ارسال نشده است. [بررسی شما](https://wordpress.org/support/plugin/tripvance/reviews/#new-post) [مشاهدهٔ همهٔ بررسی‌ها](https://wordpress.org/support/plugin/tripvance/reviews/) ## مشارکت کنندگان * [ abourri ](https://profiles.wordpress.org/abourri/) ## پشتیبانی چیزی برای گفتن دارید؟ نیاز به کمک دارید؟ [مشاهده انجمن پشتیبانی](https://wordpress.org/support/plugin/tripvance/)