apostrophe
Advanced tools
Changelog
3.16.0 (2022-03-18)
data-apos-test=""
selectors for certain elements frequently selected in QA tests, such as data-apos-test="adminBar"
.insecurePasswords
option has been added to the login module. This option is deliberately named to discourage use for any purpose other than functional tests in which repeated password hashing would unduly limit performance. Normally password hashing is intentionally difficult to slow down brute force attacks, especially if a database is compromised.POST
ing a new child page with _targetId: '_home'
now works properly in combination with _position: 'lastChild'
.Changelog
3.15.0 (2022-03-02)
Changelog
3.14.2 (2022-02-27)
Changelog
3.14.1 (2022-02-25)
_children
feature. A one-time migration is included to reconnect improperly replicated versions of the same parked pages. This runs automatically, no manual action is required. Thanks to justyna1 for identifying the issue.Changelog
3.14.0 (2022-02-22)
req.session
. This is acceptable because the real purpose of the CSRF check is simply to verify that the browser has sent the cookie at all, which it will not allow a cross-origin script to do.req.session
is actually used or a user logs in. Again, this reduces complications for those implementing caching strategies.express-cache-on-demand
lib to make similar and concurrent requests on pieces and pages faster.beforeUpdate
and beforeSave
events.@apostrophecms/piece-page-type
, the "show page" URLs for individual pieces should not contain two slashes before the piece slug. Thanks to Martí Bravo for the fix.afterPasswordVerified
login steps.@apostrophecms/asset:build
task properly in production.start
replaced with flex-start
to address SCSS warnings.Changelog
3.13.0 - 2022-02-04
requirements
feature, which can be extended in modules that improve
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 new askForConfirmation
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 for afterSubmit
for now.param
property in serveNotFound
. This fixes a problem where page titles using diacritics triggered false 404 errors.