Content Not Being Displayed With the New Lexical Editor (#3325)
With the 5.36.0 release, we’ve addressed a couple of Lexical-related usability issues. Unfortunately, we’ve also introduced an issue that would cause content created with the previous version of the editor to not get displayed.
With this release, the Lexical content that was created prior to 5.36.0 version of Webiny should displayed as expected.
Website Settings - Fixed Theme Selector (#3331)
In a multi-theme setup, at the end of the Website Settings form, the select component that would enable users to pick the theme for the current tenant wasn’t working as expected. On page load, the select component would be simply empty and not showing the value that was previously selected.
As seen in the screenshot, the select component now correctly shows the currently selected theme.
Intermittent Errors When Refreshing the Page Builder (#3331)
Intermittently, when refreshing the Page Builder’s page editor, users might experience the editor crashing. This issue has been addressed with this release.
Button Page Element Crashing on Empty Link URL (#3331)
When creating a button page element, in some cases, if the user would leave the link URL field empty, the editor would crash. This issue has been addressed with this release.
Folder Creation Issue (#3328)
The 5.36.0 version introduced a bug that affected the folder creation process when using the “Create folder” button in the top right corner. After completing the folder creation process, the folder was not saved with the correct
parentId, and not showing in the folder tree.
With this bug fix, folders will now be properly saved with the appropriate
Folder Tree Performance Improvements (#3332)
We experienced some performance issues when creating 8 or more nested folders: this has been solved and the tested creating more than 50 nested folders.
Migration Failure in Locale Without File Entries (#3333)
With 5.36.0 version we introduced the Advanced Content Organisation for File Manager: in order to work a data migration was needed and executed via the Data Migration Lambda Function. When dealing with a locale that lacked file entries, the migration process would fail.
We have resolved this migration bug. The fix ensures that in cases where a locale does not have any file entries, the migration process no longer encounters errors and proceeds smoothly.
The fix specifically targets instances where the migration failed due to this particular scenario. In case you experienced a migration failure, this has been marked as failed and will be re-run during Webiny project deploy.
Prior to this release, the
webiny infoCommand Now Works as Expected (#3331)
webiny infocommand would not work if an environment wasn’t passed (in which case the command should internally retrieve a list of all environments).
This issue has now been addressed.