New switch added to Site Configuration > Portal Functionality tab called "Force Compatibility property configuration mode?" This option ensures that all new properties automatically use the Standard tariff editing mode, and they are unable to switch to other tariff modes. This simplifies the price configuration options available to managers. By default, all new installations of Jomres have this option set to Yes, updated installations have this set to No.
Added new Tariff Editing mode : Standard. It is based on Micromanage, but some of the more confusing elements have been removed and have added some new elements.
In Standard mode you can only create one tariff for each room type. With Standard editing guest number dropdowns are visible in the booking form by default, the old style guest types are not supported. You can add an "Extra guest price" in Property Configuration > Standard tariffs tab (todo later versions will include the ability to set extra guest prices for individual tariffs).
Standard editing mode introduces new 7 and 30 day modifier settings. They can either be flat rate or a percentage calculation that will discount bookings if they're longer than 7 and 30 days respective.
When in Standard mode many previous Property Configuration options are no longer available to property managers as they're sometimes conflicting or simply overkill and un-necessary for property managers to access.
Child rates. If a property uses Standard tariff editing mode then they are able to set Child rates. These rates are the same, regardless of the room types chosen. Manager can create their own child rantes (todo nice to have, use javascript to ensure that child age ranges don't overlap)
Occupancy Levels. Once rooms have been added, the manager should then check that occupancy levels are valid for different room types (todo this can be improved, currently you need to save occupancy levels after adding/removing rooms, because total occupancy levels need to be recalculated however would like to automate this some more).
Property Configuration > Bookings tab has two new options. City tax and Cleaning fee. City tax offers a variety of models by which the tax can be calculated. Booking form template adjustments are required to capitalise on these new changes.
Added clauses that allow me to distribute a new search widget plugin with different template files
Added ability for script to hand form elements to the search script, which can then be given to the template file for rendering.
Improved error feedback for users. Red whoops screens will now include the message that was part of the thrown error, as normally these errors require inspection of the error logs to determine the issue. This approach is more helpful and it doesn't expose any vulnerabilities.
Significant changes to make Jomres compatible with Joomla 4. There are still a handful of things to figure out, and Jomres plugins still need J4 template files, but this takes us 95% of the way to be J4 ready.
Added func to empty package dirs first before update.
Added Connect admin panel to Core.
Added a check for BS4 when building property config tabs.
Save my account modified to create user images dirs if they don't exist.
Some modals modified to use new bs4 hide class.
Added ability to disable sending all emails. No config option available, configuration.php would need to be edited to disable them ( 'send_emails' => 0, )
Switched to saving extra name instead of the definition string.
Max input vars description updated.
Updated installation process for wp to ensure that Jomres can be installed under the WP Plugins dir.
Tweaked how placeholders are set in the generate date input function.
Admin FAQ section removed as the questions are old and there are better resources available online.
Added check to see if autoload.php exists, if it doesn't force package reinstallation. On occasion, if the server was slow with the download then autoload.php not existing can be one of the best indicators that the packages weren't completely downloaded therefore if it doesn't then we need to start again.
Removed lots of clauses that check to see if X option has been enabled in integrated search. While these checks are useful to reduce the amount of work required to create the search form elements, unfortunately the clauses can create a lot of confusion when things don't appear in search forms (e.g. dropdowns for regions etc). For simplicity's sake we'll remove the checks, meaning that all of the search things will be available all of the time.
Added a new ajax script designed to respond with populated locations.
Removed option regarding if BS should be used in frontend, it hasn't been a valid option for years.
Moved hidden inputs from bottom of site config form to top because this may fix some odd intermittent behaviour seen in some places.
Moved hidden inputs from bottom of property config form to top because this may fix some odd intermittent behaviour seen in some places.
Standard and Micromanage tariff editing modes updated to work with BS4
Improved error reporting if a template file does not exist.
Added ability for search handling script to receive a custom search template file name.
Changed "number of guests" to "sleeps" in language files.
Disable gateways tab if using jomres platform
Editing mode disable in Wordpress frontend. It's stopped working and it's problematic as it's an extra layer of functionality that managers don't need. Backend editing mode works fine.
SRP Schema changed from Residence to LodgingBusiness
Added a warning to advise that users must be property managers to use the media centre. This is because the MC scripts are called by both front and backend.
Added search related functionality for constructing search forms (todo) relating to new occupancy levels.
Fixed a notice that can be thrown when room type images don't exist.
Fixed room type markup not being re-parsed.
Anonymise street information if settings require it (basic module output function used by some plugins).
Resolved an annoying niggle of date picker font sizes being overlarge.
Tweaked email checking functionality so that an email address can only be re-used if it's because a manager has used the select guests dropdown.
Changed how we prevent opt-ins from being stored, as was causing weird and wonderful behaviour in specific circumstances in the booking engine.
New switch added to Site Configuration > Portal Functionality tab called "Force Compatibility property configuration mode?" This option ensures that all new properties automatically use the Standard tariff editing mode, and they are unable to switch to other tariff modes. This simplifies the price configuration options available to managers. By default, all new installations of Jomres have this option set to Yes, updated installations have this set to No. Added new Tariff Editing mode : Standard. It is based on Micromanage, but some of the more confusing elements have been removed and have added some new elements. In Standard mode you can only create one tariff for each room type. With Standard editing guest number dropdowns are visible in the booking form by default, the old style guest types are not supported. You can add an "Extra guest price" in Property Configuration > Standard tariffs tab (todo later versions will include the ability to set extra guest prices for individual tariffs). Standard editing mode introduces new 7 and 30 day modifier settings. They can either be flat rate or a percentage calculation that will discount bookings if they're longer than 7 and 30 days respective. When in Standard mode many previous Property Configuration options are no longer available to property managers as they're sometimes conflicting or simply overkill and un-necessary for property managers to access. Child rates. If a property uses Standard tariff editing mode then they are able to set Child rates. These rates are the same, regardless of the room types chosen. Manager can create their own child rantes (todo nice to have, use javascript to ensure that child age ranges don't overlap) Occupancy Levels. Once rooms have been added, the manager should then check that occupancy levels are valid for different room types (todo this can be improved, currently you need to save occupancy levels after adding/removing rooms, because total occupancy levels need to be recalculated however would like to automate this some more).
Property Configuration > Bookings tab has two new options. City tax and Cleaning fee. City tax offers a variety of models by which the tax can be calculated. Booking form template adjustments are required to capitalise on these new changes. Added clauses that allow me to distribute a new search widget plugin with different template files Added ability for script to hand form elements to the search script, which can then be given to the template file for rendering. Improved error feedback for users. Red whoops screens will now include the message that was part of the thrown error, as normally these errors require inspection of the error logs to determine the issue. This approach is more helpful and it doesn't expose any vulnerabilities. Significant changes to make Jomres compatible with Joomla 4. There are still a handful of things to figure out, and Jomres plugins still need J4 template files, but this takes us 95% of the way to be J4 ready.
Added func to empty package dirs first before update. Added Connect admin panel to Core. Added a check for BS4 when building property config tabs. Save my account modified to create user images dirs if they don't exist. Some modals modified to use new bs4 hide class. Added ability to disable sending all emails. No config option available, configuration.php would need to be edited to disable them ( 'send_emails' => 0, ) Switched to saving extra name instead of the definition string. Max input vars description updated. Updated installation process for wp to ensure that Jomres can be installed under the WP Plugins dir. Tweaked how placeholders are set in the generate date input function. Admin FAQ section removed as the questions are old and there are better resources available online. Added check to see if autoload.php exists, if it doesn't force package reinstallation. On occasion, if the server was slow with the download then autoload.php not existing can be one of the best indicators that the packages weren't completely downloaded therefore if it doesn't then we need to start again. Removed lots of clauses that check to see if X option has been enabled in integrated search. While these checks are useful to reduce the amount of work required to create the search form elements, unfortunately the clauses can create a lot of confusion when things don't appear in search forms (e.g. dropdowns for regions etc). For simplicity's sake we'll remove the checks, meaning that all of the search things will be available all of the time. Added a new ajax script designed to respond with populated locations. Removed option regarding if BS should be used in frontend, it hasn't been a valid option for years. Moved hidden inputs from bottom of site config form to top because this may fix some odd intermittent behaviour seen in some places. Moved hidden inputs from bottom of property config form to top because this may fix some odd intermittent behaviour seen in some places. Standard and Micromanage tariff editing modes updated to work with BS4 Improved error reporting if a template file does not exist. Added ability for search handling script to receive a custom search template file name. Changed "number of guests" to "sleeps" in language files. Disable gateways tab if using jomres platform Editing mode disable in Wordpress frontend. It's stopped working and it's problematic as it's an extra layer of functionality that managers don't need. Backend editing mode works fine. SRP Schema changed from Residence to LodgingBusiness Added a warning to advise that users must be property managers to use the media centre. This is because the MC scripts are called by both front and backend. Added search related functionality for constructing search forms (todo) relating to new occupancy levels.
Fixed a notice that can be thrown when room type images don't exist. Fixed room type markup not being re-parsed. Anonymise street information if settings require it (basic module output function used by some plugins). Resolved an annoying niggle of date picker font sizes being overlarge. Tweaked email checking functionality so that an email address can only be re-used if it's because a manager has used the select guests dropdown. Changed how we prevent opt-ins from being stored, as was causing weird and wonderful behaviour in specific circumstances in the booking engine.