Fixed * Refunds were deducted twice, leaving a negative amount paid. Recording a refund wrote the refund as its own entry and marked the original payment refunded, so the same money came off the booking twice over: a 1,000 payment with a 150 refund stored the amount paid as −150 instead of 850, reported more outstanding than the trip costs, and reset the payment status to Pending — indistinguishable from a booking that had never paid. A refund is now a single entry of its own and the original payment keeps its own record, so what you received, what you sent back and what that leaves are each counted once; the booking screen reports all three. A fully refunded booking now reads Refunded rather than Pending, including where you marked a payment refunded by hand. Because the original payment is no longer closed off, a second partial refund against the same payment is possible where it previously was not, and a new check refuses any refund that would send back more than the booking ever received. Bookings whose stored figures are already wrong are recalculated once, automatically, on the first admin page you open after updating; bookings with no refunds are not touched. Each booking’s previous figures are copied to a backup table (yatra_refund_totals_repair_backup_v1) before they change; if a copy cannot be made, that booking is left alone and retried later. * Every booking was counted twice on the customer’s record. A customer with two bookings was shown as having four — in My Account and on the Customers screen alike. The booking count, total spent and traveller totals stored against a customer were added up by hand, and one checkout added to them twice, because both the checkout and the booking service create-or-update the customer record. Nothing ever subtracted either, so cancelling or deleting a booking left the count where it was, and a customer an operator added by hand started life showing one booking they had never made. These figures are now worked out from the bookings themselves whenever a booking is created, changed, cancelled or deleted, so they cannot drift again. Counts already stored wrong are repaired once, automatically, on the first admin page you open after updating. Before rebuilding, the current figures are copied to a backup table (yatra_customers_stats_backup_v1); if that copy cannot be made, the rebuild waits an hour and tries again. * Cancelled trips were counted as upcoming. “Upcoming Trips” in My Account looked only at the travel date, so a trip the customer had cancelled kept being counted and listed as upcoming. A cancelled or refunded booking is no longer upcoming, and the Dashboard and Bookings pages now agree about a trip departing today — one used to count it and the other not. * The payment section of the booking form could not be translated. On a translated site the booking form came out in the site’s language right up to the payment methods, which stayed in English — the one part of the checkout a customer cannot miss. Yatra had written each gateway’s name and description into your saved settings in English when it was installed, and several of those seeded texts did not match the gateway’s own wording, so the checkout mistook them for labels you had typed yourself and used them in place of the translatable ones. Yatra now recognises its own old defaults and lets them translate, without touching your saved settings: a name or description you genuinely customised is still shown exactly as you wrote it, and new installs no longer store these labels at all. The date-format hint in empty date fields (“YYYY-MM-DD”) is translatable too, so it can follow your locale’s convention. * The confirmation page promised travel documents that were never sent. Under What’s Next, Yatra told every customer they would receive “a detailed itinerary and preparation guide within 24-48 hours” — nothing sends one, so customers waited for an email that was not coming and then asked where it was. The pay-later confirmation email said the same. Both now point to where the booking really lives: its details, trip itinerary and any balance due are in My Account, linked using your configured account address. A customer who booked as a guest is told how to reach it instead — create an account with the email address they booked with and the booking appears there — and if your site does not allow registration they are simply asked to keep their confirmation email, rather than being sent to a login page that holds nothing for them. * Booking statuses were missing from the My Account bookings list. Every booking in the list showed a “Pending” badge whatever its real status, the Completed filter found nothing and the Pending filter only matched on payment, because the list did not carry the booking’s status at all (the booking detail page did, which is why the two disagreed). The list now carries it, so badges, filters and counts all read the real status. * Late bookings never got the trip reminder. The daily reminder went only to bookings travelling exactly the configured number of days out, so a booking made or confirmed inside that window — booked one day before a three-day reminder, say — never received one, and neither did a booking whose reminder day WP-Cron missed. Every eligible booking travelling between today and the reminder day now gets its reminder on the next daily run, once, and a late reminder states the real number of days left instead of the configured number. Resend email → Trip reminder on a booking now sends exactly the same email as the automatic one, including the outstanding-balance block, and reports an error instead of “sent” when the Trip reminder email is switched off. * The archive pages’ structured data described an empty list. The trip archive and the destination, activity and trip-category listings printed CollectionPage JSON-LD with a hardcoded empty ItemList ("numberOfItems": 0) even when the page showed cards. The list now holds the cards actually shown — each with its URL, name and position — following filters, sorting and pagination (page 2 continues from position 11), and a page with no results leaves the list out instead of printing it empty. SEO titles, meta descriptions, canonical URLs, robots directives, prev/next links and sitemaps are unchanged. New filter yatra_seo_collection_page_schema to change or remove the list. * The Payments method filter offered the wrong choices. All Methods always listed Credit Card, PayPal, Bank Transfer and Cash, whatever was set up, so most gateways named in the table could not be chosen — on a site using Stripe and Bank Transfer, Stripe could not be filtered at all, and “Bank Transfer” missed bank transfers taken at checkout. The filter now lists the payment methods you have enabled plus any method that already has payments recorded, with the same names the table shows, so a gateway you switched off stays filterable for its past payments. The two spellings of one method (a checkout “bank_transfer” and a hand-entered “Bank Transfer”) appear once and filter together in every language, and the table now shows a hand-entered method under the same translated name as the gateway. * The enquiry page could stop with a fatal error on older setups. On PHP 7.4/8.0 with WordPress 6.0–6.4, reading a trip’s enquiry settings called a PHP 8.1 function WordPress only provides from 6.5. It now works on every supported PHP and WordPress version. * Trip listings made a request back to your own site for every card. To decide whether to show the “Group Discounts” badge, each trip card on a listing page called the site’s REST API over HTTP while the page was being built — up to a dozen extra requests per page, and on hosts that block such loopback requests each one waited for a timeout, making listings very slow. The badge information is now read directly, with the same result and no extra requests. * The trip listing price filter always showed “$”. The price range under Filters was redrawn by the page script with a hard-coded dollar sign, so a store in euros or pounds showed “$9 – $8,999” as soon as the page finished loading or the slider moved. It now uses your currency, symbol position, decimals and separators — exactly as prices are printed elsewhere. * Parts of the admin stayed English on sites translated with a WordPress.org language pack. Screens that load separately from the main admin script — the Trip Consent form editor among them — never received their translations, because WordPress only loads the translation file for the main script. Those screens now get their translations whichever way the site is translated, and plural forms follow the language’s own rules. A few labels in the admin header (the Pro version, the license status badge and the dark-mode button) and the Trip Consent field-type tooltips were not translatable at all; they are now. * A recurring departure’s booking cutoff was only enforced by the calendar. Booking Cutoff (hours before) and the “bookings open N days ahead” limit on a recurring departure correctly removed those dates from the trip calendar, but the booking itself was not checked: a date inside the cutoff matched no departure, was treated as an open-dated trip and the booking went through — from an old link, a page left open, or a request made directly. Such a booking is now refused (“Booking cutoff has passed for this departure.”, or “This departure is not open for booking.” before bookings open). Tip: the cutoff is set in hours, so 20 days is 480. * Admin calendars always started the week on Sunday. The availability calendar and the admin date pickers ignored Settings → General → Week Starts On, which the frontend calendars already honoured. They now start on the configured day, and their weekday names are translatable. * The Google Calendar settings showed a “Sync Departures” switch that did nothing. Nothing ever created an event from it. Departures reach the calendar through One event per departure, which is built from bookings, so the switch is removed and the Sync Bookings description explains this. The setting stays stored, so nothing saved is lost.