Terminalfour: 8.3.3
- Date Released:
- February 7 2020
General
In our continued effort to improve the product's usability, we've made some more adjustments in the area of Direct Edit and Media Library. These changes are the direct result of user testing and feedback sessions. If you are interested in getting involved in future sessions please contact our Product Manager Laura Murphy, and let us know. These usability improvements will be an ongoing process.
The changes made specifically for this release were:
Direct Edit
- Direct Edit now has a walkthrough/introduction to give a first-time user a view on the main features of editing through the Direct Edit interface. This guides the user once they enter Direct Edit
(RDSM-31285)
- We got feedback to say the positioning of the WYSIWYG toolbar wasn't working well - it used to be always at the top of the screen. With these changes, it becomes sticky to the movements of the user to make it more obvious. We also changed where the content block options are so they don't overlap with the WYSIWYG as that was causing frustrations.
(RDSM-31283)
- Small coloring changes were introduced such as the contrast in the Direct Edit admin interface to help with navigation
(RDSM-31277)
. Highlighting text in Direct Edit should be much more obvious now with a blue tone over the highlighted area.(RDSM-31282)
Media Library
- We've reviewed and made a few changes to the flow of cropping images and variant creation. The save button is more obvious so as not to confuse it with the overall media save, the crop tool is initiated once you get in there so it's easier to proceed with your task. We've also made wording changes, label changes and adjusted placement to improve the experience of creating variants.
- Sticking with variants we've made it much easier to see whether your items have variants already and how many variants exist. They'll show up in the listing now
(RDSM-31288)
- Lots of people don't know that you can use the description field in our media item in order to populate the alt tag of your images. We added a small bit of extra information in our labels to make sure people don't miss that useful opportunity.
(RDSM-31275)
Stripe changes
Stripe version updated to 16.1.0
Did you know our Form Builder can accept credit card payments through Stripe?
We've updated the interface for this and updated our integration to version 16.1.0 of the Stripe API. This means we are ready for Strong Customer Authentication enforcement. In order to make use of the new API, you'll need a publishable key from your Stripe dashboard. 8.3.3 allows you to add a Stripe publishable key in the payment gateway interface so you can use the new API. If you are on older versions (pre 8.3.3) and wish to use the Stripe please contact Client Support to make the relevant updates.
In Form Bank on the published forms, you'll notice changes to the credit card field. We now require less information than previously such as a full address, the interaction is much more compact now. The field itself automatically adapts to the credit card information as it's typed in. For example, US credit cards have a zip code field whereas for a UK card a postcode field will appear.
Language changes
We started a project to review and ensure the language and wording within the product are consistent, accurate and meaningful. This release includes over 100 minor text changes to start to make that goal a reality.
Ability to disable Programmable Layouts
This release sees the introduction of a configuration option to turn off Programmable Layouts. This has been put in place from an administrator's perspective to help with debugging issues that potentially have been caused by your programmable layout scripts. It will turn off all Programmable Layouts in your application so it should be used with caution.
Specific bugs
Mirrored content deletion in Direct Edit - RDSM-31571
The experience of deleting mirrored content in inline edit mode in Direct Edit was different to that of the normal interface. In the normal interface when you try to delete content that is mirrored you get the option to just remove the content from this Section or to make it inactive. The same thing now happens in inline edit mode in Direct Edit as a result of the changes in this release.
Remember/retain Media Library category location after actions - RDSM-30478
This is an issue that caused much frustration among users so we're delighted to get it cleared up. Navigation in the Media Library frequently left you at the root category rather than the category you were just in. That should behave much better now with the changes we've made here.
Section link is not showing up in preview until content is saved - RDSM-29253
This is another issue that has caused unnecessary confusion for many clients in the past. Before this fix when you create new a Content Item that has a Section/Content Item link in it the preview wouldn't show up correctly for the link until the Content Item was saved. We've changed this now so the preview should the correct regardless of whether the Content Item has previously been saved or not.
Content Syncer - the ability to map publish date, expiry date and review date RDSM-24158
The ability in External Content Syncer to map the publish date, review date and expiry date from the external source existed in version 7.4 but was never ported to version 8. We've got that back up and working again now so you map these properties in the same way as mapping your external data to content elements.
Drop Support / End of Life functionality
As part of our streamlining goals, we're removing functionality that is no longer in use or useful to our users. This allows development flow to be cleaner and helps us improve the overall health of the application. A number of features are reaching end-of-life with this release. Please see our technical roadmap for ongoing details.
Before upgrading
In advance of the upgrade please view the information and Technical Roadmap. Please contact us prior to upgrading we can provide you with the pre and post-upgrade tasks.
Priority
Please note that the priorities assigned to bugs differ from those assigned to Client Support tickets:
- P1 - Major rework of product.
- P2 - Major performance change.
- P3 - Regular priority change.
- P4 - Minor change.
- Trivial - Very minor UI changes.