The highlight of this release is a new Reports screen. Occupancy, ADR, RevPAR and revenue are worked out night by night, so a stay across a month end counts in both months, and every figure can be charted, compared with the period before and exported to CSV. A site can now also be a booking site beside a website the property already has, and the booking form to paste into that website, which needed the Hub, is free in Solidres. The administrator gets a Solidres entry in Joomla's own menu, a Solidres dashboard, today's arrivals, departures, in-house guests and unread reservations on the home page, and, on a new site, a Getting started checklist. Solidres pages now follow the template's light or dark mode instead of the visitor's device. The release fixes a security issue with bookings made without an account, so we recommend updating. It also announces that the Complex Tariff and Statistics plugins will be removed in Solidres 4.6.0, and that support for Falang is going away in favour of Speedy Translate, whose Lite edition is free.

Highlight: Reports

• Its own screen: open it from the Solidres menu → Reservations → Reports. Pick a report, a property or all of them, and a period: this or last month, quarter or year, the last or next 30 or 90 days, or a custom range. Rows can be grouped by day, week or month.
• Three reports in core:
  • Performance: occupancy, ADR, RevPAR, room revenue and room nights over time.
  • Revenue: room revenue, extras, fees, booking discounts and total revenue for each period, with the tax, tourist tax and discounts given beside them.
  • Booking sources: bookings, room nights, revenue and its share, ADR and average stay for each source, the most revenue first.
• Counted by the night: each night of a stay is counted in the period it falls in, with its share of the booking's money. Cancelled and trashed bookings never count, and each currency gets its own figures.
• Read at a glance: headline figures show their change against the period before, above a chart and a sortable table with totals. Every report exports to CSV and prints on light paper. The screen follows the administrator template's light or dark mode.
• Who can see it: Reports has its own permission. With the ACL plugin (1.0.2) enabled, only the groups you grant it in Solidres Options → Permissions see the menu item and the screen.
• Hub partners: partners get the same reports on the site for the properties they own or staff, from a Reports item in the partner navigation. This needs Hub 2.4.0.
• More with the Reports plugin: the new Reports plugin (1.0.0) adds Compare with (previous period or the same period last year), Break down by (period, property or room type), cancellation rate and lead time on Booking sources, and six more reports: Production, Cancellations, Payments, Balances due, Guests, and Rate plans and coupons.
• What bookings now record: each booked room keeps the price of each of its nights, which a booking used to throw away once priced, and a booking records when it was cancelled. Reports use both. Bookings made before 4.5.0 have neither: their room price is spread evenly over the stay, and the report says how much of it that covers.

Booking site and booking form

• Two site shapes: Solidres Options → Website sets what the public site is. Website, the default, is the site you have today. Booking site is for a property that already has a website elsewhere, on WordPress, Wix or an agency's hands: this site becomes its booking pages, on an address of their own such as book.your-hotel.com, and the property page links back to the Main website you enter. Rooms, extras, checkout and payment are the same in both shapes, and you can switch at any time: nothing is installed or removed.
• With Lumina: on a booking site the header shows your logo, linked to your main website, and a Back to link instead of the menu; the hero and the footer columns are not shown and the booking bar stays pinned. The modules stay published, so switching back to Website brings them back. Other templates get the Back to link above the property page.
• Out of search results: a booking site asks search engines not to list its pages (noindex, follow), so your main website stays the result for your property's name. An option lets search engines list it, and a Robots value set on a menu item or in Global Configuration still comes first.
• The booking form, free: the property form's Embed form tab, which needed the Hub, is now part of Solidres. It gives a code to paste into a page of your own website: the search bar of the Check availability module, with the dates, a guests and rooms picker that asks each child's age, and a search button that opens this site's property page with the search made. It is a row on a wide page and a card in a narrow column, and without colours of its own it follows the website's light or dark mode. A property still on the old default button colours, grey text on light grey that was hard to read, gets the new ones when you update. A new Mode setting gives a single Book now button instead, and a second code gives the same form as plain HTML, without a script, for page builders that remove scripts or to style it yourself. The form no longer uses eval, so a website whose Content Security Policy forbids it shows the form too, and its labels are tied to their fields for screen readers. It replaces the Hub's version: a code pasted from the Hub stops working with Hub 2.4.0 and has to be replaced with the new one (see Before you upgrade).
• Booking form screen: the Solidres menu → System → Booking form shows a property's two codes, the booking page's address for a button your website builder makes itself, a preview, and what to do on WordPress, Wix and Squarespace. Wix and the WordPress.com plans below Business cannot open the booking site from pasted code, so there the screen says to link a button of the builder's own to that address.
• Getting started on a booking site: the Review your website pages step becomes Put the booking form on your website, which ticks when the first search arrives through the form.
• Show only reservation form: a property page that hides its name and description with this option keeps a heading for screen readers and search engines.

Booking & search

• Coupons on apartment pages: a property in apartment mode shows the coupon field above Reserve, and an applied coupon re-prices the stay on the page, keeping the dates the guest chose. A guest booking an apartment had nowhere to enter a code. Pressing Enter in the field checks the code instead of sending the form, an unknown code gets a clear answer instead of an error, and the result is announced to screen readers.
• Rate plans without people limits: a rate plan limited per room type whose adult and child limits are left empty is offered again to searches that give a number of guests. It was offered only to searches that gave none. Rate plans limited per rate plan read their limits as before.
• Check availability module: on a site without a published default property, the module shows a notice in place of its form. It used to break the page.
• Dark mode: Solidres follows the template's light or dark mode, and Joomla's theme switch, instead of the visitor's device. On a template with no dark mode, such as Cassiopeia, Solidres panels, calendars and forms used to turn dark on a light page whenever the device was set to dark. The date pickers take their theme from the page too, and printing stays light. The Hub, Experience, Front Desk, Dashboard, Inventory and Nano Gallery versions released alongside follow the same rule.

Administration

• Solidres in Joomla's menu: Solidres has its own entry in the administrator menu, right below Home Dashboard, with the same groups as before. It replaces the menu that sat beside each Solidres list, so lists use the full width, and Joomla's sidebar is no longer collapsed on Solidres pages. On a phone the menu is behind Joomla's menu button. The unread count stays on the Reservations link.
• Solidres dashboard: the dashboard icon next to Solidres in the menu opens a dashboard with a card for each menu group, following the features you have enabled and each user's permissions.
• Reservation tiles: today's arrivals, departures and in-house guests, and the unread reservations, as live counts on the Solidres dashboard and at the top of the administrator's home page. Each tile opens the Reservations list filtered the same way, so the number on the tile is the number of rows. Tiles count the statuses the reports count, on today's date in the site's time zone, and each can be hidden in the Quick Icon - Solidres plugin. Installing or updating to 4.5.0 adds them once; after that you can move or remove them.
• Four modules join Solidres: the Quick search module, which finds a reservation from the administrator's dashboard, and three site modules: Availability, a room type's availability calendar, Extras, a list of your extras, and Tracking, where guests look up their booking with its code and their email address. They are now part of Solidres, free, and install and update with it. A site that has them already keeps its modules and their settings.
• Getting started: a checklist card with the steps from a fresh install to a first booking, which ticks each step off as the site completes it: name the property and give it an email address, set the time zone, add room types, set rates, choose how guests pay, enter the Download ID when an extension needs it, replace the placeholder text of the website's pages and make a test booking, with clean web addresses and connecting channels as optional steps. Each step opens the screen where it is done. The card disappears once every required step is done, and each user can hide it. A new installation puts it on the Solidres dashboard and the home page, beside the reservation tiles. An updated site does not get it, since most of its steps are long done; add the Solidres - Getting started module from System → Administrator Modules if you want it.
• Back-office menu preset: a custom administrator menu can import the new Solidres back office preset: the Solidres groups, then Website (articles, media, menus, site templates and modules), Users, System (configuration, updates, installing, scheduled tasks, cache) and Help, which opens the Solidres documentation. It suits staff who run the booking site and need nothing else of Joomla.
• One Download ID: the Download ID in Solidres Options now reaches every Solidres extension. Saving Solidres Options writes it to every Solidres update site, installing or updating an extension copies it to that extension's update site, and every download Joomla makes from solidres.com carries it, even for an update site that lost its key. Nothing has to be pasted into System → Update Sites.
• Update status on the System page: each Solidres extension shows whether Joomla can update it: no update site, a Download ID missing, or the version Joomla's last check found, with a link to System → Update. A package's members show their package's status.
• In-house filter: the Reservations list can show the reservations staying on any day: arrived and not yet left.
• Unread count: trashed reservations are no longer counted as unread.
• Customers and coupons: both lists scroll sideways on screens up to 1440px wide. Their last columns used to be cut off.
• Rate plan dates: saving a daily rate plan with a new Valid from or Valid to fits its price grid to the new dates again, as it did before Solidres 4.0: days outside them are removed, and days they add appear empty, ready to price. A daily rate plan whose dates were changed since 4.0 is fixed the next time you save it.
• Minimum and maximum stay on manual reservations: staff creating or amending a reservation in the administrator, and partners doing so in the Hub's partner dashboard, can now book a rate plan priced by the night for a stay shorter than its minimum or longer than its maximum, for example to fill a one-night gap. Such a plan used to be left out of Choose a rate plan, which could leave the list empty. It is now listed with the limit the stay goes past, such as Standard rate (min. stay 3 nights), and priced night by night. Package rate plans still need a stay within their limits, and online bookings still enforce them.
• Deleting reservations: on a site without the Custom Field plugin, deleting a reservation no longer stops with a "Class CustomFieldHelper not found" error.
• Save as Copy: a copy of a property or a room type is named the way Joomla names copies, Sunflower (2), with the first free alias, sunflower-2. A copy used to keep the original's name and alias, and so its address on the site, which left one of the two out of reach of its own link. A copied property starts with Default off: copying the default property used to take the flag from the original.
• Unique aliases: each property needs an alias no other property uses, and each room type one no other room type uses, in any property, category or state, the trash included, because the alias is its address on the site. A save with a taken alias is refused with a message naming it, and an alias left empty becomes the first free one.
• Default property: the default property can no longer be deleted, unpublished, archived or trashed, from the list or by saving its form, since it is the property the Check availability module searches. The message names it and says how to make another property the default first. Other properties selected with it are still processed.
• Saving properties: a save keeps what its form did not show: settings the form has no field for, the payment method order, each payment method's settings, the tags, the facilities and themes, and custom fields the form left out. What the form did show is saved as sent, and a field emptied there is cleared: emptying the deposit amounts or the custom tabs now clears them, where a save used to keep the old rows. A form showing only part of a property, such as the Hub partner's, used to wipe the rest on every save: each payment method's base rate and visibility, the embed form settings, and Stripe, which switched itself off when its API key was hidden from partners.
• Hiding fields from Hub partners: Ignored property fields in Solidres Options → Hub works. It hides the fields you choose from the property form of Hub partners, and their saves keep those fields' values. The option could be set before but never hid anything. With Hub 2.4.0 it offers every field of the partner's form, by tab, and a new Ignored room type fields does the same for room types.
• Deleting properties: on a site with the Limit Booking plugin enabled, deleting a property no longer stops with a "Call to a member function setState() on null" error. The property's limit bookings are deleted with it, as intended.
• Coupons of a deleted property: deleting a property deletes only the coupons no other property uses. The others lose their link to it and keep applying to the properties they still list. Deleting a property used to delete every coupon linked to it, including coupons other properties still offered.
• Plugins tab: the Plugins tab of the property form, the experience form and the Hub partner's property form shows a plugin's description of its fields, such as Conversion tracking's note that a property's IDs are added to the site-wide ones.
• Rate plan tab: with Complex Tariff disabled, the room type's rate plan tab showed the channel manager sync notice as a raw language key. It reads as text again, in every language.
• Sites without a currency: before the first currency is added, as on a fresh install without sample data, the Experience dashboard and the Experience extras list no longer stop with a "Cannot assign null to property" error: amounts show without a currency until one is set. A display currency a visitor picked that has since been deleted no longer stops the page either: prices show in the base currency.
• Uninstalling Solidres: uninstalling the Solidres Core package stopped halfway with a "Class not found" error, and the site could then load no page, on the site or in the administrator. It now removes everything it installed: also the Solidres dashboard's modules, the reservation tiles on the administrator's home page and the Solidres Property content type that tags use, which a reinstall used to add a second time. As before, Solidres can only be uninstalled after its add-ons.

Multilingual sites

• No more Enable multilingual mode: the option is gone from Solidres Options. Solidres now finds out for itself whether Speedy Translate or Falang translates the site, and looks up translations only on pages in a language other than the site's default. Searches that used to need the option switched on, such as the Hub's location search, work without it.
• {lang} tags: on a site with Speedy Translate, the {lang en}…{/lang} blocks of a page are handled once, by Speedy Translate. They keep working in emails and PDFs as before.

Security

• Bookings made without an account: such a booking could be read, amended, cancelled or overwritten from the site's customer area by people who had not made it. Each of those now needs a signed-in user whose customer record is the booking's. Guests still reach their booking from the tracking page with its code and their email address, and the room list of an existing booking on the site is for the property's Hub partner only. The same owner check is fixed in the forms of the Hub 2.4.0, Feedback 2.1.1, Limit Booking 2.0.3 and Discount 1.0.3 released alongside. We recommend updating.
• Hub partner property form: with Hub 2.4.0, a partner can no longer set the fields only an administrator sets: the Default switch, which made their property the one the site searches, property approval, the access level, the creator and creation date, the commission rate, the staff and the menu item fields that create a menu item on the site.
• Links that forward visitors: with Experience 2.3.0, the Hub's experience list and the experience booking form forward a visitor to the address in a link only when it is a page of the site, so a link to your site can no longer send visitors to another one.
• PayPal payments: with PayPal 2.0.1, a payment is recorded only on the booking its PayPal order was created for. A PayPal order paid for one booking could be used to confirm another.
• PDFs: with the dompdf library 1.1.0, the invoices, vouchers and Hub commission notes are made with Dompdf 3.1.6, which fixes six security advisories in the version bundled until now, among them reading a local file through an SVG image in a document made from details a guest typed in.
• Stripe Connect: with Stripe 2.0.0 and Stripe for Experience 2.1.0, creating a connected account and opening its onboarding page, where payout details are entered, need a Solidres administrator or the partner of that property or experience. Both used to answer anyone.

Going away

• Complex Tariff: deprecated, and removed in Solidres 4.6.0. Its replacement, the Rate Plan plugin, edits the same rate plans, so nothing has to be entered again, and takes over as soon as it is enabled. While Complex Tariff is enabled without Rate Plan, the room type editor and the System page say so. Updating to 4.6.0 will stop on a site that still has Complex Tariff enabled without Rate Plan installed, because its rate plans would otherwise stop pricing bookings.
• Statistics: deprecated, and removed in Solidres 4.6.0. Front Desk and Dashboard replace its calendars and dashboard, read the same reservations and keep your saved widget layout. While Statistics is enabled, its pages and the System page say so, and updating to 4.6.0 will stop until Front Desk and Dashboard are installed.
• Falang: Solidres support for Falang is deprecated, and removed in a future release. Speedy Translate Lite, free, replaces it: it adds language tabs to the Solidres forms, and its Falang import copies your translations across. While Falang translates the site, the Properties and Experiences lists and the System page say so. Falang keeps working until then.
• Legacy date picker: deprecated, and removed in a future release. Its option in Solidres Options reads Legacy datepicker (deprecated) and shows a warning when selected, and the System page flags a site still using it. The Modern date picker stays the default.
• Solidres' own update check: removed. Solidres no longer contacts solidres.com from your administrator pages, so it no longer sends the list of your Solidres extensions and their versions. Joomla's updater finds Solidres updates instead: they are listed in System → Update with the rest of your site, and downloaded with the Download ID in Solidres Options. Check updates on the System page now runs that same Joomla check. The update notices on the System page come from it too.
• Google Analytics, Google Ads and Facebook plugins: replaced by Conversion tracking, and no longer released. Installing Conversion tracking copies their IDs and switches them off. Google Analytics had recorded nothing since Google stopped processing Universal Analytics in July 2023, Google Ads conversions carried no value, and all three counted a booking again on every reload of its confirmation page.
• For developers: SideNavigationHelper::getSideNavigation() now returns nothing and is deprecated. Its layout, layouts/solidres/navigation.php, is deleted on update.

Released alongside

• Dashboard 1.1.0: every widget takes its figures from the Reports engine, over one property and one period for the whole page, and links to its report. This fixes wrong figures: revenue filed under the check-in date, RevPAR worked out from checkout dates, currencies added together, and ranges such as last month finding nothing in January. The widgets follow the administrator template's light or dark mode, and Lumina's colours on the Hub's partner dashboard.
• Front Desk 1.1.0: the Reservation details window shows the note the guest left when booking, so special requests are visible from the calendar. The today strip counts arrivals and departures as the tiles do: on today's date in the site's time zone rather than the user's, and without the cancelled bookings it counted when no display statuses were set. The calendar follows the administrator template's light or dark mode.
• Hub 2.4.0: the Reports screen for partners. With Speedy Translate, the Hub's free-text search and the property search box of the Advanced Search module find properties by their translated names and addresses. They used to search Falang's translations only. Commission is recorded for experience bookings again: since the Joomla 6 versions of Hub and Experience, a booking made on an experience's page created no commission for its partner. Ignored property fields offers every field of the partner's property form, grouped by tab, and the new Ignored room type fields hides room type fields the same way; a tab, a group of custom fields or a payment method whose fields are all hidden is left out. A partner's save keeps what their form does not show: the embed form settings, the payment method settings, the commission rates linked to the property, and a room type's child pricing, which a partner's save used to reset to the site-wide rule. Partners edit room types in the administrator's room type form, without the fields only an administrator sets, and a partner's Save as Copy of a room type gives the copy new rooms and copies its rates and rate plans instead of taking the original's rooms. Partners can no longer set the administrator-only fields of a property (see Security). The embed form moved into Solidres as its free booking form, and the Hub no longer has one.
• Experience 2.3.0: with Speedy Translate, the location search finds experiences by their translated base and end locations, which it did with Falang only. A location can be typed in the page's language or as originally written. The Experience Search module no longer fails on a page in another language on a site without a translation extension. Deleting an experience works again: it used to stop with a "Call to undefined method" error. Save as Copy gives the copy time slots of its own; it used to move the original's time slots, and the bookings made on them, to the copy. Partners can publish, unpublish and trash their experiences from the Hub's experience list again. Deleting an experience deletes only the extras no other experience offers; it used to delete shared extras as well, with their lines in other experiences' bookings. The booking confirmation email and the PDF voucher show the experience's logo only when it has one; they used to show a broken image. Links that forward the visitor stay on the site (see Security). Uninstalling the package removes all of its tables: a database error used to stop it halfway.
• Custom Field 2.0.2: custom field titles in emails and PDFs come in the guest's language with Speedy Translate too.
• Reports 1.0.0: new, see above.
• Conversion tracking 1.0.0: new. Tells your analytics and advertising tools that a booking was made, once per new booking: never on a reload, for an amendment or for a payment that failed. It publishes a GA4 purchase on the data layer for Google Tag Manager and a solidres:purchase browser event for other tools, and has connectors that need only an ID for Google Analytics 4 and Google Ads, Meta Pixel, Microsoft Advertising, TikTok, Matomo, Plausible, Umami and Fathom, with the hotel campaign fields Google, Meta, Microsoft and TikTok read. Custom code with booking tokens reaches any other tool, and each script can wait for your consent tool. IDs are set for the whole site, and a property or an experience can add its own on its Plugins tab.
• ACL 1.0.2: enforces the new Reports permission, and the permissions of the tourist tax screens, which ignored them. The new Booking form screen follows the System permission, as the rest of the System group does.
• Channel Manager 4.2.0: the MyAllocator connection is removed, since MyAllocator support ended on 1 October 2026. A site still set to MyAllocator is moved to the Solidres Channel Manager on update. Beds24 support ends on 15 November 2026, and the Channel Manager now says so wherever Beds24 is set up. The Inventory grid joins the package, at the package's version: Inventory 4.2.0 installs, updates and uninstalls with the Channel Manager. Install the package over the Inventory plugin you have; nothing else to do. Uninstalling the package now removes its tables. Trashing or archiving a room type takes it off the channels, as deleting it does: a trashed room type used to stay on the channels and count towards the plan's room limit. With the Channel Manager enabled, changing the country on a guest form no longer ends in an error, and a partner's property save keeps the Beds24 property mapping.
• Currency 2.1.0: now a package: the Currency plugin and its exchange rate task plugin install, update and uninstall together, and update from System → Update with the Download ID in Solidres Options. Install the package over the Currency plugin you have; nothing else to do.
• iCal 3.1.1: the iCal URL of a room type or an experience now ends in .ics, so Airbnb accepts it as it is. Links you have already given to other sites keep working. A partner's room type save keeps the room type's iCal settings. The package now updates from System → Update with the Download ID in Solidres Options.
• Flex Search 1.0.3: its results price rate plans again. Since its Joomla 6 version it had shown the standard tariff only, whichever rate plan editor was enabled.
• Rate Plan 1.1.3: the rate plan editor fits a phone: its fields no longer stick out of their boxes, and a daily rate plan sets out each date's fields two to a row instead of one under the other. With Speedy Translate, the language tabs of a rate plan's Title and Description now send what you type under the names Speedy Translate saves, and each rate plan you open shows its own translations; saving them also needs a Speedy Translate release that supports the Rate Plan editor. The tabs show only in Speedy Translate's Speedy mode, the one that saves them.
• Stripe 2.0.0: the Stripe payment plugin for Joomla 6 and Solidres 4. Stripe 1.0.1 and earlier were made for Solidres 3, and on Solidres 4 they stop the booking page from loading. Install 2.0.0 over the version you have; your Stripe settings are kept. From now on Stripe updates from System → Update with the Download ID in Solidres Options. With Stripe Connect, the Sign up and Add information buttons of a property's payment settings work again, on the administrator's property form too, and only for a Solidres administrator or the partner of that property.
• Stripe for Experience 2.1.0: Stripe Connect works on an experience's payment settings: the Sign up and Add information buttons create and link the connected account, for a Solidres administrator or the partner of that experience only, and a booking paid through Stripe Connect no longer fails. From now on it updates from System → Update with the Download ID in Solidres Options.
• Camera 2.1.0: now a package: the Camera Slideshow plugin and the Camera Slideshow module install, update and uninstall together, and update from System → Update with the Download ID in Solidres Options. Install the package over the plugin and module you have; your settings and module positions are kept.
• Clocks 1.0.0: rewritten for Joomla 6. Each clock follows the time zone of its city, daylight saving time included; 0.1.x moved every clock by the daylight saving time of the browser it was viewed in. The row can open with the website's own time, the clock faces follow the administrator's light and dark modes, and the module updates from System → Update with the Download ID in Solidres Options. Clocks set up with 0.1.x are kept: a clock named after a city gets that city's time zone, and any other keeps its UTC offset until you choose a time zone for it.
• Feedback 2.1.1: the security fix for bookings made without an account: a signed-in user could review such a booking without having made it. A guest reviews it from the link in their feedback request, as before.
• Invoice 2.1.1: paying an invoice goes to the payment method the guest picked, and only to it. With PayPal enabled, paying an invoice with another method such as Mollie used to start a PayPal payment instead. The package now updates from System → Update with the Download ID in Solidres Options.
• Discount 1.0.3, Limit Booking 2.0.3, SMS 1.0.2 and Nano Gallery 2.0.1: Discount and Limit Booking carry the owner check fixed under Security; a partner's property save no longer clears its SMS settings; Nano Gallery follows the template's light or dark mode.
• Updates for every plugin and module: ACL 1.0.2, Advanced Extra 1.0.2, Custom Field 2.0.2, Dashboard 1.1.0, Discount 1.0.3, Flex Search 1.0.3, Front Desk 1.1.0, Housekeeping 2.0.3, Limit Booking 2.0.3, Load Module 1.0.1, Nano Gallery 2.0.1, QR Code 1.0.1, Rate Plan 1.1.3, Reports 1.0.0, Reservation Code 1.0.1, SMS 1.0.2 and Stream 2.0.4, the PayPal 2.0.1 and Offline 1.0.1 payment plugins, the Map 1.0.1, Tabs 2.0.1, Vegas Slideshow 1.0.1 and Splide Slideshow 1.0.0 modules, and the dompdf library 1.1.0 update from System → Update with the Download ID in Solidres Options. Install each of these versions once over the one you have; from then on its updates are listed in System → Update.
• Lumina 1.1.2: the Hub's Reports screen takes Lumina's colours. With no logo file and no site title set, the header shows the site name as a text logo instead of the template's sample logo. On a booking site the header links back to your main website and leaves out the menu, the hero and the footer columns (see Booking site and booking form). Lumina updates from System → Update with the Download ID in Solidres Options.

Before you upgrade

• Requirements: Hub 2.4.0, Experience 2.3.0, Custom Field 2.0.2, Dashboard 1.1.0, Front Desk 1.1.0, Reports 1.0.0 and Conversion tracking 1.0.0 need Solidres 4.5.0. Update Solidres first.
• Conversion tracking: the values your tools receive change. Google Analytics gets the revenue before tax, as the Revenue report counts it, so it shows less than the old plugin sent; Google Ads, Meta and the other ad platforms get the total the guest pays. If your site also loads one of these tools through Google Tag Manager or its template, use either that or the connector for it, not both, or bookings are counted twice.
• Multilingual sites: update Hub, Experience and Custom Field with Solidres. Their earlier versions read the removed Enable multilingual mode option, so once Solidres Options are saved their translated searches stop, and the Experience Search module can fail on pages in another language.
• Get ready for 4.6.0: if you still use Complex Tariff or Statistics, install and enable Rate Plan, or Front Desk and Dashboard, now. They use the same data and take over as soon as they are enabled, and the update to 4.6.0 will not go ahead without them.
• Database: the update adds a table for the nightly prices, a cancellation date on reservations and two indexes on the reservations table. Reports on bookings made before 4.5.0 spread their room price over the stay, and cancellations made before 4.5.0 have no date.
• Reports permission: if you use the ACL plugin, grant the Reports permission to the groups that should see reports. No group other than Super Users has it until you do.
• Aliases: properties, or room types, that already share an alias keep it until one of them is saved: that save then asks for an alias of its own. Room type aliases are now unique across all properties, so a double-room in two properties needs another alias in one of them, such as double-room-2. A new alias changes that page's address, so update any links to it.
• Template overrides: three front-end layouts have changed: layouts/com_solidres/asset/rooms.php, the room step of the reservation form in the administrator and the Hub's partner dashboard, and layouts/com_solidres/asset/coupon_form.php and layouts/com_solidres/asset/checkinoutform_apartment.php, for the coupon field on apartment pages. In the administrator, the Customers and Coupons lists, the property form and its Channel Manager tab, the room type's tariff and Channel Manager tabs, the System page and the Statistics and Calendars notices have changed, and the System page flags overrides of them that need updating. An override of layouts/solidres/navigation.php no longer has any effect. For the booking site, the property page layouts (com_solidres/reservationasset/default.php, default_style2.php and default_style3.php) have changed, and the embed form's layouts moved from the Hub into Solidres: layouts/com_solidres/embed/form.php and script.php on the site, with the new button.php and plain.php, and the administrator's preview, which is now layouts/com_solidres/embed/preview.php.
• Dark mode in templates and custom CSS: Solidres' site styles no longer switch on prefers-color-scheme. They pair each light colour with its dark one in light-dark(), which follows the color-scheme your template declares, and follow [data-bs-theme="dark"]. A template with a dark mode gets dark Solidres pages once it declares color-scheme or sets that attribute. Check any custom CSS that restyled Solidres inside a prefers-color-scheme: dark query.
• Booking form codes: a code pasted on a website from the Hub's embed form stops working once the Hub is updated to 2.4.0, which removes the script it loads. After updating, copy the new code from the Solidres menu → System → Booking form (or the property's Embed form tab) and replace the old one on your website.
• Beds24: support ends on 15 November 2026. A site keeps syncing with Beds24 on the versions it has installed, but a Solidres or Channel Manager update released after that date no longer supports it. Plan your move before then.