From f698a0d8c178281cea94882323d28d33b521fb3c Mon Sep 17 00:00:00 2001 From: hishamco Date: Tue, 1 Nov 2022 17:06:41 +0300 Subject: [PATCH] Fix docs branch --- src/OrchardCore.Modules/OrchardCore.Tenants/Manifest.cs | 2 +- src/docs/topics/publishing-releases/README.md | 8 ++++---- .../cypress-commands/README.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/OrchardCore.Modules/OrchardCore.Tenants/Manifest.cs b/src/OrchardCore.Modules/OrchardCore.Tenants/Manifest.cs index 21d360e7f6b..c2094cbd2fb 100644 --- a/src/OrchardCore.Modules/OrchardCore.Tenants/Manifest.cs +++ b/src/OrchardCore.Modules/OrchardCore.Tenants/Manifest.cs @@ -26,7 +26,7 @@ [assembly: Feature( Id = "OrchardCore.Tenants.Distributed", Name = "Distributed Tenants", - Description = "Keeps in sync tenants states, needs a distributed cache e.g. 'Redis Cache' and a stateless configuration, see: https://docs.orchardcore.net/en/dev/docs/reference/core/Shells/index.html", + Description = "Keeps in sync tenants states, needs a distributed cache e.g. 'Redis Cache' and a stateless configuration, see: https://docs.orchardcore.net/en/latest/docs/reference/core/Shells/index.html", Category = "Distributed", DefaultTenantOnly = true )] diff --git a/src/docs/topics/publishing-releases/README.md b/src/docs/topics/publishing-releases/README.md index fbe329e047b..d1080c7c988 100644 --- a/src/docs/topics/publishing-releases/README.md +++ b/src/docs/topics/publishing-releases/README.md @@ -34,10 +34,10 @@ Update the source so everything looks like on the new version. Make sure everything works all right. - [ ] Make sure that [OrchardCore.Samples works](https://github.com/OrchardCMS/OrchardCore.Samples). -- [ ] Test the [guides](https://docs.orchardcore.net/en/dev/docs/guides/) with the NuGet packages from the Cloudsmith feed (branches under `release/` are automatically published too). Test at least the following guides: - - [Creating a modular ASP.NET Core application](https://docs.orchardcore.net/en/dev/docs/guides/create-modular-application-mvc/) - - [Creating an Orchard Core CMS website](https://docs.orchardcore.net/en/dev/docs/guides/create-cms-application/) - - [Creating a new decoupled CMS Website](https://docs.orchardcore.net/en/dev/docs/guides/decoupled-cms/) +- [ ] Test the [guides](https://docs.orchardcore.net/en/latest/docs/guides/) with the NuGet packages from the Cloudsmith feed (branches under `release/` are automatically published too). Test at least the following guides: + - [Creating a modular ASP.NET Core application](https://docs.orchardcore.net/en/latest/docs/guides/create-modular-application-mvc/) + - [Creating an Orchard Core CMS website](https://docs.orchardcore.net/en/latest/docs/guides/create-cms-application/) + - [Creating a new decoupled CMS Website](https://docs.orchardcore.net/en/latest/docs/guides/decoupled-cms/) ### Prepare and publish Orchard Core Translations diff --git a/test/OrchardCore.Tests.Functional/cypress-commands/README.md b/test/OrchardCore.Tests.Functional/cypress-commands/README.md index d49ddb9d416..515ac762580 100644 --- a/test/OrchardCore.Tests.Functional/cypress-commands/README.md +++ b/test/OrchardCore.Tests.Functional/cypress-commands/README.md @@ -32,7 +32,7 @@ First thing to do to use this package is to add the credentials to be used to in ### Orchard default tenant -This library assumes that you will be testing OrchardCore by leveraging the [Tenants](https://docs.orchardcore.net/en/dev/docs/glossary/#tenant) feature. You **must** create a test that runs first and sets up the Default tenant using the [Software as a service ](https://docs.orchardcore.net/en/dev/docs/getting-started/starter-recipes/#saas-recipe-with-thetheme) setup recipe. +This library assumes that you will be testing OrchardCore by leveraging the [Tenants](https://docs.orchardcore.net/en/latest/docs/glossary/#tenant) feature. You **must** create a test that runs first and sets up the Default tenant using the [Software as a service ](https://docs.orchardcore.net/en/dev/docs/getting-started/starter-recipes/#saas-recipe-with-thetheme) setup recipe. To do so we suggest you create a test named `integration\000-setup-saas-site.js` with the following contents.