From 41d9b400c218140c4262bdd2924933d72cb8e594 Mon Sep 17 00:00:00 2001 From: brynwhyman Date: Wed, 6 Oct 2021 11:28:47 +1300 Subject: [PATCH 1/2] DOCS clarify 'cms recipe' docs Addressing feedback to clarify reference to 'CWP CMS recipe' --- docs/en/03_Upgrading/03_Migrating_off_CWP.md | 16 ++++++++++------ docs/en/04_Changelogs/4.9.0.md | 2 +- 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/docs/en/03_Upgrading/03_Migrating_off_CWP.md b/docs/en/03_Upgrading/03_Migrating_off_CWP.md index f0080dfcf..98ca12ac8 100644 --- a/docs/en/03_Upgrading/03_Migrating_off_CWP.md +++ b/docs/en/03_Upgrading/03_Migrating_off_CWP.md @@ -1,15 +1,15 @@ --- -title: Migrating off CWP -summary: Migrate your project off the Common Web Platform v2 +title: Migrating off CWP CMS recipe +summary: Migrate your project off the Common Web Platform CMS recipe v2 --- -# Migrate your project off the Common Web Platform v2 +# Migrate your project off the Common Web Platform CMS recipe v2 -Until November 2021, Silverstripe Ltd maintained a specialised version of the Silverstripe CMS project for the New Zealand Government and related New Zealand public-sector agencies. This version was called _Common Web Platform_ (CWP for short). +Until September 2021, Silverstripe Ltd maintained a specialised version of Silverstripe CMS for the New Zealand Government and related New Zealand public-sector agencies. This version was called _Common Web Platform_ (CWP for short). -The CWP CMS release has been discontinued. CWP projects who wish to continue to receive updates must migrate their code base off the latest CWP release back to the regular Silverstripe CMS release. +The CWP CMS release has been discontinued. CWP projects who wish to continue to receive CMS updates must migrate their code base off the latest CWP CMS release back to the regular Silverstripe CMS release. -## Steps to migrate away from CWP +## Steps to migrate away from CWP recipe Before you begin this process you must identify which version of Silverstripe CMS Recipe you want to upgrade to. You can upgrade to [Silverstripe CMS Recipe 4.9.0](/changelogs/4.9.0/) or greater. @@ -36,6 +36,10 @@ Once you've completed the clean up, you should run a `composer update` to sync u ## Questions +### Will this have an effect on the features of my project? + +Neither the steps to inline now deprecated recipes, nor replacing those that have a new package name will affect the feature-set of your project. It will also have no effect on how your project is currently hosted. This change simply focuses on ensuring that your project continues to receive CMS upgrades through the standard Silverstripe CMS release line - no longer following the ‘CWP 2.x’ versioning convention. + ### What constraint should I use in my requirement version? That really depends on how comfortable your organisiation is with automatically applying updates to your Silverstripe CMS project. diff --git a/docs/en/04_Changelogs/4.9.0.md b/docs/en/04_Changelogs/4.9.0.md index 871bb24db..68efb0b46 100644 --- a/docs/en/04_Changelogs/4.9.0.md +++ b/docs/en/04_Changelogs/4.9.0.md @@ -130,7 +130,7 @@ While it is still advised that you perform your own due diligence when upgrading This release marks the first release for Common Web Platform projects to eject out of managing projects in the CWP 2.x version line and to begin following the standard CMS 4.x version line, by adopting the CMS Recipe. -Review the [Migrate your project off the Common Web Platform v2](/Upgrading/Migrating_off_CWP) guidance to learn how to transition from CWP. +Review the [Migrate your project off the Common Web Platform CMS recipe](/Upgrading/Migrating_off_CWP) guidance to learn how to transition from CWP. ## Dropping support for Internet Explorer 11{#ie11eol} From 9a119a35816004f0fc7587a8f8b08093f11c6c9b Mon Sep 17 00:00:00 2001 From: brynwhyman Date: Wed, 6 Oct 2021 12:43:43 +1300 Subject: [PATCH 2/2] DOCS add release announcement link to changelog I've also suggested a note to an existing Chrome lazy-loading bug --- docs/en/04_Changelogs/4.9.0.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/en/04_Changelogs/4.9.0.md b/docs/en/04_Changelogs/4.9.0.md index 68efb0b46..f8fd4b6ed 100644 --- a/docs/en/04_Changelogs/4.9.0.md +++ b/docs/en/04_Changelogs/4.9.0.md @@ -92,6 +92,8 @@ A full list of module versions included in CMS Recipe 4.9.0 is provided below. W Upgrading to Silverstripe CMS Recipe 4.9.0 is recommended for all sites. This upgrade can be carried out by any development team familiar with Silverstripe. +In addition to the below, have a read of the [CMS 4.9 release announcement](https://www.silverstripe.org/blog/cms-4-9-is-here/). + - [Security considerations](#security-considerations) - [Security audit and regression test](#audit) - [For development teams of Common Web Platform projects](#cwp-end) @@ -119,7 +121,6 @@ We have provided a high-level severity rating of the vulnerabilities below based If your site has a custom GraphQL 3 ItemQuery/ListQuery Scaffolder implementation that relies on having no permission check, you will need to add a custom permission checker to bypass the `canView()` check. See the [security announcement](https://www.silverstripe.org/download/security-releases/CVE-2021-28661) for implementation details. - ## Regression test and Security audit{#audit} This release has been comprehensively regression tested and passed to a third party for a security-focused audit. @@ -211,6 +212,8 @@ Content authors can disable lazy loading on images added via the HTML editor fie Consult the [Insert images](https://userhelp.silverstripe.org/en/4/creating_pages_and_content/creating_and_editing_content/inserting_images/#lazy-loading) article in the Silverstripe CMS user help for detailed instructions. +*Also note:* There is a [long-standing bug in Google Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=875403) that will prevent images that have not yet been in view (and loaded) from being included if a user chooses to print the page. This is something that site owners should be made aware of. + ### Manage your CMS sessions across devices {#session-manager} The [session manager module](https://github.com/silverstripe/silverstripe-session-manager) is a new security focused feature which allows a CMS user to view and manage their active sessions in the CMS within the "My profile" section of the CMS (/admin/myprofile). They can see the device details behind each session and have the ability to revoke these sessions. This new module has been added to `silverstripe/recipe-cms` which is the recommended method of managing Silverstripe CMS dependencies in a project.