Apostrophe 3.13.0 #3649
agilbert
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
-
Hi everyone,
One month of 2022 is in the books - I hope it was a great January for everyone. Today we shipped our latest release of Apostrophe features and modules, and I’m happy to share some details on those with you all.
The release includes some new hooks in the core of Apostrophe to support customizations of the login experience. We’re using these hooks in two new modules that have been shipped as beta releases.
Following the release of our Passport Bridge module in January, we’re excited to make these additional security enhancements available as open source modules, and hope that other developers are able to leverage the new hooks in the core to extend the login behavior of Apostrophe in helpful ways.
As always, read on for the full release notes, and enjoy the weekend 🌞
Apostrophe 3.13.0
Adds
requirements
feature, which can be extended in modules thatimprove
the@apostrophecms/login
module. These requirements are not imposed for single sign-on logins via@apostrophecms/passport-bridge
. See the documentation for more information.i18n/
folder. Thanks to Michael Huna for the contribution.afterPasswordVerified
requirements one by one when emitting done event, allows to manage errors ans success before to go to the next requirement. Stores and validate each requirement in the token. Checks the newaskForConfirmation
requirement option to go to the next step when emitting done event or waiting for the confirm event (in order to manage success messages). Removes support forafterSubmit
for now.Fixes
param
property inserveNotFound
. This fixes a problem where page titles using diacritics triggered false 404 errors.Apostrophe 3.x modules
content-upgrader 3.0.0-beta
defaultLocale
option withmapLocale
, which defaults to mappingdefault
toen
, as that's the right thing to do for projects with or without workflow in most cases, and allows for a broader remapping if needed. Clarified documentation on how this works and implemented it for the case where workflow is enabled for the first time.visibility
property is now set, as required in A3. Ifpublished
wastrue
it is set topublic
, otherwise tologinRequired
. While the two features are not identical this does a good job of avoiding premature public access to migrated content.prefixes
option._id
for every exportedarea
.aposUsersSafe
collection from 2.x to 3.x, either.form 1.0.0
Fixes
Adds
login-recaptcha 1.0.0-beta
login-totp 1.0.0-beta
multisite 3.2.1
privateDashboards
option is enabled.Apostrophe 2.220.8
Other modules
sanitize-html 2.7.0
<img />
tags. Thanks to Zade Viggers.Beta Was this translation helpful? Give feedback.
All reactions