Apostrophe 3.31.0: Widget placeholder and misc. fixes #3925
BoDonkey
announced in
Release Notes
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Howdy All!
This release cycle improved the Editor experience once again! Widget placeholders allow visualization of widget content on the page before any editing. Editors can now more easily select just the right widget to get the look they want. Developers can elect to use the default placeholder content or substitute their own for both core and custom widgets.
The popular
sanitize-html
package got a fix from community member Kedar Chandrayan. This is the third contribution by this individual, with one still in the pull request pipeline. Thanks!Moving into our next release cycle, we will be looking to achieve greater parity between A2 and A3 with the reintroduction of the password recovery link on the login page. Additionally, we are making build enhancements, improving the creation of custom schema, and improving localization.
Until next time, remember: Try not. Do, or do not. There is no try. You can “save draft,” though.
Apostrophe 3.31.0
Adds
placeholder: true
andinitialModal: false
features to improve the user experience of adding widgets to the page. Checkout the Widget Placeholders documentation for more detail.Enterprise modules
@apostrophecms-pro/advanced-permission
1.2.1Changes
contributor
role to see, edit and discard submitted drafts. It fixes a regression introduced in version1.2.0
.@apostrophecms/multisite
3.8.2Changes
baseUrl
in uploadfs URLs when using the local storage backend.Apostrophe 2.x modules
apostrophe-workflow
2.40.1This module adds powerful workflow and localization capabilities to Apostrophe. As a workflow system it provides for a draft version of every document, so that changes do not immediately "go live." As a localization system it provides for documents to exist in several locales, allowing for easy internationalization.
Fixes
Utilities
sanitize-html
2.7.3This module provides a simple HTML sanitizer with a clear API.
Fixes
false
, then do not assume that all tags are allowed. Rather, allow no tags in this case, to be on the safe side. This matches the existing documentation and fixes issue #176. Thanks to Kedar Chandrayan for the fix.Beta Was this translation helpful? Give feedback.
All reactions