Continuum XFP #121 (8.0.0)
In XFP 8.0.0, we have introduced compatibility with our updated system requirements. This includes support for PHP 7.4, MariaDB 10.5 and SQL Server 2019.
This release:
New Adds compatibility with Maria DB 10.5, Windows Server 2019 and SQL Server 2019.
We have ensured Jadu XFP is compatible with the updated stack requirements. Developers who have developed their own functionality can review the changes in the developer guidance.
Impacts: Custom developments.
New Adds compatibility with PHP 7.4.
We have ensured Jadu XFP is compatible with the updated stack requirements. Developers who have developed their own functionality can review the changes within PHP 7.4 on php.net.
Impacts: Custom developments.
New Adds indexes to CXM user form metadata table.
This table associates the CXM person reference with the form submission and helps power the User Account, Organisation and Person Reference variables. Adding indexes improves the performance of the queries that are run when completing forms integrated with CXM.
Impacts: Internal forms integrated with CXM that pass in the personReference url parameter.
New Adds indexes to the event booking event table to improve performance.
The event booking tables store the booked events data collected when making a booking using the event booking component on a form. Adding indexes improves the performance of the queries that are run when using the event booking component.
Impacts: Event booking component.
New Adds pagination to the forms list view.
The forms list view on the website (accessed via xfp/forms) defaulted to only displaying the first 50 live and visible forms. This update adds pagination to the list view page to enable users to find the appropriate form for their needs.
Note, if your site is using the classic templates professional services will be required to style the pagination section of the forms list page as part of this release. Photon sites will inherit existing styles for pagination and do not require professional services.
Impacts: Form list on the website accessed via the url xfp/forms.
Update Updates include path for File Upload question dropzone javascript on embedded forms to load dropzone.js from the web front end instead of the control centre.
The file upload question uses the dropzone.js library to let users drag and drop files into the question. As a javascript library it is included on the client (browser) side. In XFP two versions of the dropzone.js library exist, one for the website and another for the control centre. Embedded forms should use the website version. This update ensures that the website version is used on embedded forms.
Impacts: File upload questions on embedded forms.
Update Updates the location of schedule task lock files from the logs directory to the temp directory.
This change is required on WISP environments where the user account used by the background tasks for Data Retention, PayBridge Balance Import and User Account Deletion does not have permission to create the lock file in the logs directory.
Impacts: Data Retention, PayBridge Balance Import, User Account Deletion.
Update Updates the logo for Whitespace within the Integrations page.
Impacts: Whitespace integration pages.
Update Updates the logo for Bartec Collective within the Integrations page.
Impacts: Bartec Collective integration pages.
Update Updates encryption method used by Connector settings and Office 365 authorisation.
Sensitive settings are stored encrypted in the database. Over time it becomes necessary to update the encryption methods used to ensure the platform stays secure. Existing settings are migrated to the new encryption method without needing to be reentered after deployment of the patch.
Impacts: Connectors and Office365 Integration and Event Booking component.
Update Updates database binding for MySQL database connections configured in the control centre under XForms Pro > Database Connections to use mysqli instead of mysql.
Mysql database functions were removed in PHP 7.0.0 and replaced with mysqli equivalents. XFP Database Connections are typically used by custom integrated components to retrieve records from a third party database, although some developers may have used the functionality in other custom developments.
Impacts: Custom Integrated Components.
Update Standardised database table names to singular convention. Pluralised database table names have been renamed to their singular form.
Details of the changes are available in the developer guidance.
Impact: Custom developments that directly query XFP database tables.
Update Removes unused constants and global variables from constant.xml.example and globals.xml.example files.
Existing installs will not be affected by this change due to the example files not being actively used by the application. The example files are used during the installation process to create configuration xml files for the install.
Impact: New installs only.
Update Updates the Location component to use the settings configured under Integrations > Google Maps instead of XFP specific constants “xforms_google_maps_integration_enabled” and “xforms_google_api_key”.
The Location component will now use the Google Map keys from the Integrations pages. If you use Google Maps ensure that the keys are set under Integrations > Google Maps after updating.
Impact: Location component.
Update Updates all day events booked using the Event Booking question to use the start and end date columns in the database
All day bookings and slot bookings before this version used different database columns to save the booked date. This resulted in complicated queries that were slow running. We have refactored the code to simplify the queries and improve performance. All existing all day events will be migrated and the behaviour of the event booking component is unchanged.
Impacts: Event booking component.
Fix Fixes an issue with rolling back migration 20200812164339 treating single entries in logic inputs as arrays.
Logic inputs can be set to accept multiple entries, for example, the Postcode Area logic allows users to define postcodes within 4 areas. It was expected that more than one entry would be provided for each area. However if only a single entry was provided when rolling back this migration the rolled back data ended up in the form of an array and not a single entry.
Impacts: Postcode Area logic after a deployment rollback.
Fix Fixes link for “Change your notification settings” in the daily submission digest email so it goes to the CRM Submission Digest setting in the control centre instead of a 404 page.
The CRM submission digest will send a daily summary of CRM submissions (including CXM) with the total number of submissions made and details of any failed submissions. The email contains a link to “Change your notifications settings” that when clicked should take the user to the XForms Pro > CRM page in the control centre. The fix ensures the link is resolves to the CRM Submission Digest setting page and doesn’t give a 404 when clicked.
Impacts: CRM Submission Digest email.
Fix Fixes the link to setup a connector from the data management export configuration page.
When setting up a data management export, XFP gives the option to transport the exported data via a connector to another system. A link to guide users to the connector setup page is provided on the export configuration page. When clicked the link should take the user XForms Pro > Connectors. Prior to this change clicking the link to setup a connector from the data management export configuration page would result in a 404 page.
Impacts: Data management export configuration.
Fix Fixes using event booking questions within a repeatable question.
An event booking question in a repeatable question that has at least two rows of responses would only save the answer to the event booking question from the last row entered. This fix ensures that all responses to an event booking question in a repeatable question are saved.
Impacts: Event booking question within a repeatable question.
Compatibility
This release contains both XFP 8.0.0 (8.0.0) and the corresponding Continuum CMS version in a single package. There is no need to apply the Continuum CMS package separately.
If you are unsure of compatibility please speak to Jadu Support who can advise.
Semantic version number: 8.0.0