Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
This PR documents the new redirectFailedUppercaseUrls option of the @apostrophecms/page module. Closes PRO-3538.
What are the specific steps to test this change?
For example:
Run the website and log in as an admin
Open a piece manager modal and select several pieces
Click the "Archive" button on the top left of the manager and confirm that it should proceed
Check that all pieces have been archived properly
Build the navigation
Check the page module options section (/reference/modules/page.html#options) and specific redirectFailedUppercaseUrls section (/reference/modules/page.html#redirectfaileduppercaseurls) for accuracy
What kind of change does this PR introduce?
(Check at least one)
[ ] Bug fix
[ ] New feature
[ ] Refactor
[X] Documentation
[ ] Build-related changes
[ ] Other
Make sure the PR fulfills these requirements:
[X] It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
[ ] The changelog is updated
[ ] Related documentation has been updated
[ ] Related tests have been updated
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
linear[bot]
commented
1 year ago
Summary
Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
This PR documents the new
redirectFailedUppercaseUrlsoption of the@apostrophecms/pagemodule. Closes PRO-3538.What are the specific steps to test this change?
For example:
What kind of change does this PR introduce?
(Check at least one)
Make sure the PR fulfills these requirements:
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information: