Solidres for Joomla 4.7.0

Your guests' emails have a new design, and you word them yourself: Solidres → Emails gives each email of each property a subject and a message per language, with the booking's values, a preview on your latest booking and a test sent to yourself, and no Super User needed. The PHP email layouts are removed in this release, so an email changed with a template override or a language override goes back to the standard design and text when you update: read Before you upgrade first.

The reservation screens are rebuilt too. The reservations list has quick filters, status badges and check-in and check-out ranges, and opens fast however many rows it shows; a booking has a summary above its tabs and figures you change from the keyboard. Your guests see their bookings under Upcoming, Past and Cancelled, and each booking reads like a receipt, with what is still due first, the voucher and invoice to download and the messages you left them, with their files. See Managing reservations and How to configure front-end customer dashboard.

Your site can ask for cookie consent by itself: Solidres Options → Cookie consent shows a banner of the site's own whenever the site has something to ask about, in your guests' language and in your template's colours, and runs Conversion tracking's tags, or any script you mark, only after the guest accepts. It is off on an updated site until you turn it on. See Cookie consent on your site.

Emails

• Emails screen: Solidres → Emails, beside Statuses, and the link Edit the wording of these emails in the Booking emails section of the property's Booking tab. Each email the guest receives has a subject and a message, the paragraphs above the booking's details, per property and per language. Insert a value adds the guest's name, the reservation code, the dates, the amounts and the rest; Preview shows the email with the property's latest reservation, or a sample one; Send me a test sends it to you; Reset to standard text goes back to the standard wording, translated into every language Solidres comes in. Anyone allowed to edit properties can use it. See Wording the emails your guests receive.
• A new design: every email about a booking, the property's notification included, has one design: a single column that reads well on a phone, the property's logo or its name at the top, the primary colour of the default site template when it has one (Lumina's, for example), dark mode in the mail apps that offer it, right to left in Arabic, Hebrew and Persian, and the property's address, phone, email and social links at the foot. Lines with nothing to show, such as extras, a coupon or a deposit of zero, are left out.
• The full template: the Super User sees Edit the full template under each email, which opens the email's Twig template for that property in a code editor, with a preview, Reset to shipped template and Restore previous, and a notice listing what changed when an update changes the shipped template. A site template can carry its own email templates in html/com_solidres/emails/, listed and checked on the System page like any override.
• Checked when saved: a subject, message or template that cannot be sent, such as a value whose braces are not closed, is refused when you save it, with the reason and the line. An edited template that still fails when an email is sent falls back to the shipped template, so the guest gets the email.
• Status texts: the Email text of a status (Solidres → Statuses) has the same editor and values. Texts written with the older names, such as {res_code}, keep working as they are.
• Payment reminder: Email subject and Email body of the reminder, in Solidres Options → Invoice, have the same values and checks. Invoice 2.2.0 fills them in, in the guest's language.
• The guest's language: a guest's email is written in the language they booked in, as before. When that language is no longer installed, it is written in the site's default language; it used to take the language of whoever sent it, such as the staff member who confirmed the booking. The property's emails are in the site's default language.
• Guest details: a booking made before the Custom Fields add-on was installed, or received from a channel, lists the guest's details from the booking. Its email used to list the labels with nothing beside them.
• Language overrides of a property's category now reach its emails.
• Invoices sent with the confirmation: with Auto send invoice on, a booking without an invoice no longer gets an empty invoice record, and leaving Apply to payment methods empty no longer stops the email.

Removed

• Extension - Solidres: removed. Everything it did is now part of Solidres, and updating uninstalls it. The property's house rules, facilities and social links, and the room type's conditions and facilities, are fields of the property and room type forms, on the same tabs and with everything entered in them kept. The room type's Custom fields tab is now called Room details. The plugin's Required / Optional / Disabled settings are in Solidres Options, on a new Form fields tab, and updating carries each site's choices over. The plugin is no longer listed in System → Plugins nor on the System page.
• Status emails without the plugin: Solidres now sends the email on a change of a reservation's status itself, as Email when changing reservation state in Solidres Options → Reservation says. A site that disabled Extension - Solidres to stop these emails gets them again after updating: turn that setting off instead.
• Legacy date picker: removed, as announced with 4.5.0. The range picker is the only date picker, and a site still set to the Legacy one switches to it when you update. Date picker engine and Months in date picker leave Solidres Options, and the property and apartment pages no longer load a jQuery UI translation file on every visit.
• jQuery UI: no longer loaded, on any Solidres page of the site or the administrator, which saves about 150 KB a page. Fields that list several records, such as a property's extras, reorder by drag and drop with Joomla's own script, and gain Move Up and Move Down buttons for the keyboard. The update deletes the jQuery UI files.

Reservations list

• Quick filters: above the list, All, Arrivals today, Departures today and In-house, each with its count. They show the same bookings as the dashboard's tiles of the same name, and the one in use is marked.
• Check-in and check-out ranges: the four date filters become two ranges, Check-in from – to and Check-out from – to, each with its two calendars side by side and read as one by screen readers. In-house on stays. A date filter now waits for a day to be picked: moving the calendar to another month no longer reloads the list.
• Status badges: the status and the payment status are badges, and the reservation code takes its status colour darkened enough to read, on a light page and a dark one.
• Faster: the list reads the payment references and the custom field columns once per page instead of once per row. A list of 100 bookings with three custom field columns ran 241 database queries and now runs 46, as many as a list of 20. The custom field columns need Custom Fields 2.0.3 for this; with 2.0.2 they are read row by row as before.
• Easier to use: payment references open from under the payment method; icon links and the approval and check-in marks have text for screen readers; a filter that matches nothing says so; a refused status change shows the reason on the page instead of in a pop-up.
• After an export: changing a filter after Export filters the list. It used to download the file again and leave the list as it was. The tourist tax report works the same way now.

A reservation

• Summary: above the tabs, the property, the dates, the status and the payment status, the total, what was paid and the balance due, and whether the booking is approved and checked in.
• Changing a figure from the keyboard: a status, an amount or another figure you can change in place is a button with a pencil. Tab to it and press Enter or Space; Escape closes the form, and the focus goes back to the figure. Screen readers read it as Change Total paid. The form opens beside the figure and follows the page's light or dark theme.
• Totals that follow: changing what was paid, the discount, the fee or the deposit updates the balance due and the summary. After a change to what was paid, the balance due used to stay as it was until the page was reloaded. The form for what was paid says that it adds no payment to the Payment history tab.
• Headings: the screen's blocks and rooms are headings at the right levels, so a screen reader can move between them. They look as before.

Your guests' bookings

• Upcoming, Past and Cancelled: the customer dashboard lists a guest's bookings under three tabs, with a search by booking code that looks in all three and, for a guest who has booked more than one property, a choice of property. Each booking is a card with the property's photo and address, the check-in and check-out dates, the nights, the total and the balance due. A booking you have still to approve is listed as Awaiting approval; it used to be left out, with only a notice counting it.
• A booking that reads like a receipt: Manage booking and the booking tracking page show the property, the dates and the status first, then the price: the total, what was paid, the balance due and any tourist tax paid at the property, with Price details folded underneath. The rooms, the guest's details and the property's messages follow. On a wide screen the price and the guest's actions sit beside the stay.
• Cancel, with a second step: cancelling asks Yes, cancel this reservation before it cancels. The last day to cancel or amend shows under its button, in the guest's language; it used to be in English.
• Voucher and invoice: Manage booking offers Download the voucher and, with Invoice on and an invoice issued, Download the invoice.
• Messages from the property: notes you mark as shown to the guest are listed with their date and their files, which the guest downloads from the booking. A file can be downloaded only by the guest the booking belongs to; the tracking page lists the file names without links. The note no longer shows the user name of the staff member who wrote it.
• The guest's details: only the details the guest gave are listed, and never their IP address.
• Totals on Manage booking: the grand total counts the payment method's surcharge or discount, a tourist tax paid at the property and the tours booked with the stay, without PHP warnings. In the administrator, the balance due no longer counts a tourist tax paid at the property as still owed.

Booking form

• Booking conditions and privacy policy: the line the guest agrees to at checkout links the booking conditions and the privacy policy only when Solidres Options names an article or an address for them. With nothing set, both links went to a page that does not exist, and with the address format and no addresses the line read only I agree with. The guest still ticks the box, which names both without a link.
• Thank-you message: the message on the last step of the booking form is sized as an introduction instead of at the page's full heading size.

Reservations

• Confirmation date: recorded for every confirmation, with the correct hour. It was recorded only when status emails were on and the confirmed status was among those that send one, and with a 12-hour clock, so a confirmation at 14:30 was stored as 02:30. Dates recorded before are not changed.
• Status email after add-ons: the email on a change of status is sent after add-ons have handled the change. A stay cancelled with tours booked with it now lists the tours as cancelled, which Experience does as the stay is cancelled; the email used to go out first.
• Dashboard tiles: a tile on the dashboard opens the list with only its own filter. Since 4.5.0 the list could stay narrowed by a filter used earlier, such as a property, which the filter bar no longer showed, and miss bookings. A date filter emptied with the calendar's Clear no longer counts as a filter in use.
• Sorting: the list sorts by property, length of stay, total and channel order ID. These headers could be clicked but did not change the order.
• Reserved rooms: the list shows the rooms each booking holds, as the reservation screen does. It read a copy of the room names saved with the booking, and a booking saved without that copy showed No assigned rooms although its room was booked. The sample bookings had no copy, and neither had any booking made while the Reservation code format made codes longer than 32 characters; Reservation Code 1.0.2 keeps such bookings on their standard code.
• The day of a date filter: In-house on shows and filters by the day you pick. West of UTC it showed the day before, and filtered by it.
• Custom fields of the guest: the reservation screen splits the guest's custom fields evenly between its two columns. Four fields showed as three and one, and a single field added an empty row and PHP warnings.
• Add-on hints: the Turn it on link beside an add-on that is not enabled, on the property screen, opens that add-on's plugin, ready to enable. Since 4.6.0 it opened the list of all plugins instead.

Customers

• Export to CSV: the Customers list exports the customers it holds, every page under its filters, search and order, or only the rows you tick. A row has the customer's code, group, names, email, phones, address, company, VAT number, username, registration and last visit dates, booking counts and whether the account is blocked, then their other profile fields when Custom Fields is on. A value a spreadsheet would run as a formula is written as text.
• Customer group filter: a list of the groups, as on the customer form. It was a text box that took a group's id.
• Search with a filter: a search no longer lists customers outside the filter in use.

Rate plans

• Monthly rate plan dates: saving a monthly rate plan fits its prices to its Valid from and Valid to, one price per month. Months the dates add appear empty, ready to price, and months outside them are removed. Extending a monthly rate plan used to add no months, so a stay in them was priced at nothing and the rate plan was not offered. A monthly rate plan whose editor shows a single month labelled 1970-01 gets its months the next time you save it, and its prices then need entering again.
• Months of a rate plan: the months of a new monthly or weekly rate plan include every month its dates touch. Dates from 31 October to 1 March used to leave out November and March.

Wishlist

• Removing a property: on the wishlist page, removing a property takes it off the page, with the loading icon shown while it is removed. The page used to reload after every removal, and the loading icon never showed.
• Remove button for everyone: on the wishlist page, the button that removes a property or a tour can be reached with the keyboard and shows when it has focus, and it is always shown on touch screens, which have no hover. It used to appear only under a mouse pointer. It is announced to screen readers as Remove followed by the name, in all 25 languages.
• No jQuery: the wishlist's script works without jQuery. A property name in the wishlist's popup is shown as text.

Solidres news

• News in the Solidres menu: Solidres → News lists the latest posts of the Solidres blog, on releases, new features and security fixes, each with its date, its first lines and a link to the full post. The menu shows how many posts you have not read yet; opening News clears the count. The posts are in English.
• Who sees it: those allowed to change Solidres Options. To hide it, turn off Show Solidres news in Solidres Options → Subscription & updates.
• What it sends: the posts are read from solidres.com about twice a day and kept on your site in between. The request sends nothing about your site, and when solidres.com cannot be reached, the screen says so and nothing else waits for it.

Security

• Guest details on the reservation screen: a guest could put script in their booking details that ran when staff opened the booking, and so act as that staff member, an administrator included. The customer details, names, notes and payment references a guest entered now show as text on the reservation screen and the reservations and customers lists. The guest's custom field values need Custom Fields 2.0.3 as well, and the tours booked with a stay Experience 2.5.0.
• My Reservations: any registered user could list other customers' bookings on the customer dashboard, and read the database through it. It now lists only the signed-in customer's own bookings, whatever the request says.
• Searching the reservations list: a search by code could list bookings outside the searcher's own. On the customer dashboard, a signed-in guest could be shown other guests' bookings that came from a channel; a Hub partner's search could match bookings of other partners' properties by their channel order ID; and a REST API caller limited to some properties could get other properties' bookings whose code matched. The search now stays within the bookings each of them may see. This was present since at least Solidres 4.0.2. We recommend updating.
• Booking vouchers: anyone could download any booking's voucher, with the guest's name, contact details, dates and prices. On the site, a voucher now downloads only for the booking's guest or a partner of its property, with Invoice 2.0.3 or later, and its file name keeps only safe characters.
• Payment records: on the site, any signed-in user could add, change or delete a booking's payment records, and so change what it shows as paid. Only a partner or staff member of the booking's property can now, and saving a record checks the booking it is stored against, not only the one posted.
• Card security codes: the Offline gateway's card form asked for the card's security code, which was stored with the booking and emailed to you. The form no longer asks for it, and the Customer payment tab shows only the card digits and expiry the gateway keeps. Update the Offline gateway to 1.0.2 as well: it no longer keeps or emails the code, and its update removes the codes already stored.
• The tracking page: a crafted link to the booking tracking page could run script in the browser of whoever opened it. The code and email the page shows back are now text.
• The System page: a back-office user without Solidres' Configure permission could switch any extension on or off, sign-in plugins included, read files through the log viewer and turn off every template's overrides. These tools now need Configure, and are hidden from users without it. The switches act only on the extensions the page lists.
• Hub partners' lists: the database could be read through the charge type filter of the partner's extras list, and a partner could list other partners' properties by changing the request. The property list now holds only the partner's own properties, and the room type filter of the partner's screens only their own room types.
• Actions taken on your behalf: the check-in, check-out and reset buttons, the figures changed in place on the reservation screen and the guest's Cancel on Manage booking did not check that the request came from your own site, so a page elsewhere could make a signed-in user run them. They now carry the form token. Update the Hub to 2.5.0 with Solidres 4.7.0: an older Hub's check-in buttons are refused.
• Guest text on the site: the guest's own details show as text on the tracking page, My Reservations, the booking form's last step and the booking forms.
• Reservations export: the export now checks that the request came from your own site, and a guest's name, address or note that starts with =, +, - or @ is written after an apostrophe, so a spreadsheet does not run it as a formula.
• Note attachments: pages, scripts, SVG, XML and JavaScript files are never attached to a note, whatever Solidres Options allow. The update gives attachments saved before 4.6.0 random names, so reload any reservation screen left open across it.
• Booking codes: a new reservation code is random, in the same eight-character format. It was made from the time of booking, so knowing that time narrowed it to about a million values. The confirmation page and the payment status check compare the code exactly; a code that was close but not equal could open them.
• Payment cancel links: the link a gateway sends a guest back to after cancelling a payment, which cancels a booking not yet paid, could be forged by anyone who knew the booking's code. The cancel and return links are now signed by your site. A guest who cancels at the gateway across the update lands on the home page, and the booking stays pending.
• Editing a booking from the site: an account allowed to edit could open any booking in the editing form on the site, which locked it, though not save it. The site now opens no booking that way: guests change theirs from Manage booking, partners from the Hub.

Cookie consent

• A banner of the site's own: Show the cookie banner in Solidres Options → Cookie consent shows it until the visitor chooses: Accept all, Reject all, or Settings to choose by category (necessary, analytics, marketing, and preferences if you offer it). It asks only when something waits for consent: on the booking pages once Conversion tracking has a tool set up, and on any page that holds back a script or carries a Google tag. A site with nothing to ask shows no banner. The choice is kept in a cookie of your site for the months you set, from 1 to 13. Raising Revision asks every visitor again, saying that the site's use of cookies has changed.
• What waits for consent: Conversion tracking's connectors and custom code, with its Consent handling set to Blocked by my consent tool and its consent tool to Solidres cookie banner (Conversion tracking 1.1.0). Any other script waits too when written as <script type="text/plain" data-category="analytics">, or marketing or preferences. Withdrawing a category reloads the page without its scripts and deletes the cookies of the tools Conversion tracking connects.
• Google Consent Mode: the banner denies Google's four consent signals before any tag runs and updates them from the visitor's choice, before the tags it holds back run.
• Your words and links: the texts are translated into every language Solidres comes in; Your own sentence adds a line of yours under them, and the banner links the privacy policy set on the General tab. A link to #cookie-settings, in a footer menu or an article, opens the visitor's choice again; a page without one shows a small button for it.
• Looks and access: a box in a bottom corner, a bar along the bottom or a box in the middle; Lumina's colours and its light and dark modes, a neutral look on another template; right to left in Arabic, Hebrew and Persian. It is used with the keyboard alone, and each switch is named for screen readers. Search engine crawlers are not shown it. The banner works under a Content Security Policy with nonces.

Solidres Options

• Conversion tracking tab: Solidres Options has a Conversion tracking tab after Integrations. Without the Conversion tracking add-on, it says what the add-on does and how to enable it; with the add-on enabled, it holds the add-on's settings (Conversion tracking 1.1.0).
• Settings kept on save: saving Solidres Options, here or through Joomla's REST API, no longer drops the settings it does not show. The settings of an add-on that is disabled at the time, such as Conversion tracking's, are kept as they were and are back when it is enabled again.
• Site name and meta description: the Website tab sets the site's name and its meta description, which used to need Joomla's Global Configuration and so a Super User. They are written to configuration.php as Global Configuration writes them; when that file cannot be written, nothing is saved and Joomla's message says why.

System page

• Fix schema: checks the database against Solidres' update files and runs again what is missing, as Joomla's own Extensions → Database → Fix does, then lists what still fails. It used to delete the folder of update files and check the database against nothing.
• File integrity: files guests upload through a custom field are no longer reported as new files.
• Servers with opcache preload: Solidres loads its constants on every request. On a server that preloads PHP files, the first page that needed one stopped with Undefined constant.
• New Solidres category: opening a new category no longer logs a PHP warning.

Released alongside

• Conversion tracking 1.1.0: its settings move from the plugin's own options to Solidres Options → Conversion tracking, where an administrator who cannot open Joomla's Plugins screen reaches them too, and the update copies them there. Works with Solidres 4.5.0 and later; with 4.7.0, its settings are kept while it is disabled, and its tags can wait for the site's own cookie banner.
• Invoice 2.2.0: the invoice email and the payment reminder are sent through the new email templates, and the invoice email is worded on the Emails screen. Needs Solidres 4.7.0.
• Feedback 2.2.0: the review request is sent through the new email templates and worded on the Emails screen, with the review link as a button below the message. Needs Solidres 4.7.0.
• Hub 2.5.0: partners get the administrator's reservations list and reservation screen, with the quick filters, the summary, the sections add-ons add and the files attached to notes. Needs Solidres 4.7.0.
• Experience 2.5.0: the tours booked with a stay show on the partner's reservation screen, and as a block of the guest's booking on Manage booking. Needs Solidres 4.7.0.
• Experience Stripe 2.2.0: a payment settles only the tour booking it was made for, and the balance of a tour booking can be paid by card from the tracking page. Use it with Experience 2.5.0.
• Custom Fields 2.0.3: reads the custom field columns of a page of reservations at once, which the faster reservations list uses, and shows every saved value as text.
• Offline 1.0.2: no longer asks for, keeps or emails the card's security code, and its update removes the codes already stored.
• PayPal 2.0.2: no longer writes its access token to the log.
• Rate Plan 1.2.1, Front Desk 1.1.2 and Dashboard 1.1.2: install, disabled, on an older Solidres that still has Complex Tariff or Statistics, so that site can update. Rate Plan and Front Desk keep partners to their own rate plans, bookings and rooms.
• Housekeeping 2.0.4: the partner's list applies its search, filters and sort, its exports work with any property name, and importing and editing rooms checks the form token and the partner.
• iCal 3.1.2: imports only http and https feeds on public addresses.
• Advanced Extra 1.0.4: the available dates of an extra use the range picker's calendar, as the Legacy date picker is gone.
• ResCode 1.0.2: a code too long for the booking, or already in use, no longer leaves the booking without its rooms, and {RANDOM} is random.
• Discount 1.0.5, Limit Booking 2.0.5, ACL 1.0.3 and Flex Search 1.0.4: partners reach their own discounts and booking limits only, the tour bookings list needs the Experience permission, and Flex Search shows signed-in customers their group's prices.

Before you upgrade

• Email layout overrides stop working: Solidres 4.7.0 sends its booking emails from Twig templates and removes the PHP email layouts of components/com_solidres/layouts/emails/. A template override of them, in templates/<template>/html/layouts/com_solidres/emails/, is no longer read: from the first email after the update, the change it made is no longer sent, and the System page lists the file as No longer used. Move a change of wording to the Emails screen, and a change of layout to a copy of the email's Twig template, as Moving an email override shows. If your emails must not change for a day, prepare the new templates on a copy of your site first.
• Email wording changed with Language Overrides: the guest's emails no longer read the language strings of their subject and greeting, such as SR_EMAIL_RESERVATION_COMPLETE or SR_EMAIL_GREETING_TEXT: their wording is on the Emails screen. If your site changed one of them in System → Manage → Language Overrides, the emails go back to the standard text when you update. Write your text on the Emails screen instead: under each email, a note names the overrides your site has of its old strings until the email has your own text. The list of strings is in the documentation. Overrides of the details' labels, such as Grand total, keep working.
• Update Invoice and Feedback with Solidres: Invoice 2.2.0 and Feedback 2.2.0 need Solidres 4.7.0, so install them after it. Until then, Invoice and Feedback send their emails in the old design, Invoice sends a payment reminder written with Insert a value with the values as typed, and the registration card designer of an older Invoice loses its drag and drop, which used jQuery UI.
• Update the Hub, Custom Fields and the Offline gateway with Solidres: under Solidres 4.7.0, a Hub older than 2.5.0 has its check-in and check-out buttons refused. Custom Fields 2.0.3 shows the guest's custom field values as text on the reservation screen, and Offline 1.0.2 removes the card security codes already stored.
• Email overrides of add-ons: overrides of Invoice's new_invoice_notification_customer_html_inliner.php and of Feedback's request_customer_feedback_html_inliner.php stop working with Invoice 2.2.0 and Feedback 2.2.0 the same way. The voucher and invoice PDFs, and the review request of a tour, are still PHP layouts.
• Database: the update adds the tables #__sr_email_templates and #__sr_email_texts, which hold each property's templates and wording.
• Code of your own: code that rendered one of the removed emails.* layouts with LayoutHelper must render the email with Solidres\Mail\GuestEmail instead. An add-on adds an email of its own with TwigPathsRegisterEvent, BeforeEmailRenderEvent and EmailPreviewDataEvent, as Invoice and Feedback do.
• Fields added to the plugin's XML files: a site that added fields of its own to plugins/extension/solidres/fields/reservationasset.xml or roomtype.xml loses them from the forms, as the files go with the plugin. The update names those fields, and keeps what was entered in them: a template override that shows them still does. To have them on the forms again, add them with a small plugin of your own, as How to add custom fields shows.
• Date picker and jQuery UI in your own code: Solidres\HTML\Jquery::datepicker(), datepickerLocalization() and ui() still exist but do nothing, and DatePicker::engine() always answers the range picker. A template override or script of your own that drew the Legacy date picker, or used jQuery UI's drag and drop, sortable or dialog, gets nothing from Solidres any more: make the override again from the new file, or load the library yourself.
• Wishlist requests: the wishlist now adds and removes through index.php?option=com_solidres&task=wishlist.add and wishlist.remove. Code of your own that called option=com_ajax&plugin=solidres&group=extension must use them instead.
• Overrides of the reservation screens: the guest's bookings list (com_solidres/customer/default.php) is rewritten. An override of it made before 4.7.0 still shows, but it lists only the upcoming bookings, with no tabs and no code search, and its status and city filters no longer filter: make it again from the new file. Manage booking (myreservation/edit.php) and the tracking page (tracking/default.php) now draw the booking with the new layout reservation/guest.php; overrides of them keep working but miss the new design. In the administrator, the reservation screen (reservation/edit.php, edit2.php, edit_general.php, edit_customer.php, edit_customer_payment.php, edit_commission_payout.php, edit_room.php, edit_note.php, edit_invoice.php and edit_stream.php, with the new edit_summary.php) and the reservations list (reservations/default.php, whose table moved to the new default_list.php) changed. The layouts reservation/general_details.php, customer_details.php and note.php changed, and reservation/card.php, guest.php, summary.php, rooms.php, extras.php, notes.php, status_badge.php and new_booking.php are new. The System page flags the overrides that need updating.
• Template overrides: com_solidres/wishlist/default_reservation_asset.php and default_experience.php changed. Compare an override of them with the new files in the System page's Template override check list.