This documentation highlights the information displayed on list of records, and the holidaymaker health-check system.
Throughout the holidaymaker CMS you will find lists of tour records. These can be your places, offers, events, or even smaller core entities such as alert boxes, and banners.
When these entities are listed they are often presented with a ‘Holidaymaker’ column with addition information and filters available at a glance.There will also often be a ‘Check-Up’ column to show any warnings, or errors on a record at a glance.
Example Place Record List Item
Example Offer Record List Item
This column will give you base information common to all records, and some additional information depending on the type of record you are viewing.
The ‘Sort Priority‘ heading will be visible for many records. The default sort is 99, with items being ordered in a ascending order – eg the lower the number the higher up the list in the mobile apps this record will be.
You can also click on the sort priority to order the list in the CMS to this same order.
Holiday Homes for Sale, and FAQs also will include a ‘Featured‘ heading. This will display along side the sort priority if a record is marked as featured. In the mobile apps, featured records will be sorted to the top, before the sort priority is taken into account.
You can also click on featured to order the list in the CMS to this same order.
Homes for Sales listings with priority and featured
If you are a group-site client (eg multiple parks or locations) then many of your list views will include the ‘Group Sites‘ heading. This will list any sites that this content is enabled for. This will show for all the main holidaymaker entities, apart from Holiday Homes for Sale which have their own location information instead.
You can also click on a group site name to filter the list in the CMS to records available to that group site.
If you have the people module enabled, or an entity supports legacy segmentation (During Stay, Signed In, Owners Only etc) then the ‘Segments’ heading will show. This will then state if the record is available for all, or is set to specific segments of people.
Offer listings with Group Sites and Segments
Various other record lists will also show additional information in this column. For example Holiday homes for Sale show the current price, and location, and Go Explore Routes show what activity, and terrain is set to them.
Go Explore Route listings with extra details in the Holidaymaker column
If you have the web module enabled, then the developer of the web surface has the ability to remove any data from this column if not relevant to your setup. In the same way they would be able to add in additional information which may be bespoke to you.
Many record lists also include a check-up column. This is to give you traffic light coloured icon, and a number if warnings, or errors on that record are found.
If a record normally includes an image, then this image is also shown on the list, with a place holder if missing.
Three records - one which passes the checkup, one with two warnings, and one with two errors (including missing image)
Some entities do not have images - eg Alert Boxes, and Information Blocks
An extra box is added to a record’s edit page which gives you more details of warnings or errors which have been found.
Errors: Common errors are missing images, missing descriptions, or detail copy, and any settings which may mean that the record will not render of function correctly.
Warnings: Common warnings are information which would give the record basic rich functionality such as missing categorisation and optional metadata which often makes a record more functional and useful to guests
Example of box with list of suggested improvements (warnings)
Example of box with list of breaking issues (errors)
If a record has valid reasons to have missing data then you can find a suppress the warning/error flags on list views by ticking on the switch found at the bottom of the side area.
Examples where this would be used:
If you have the web module enabled, then the developer of the web surface has the ability to manipulate the health check on a entity-by-entity, or even record-by-record basis. This includes escalating a warning to an error, adding adding additional warnings or errors, or removing existing warnings or errors if that data is not used on your setup.