jsonwebtokento v9.0.1 (#3483)
HTML Sanitization inIn order to further minimize the possibility of cross-site scripting (XSS) attacks, the HTML that’s rendered by the legacy rich text editor will now be sanitized, which is done with the help of the
Sanitization rules can be completely customized, using global configuration, or it can be configured on individual component instances. Read more about the sanitization configuration on NPM.
Form Field Values Not Updating When Switching Between Page Elements (#3478)With the 5.37.0 release, a regression was introduced that affected the page editor.
When switching between page elements in the page editor, in the right sidebar, the form field values would not update to reflect the values of the newly selected element.
This issue has now been taken care of and the form field values will update as expected.
Button Page Element Fixes (#3479)
Two issues have been addressed with the Button page element.
First, in case the button was first used as a regular link to another page, and then the user decided to use the Scroll to element functionality instead, the button would not update to reflect the new functionality. Basically, the button would still behave as a regular link to another page.
Second, a similar issue was present when a user enabled New tab option upon setting up their button as a regular link to another page. Again, in case the user decided to use the Scroll to element functionality instead, the button would still open the link in a new tab, making the Scroll to element functionality unusable.
Both issues have been addressed and the button will now behave as expected.
Bringing the Scroll to Element Feature Into the Lexical Editor (#3474)
Previously, the Scroll to element feature was only available with the Button page element.
With this release, the feature has been also brought into the Lexical editor.
Improve the New Entry Modal Dialog (#3485)
With the introduction of the advanced content organization in our previous releases, all content is now organized in folders. With this release, we’ve also added the folder selector to the modal dialog that lets you create new content entries inline, when using the Reference field. Now you will clearly see where the new content entry is located in the associated content model folder hierarchy.
elasticSearchparameter that can be specified via the
webiny.application.tsfile. In short, the parameter also allows developers to specify a shared Amazon ElasticSearch cluster, so that it’s used with multiple Webiny project deployments, instead of having to create a new cluster for each deployment. This can be useful for development and staging environments, where the data is not critical.
However, a few issues were present with the parameter, and they have now been addressed.