New IFrame Page Element (#2319 )
A new IFrame (inline frame ) page element is available under the “Media” section of the Page Builder elements. Choose an IFrame source (which must be a valid URL) to render an iFrame. You can also set different properties at different breakpoints as you can in other elements.
Fixed Tagging of Files (#2381 )
In some cases, trying to tag an uploaded file in the File Manager would cause the app to break. This has now been addressed.
Changing the File Upload Limits Is Now Propagated Immediately (#2385 )
Prior to this release, changes to File Manager settings would not take immediate effect.
More specifically, if a user tried to upload a file and received the “Max file exceeded.” error message, even after incrementing the maximum file upload size limit, and then trying to re-upload the file would not work. Only after a complete page reload the user would be able to continue with the upload.
This has now been addressed. Changes to File Manager settings will take immediate effect and doing a page reload is no longer needed.
Validate Model Name Against the Existing Models (#2324 )
We added a check in the UI when creating a new model to verify that the model with same name does not exist in the system already. The check is still being run on the API side, but this way we do not need to call the API to check for the existing model.
Customize the Elasticsearch Index Settings and Mappings for Your Deployment (#2316 )We added plugins to customize your Elasticsearch Index creation for any of our applications.
To find out more, read How To Customize Elasticsearch Index.
Split the Elasticsearch Index for Each of the Locales (#2323 )
We added an option to split each Elasticsearch Index to per-locale one. In all new Webiny deployments where the Elasticsearch is used, it is the default behavior.On all old systems, if you want to change how the indexes are created, and change the existing ones, please read How To Change Elasticsearch Index Name To Contain Locale.
Add Japanese Elasticsearch Index Configuration (#2326 )
We added the Japanese Elasticsearch Index configuration for all of our applications.
@types/web is a package that contains DOM types for the majority of the web APIs used in a web browser. In your projects, it replaces
@typescript/lib-dom, which you are more familiar with in form of
lib: ["dom"] in your
tsconfig.json files. When using
@types/web, you no longer need to specify
The main reason for this change is that more and more packages out there are using this new utility package for their types, and if it ends up in your
node_moduiles, all of a sudden, all your TS builds will start failing because the two types packages are clashing. To avoid these nightmare scenarios (and we spent one whole day figuring this out), we are officially switching to
@types/web by adding it as a dependency to our
@webiny/app package. The upgrade to Webiny 5.26.0 will take care of removing the
lib: ["dom"] for you.