The software is finished -- and by finished, we mean there are no show-stopping, little-children-killing bugs in it. That we know of. There are probably numerous lower-priority bugs triaged into the next point release or service pack, as well.
@@ -9,13 +9,13 @@ More information about `dotnet new` can be found at <https://docs.microsoft.com/
Once the .NET Core SDK has been installed, type the following command to install the templates for creating Orchard Core web applications:
```CMD
dotnet new -i OrchardCore.ProjectTemplates::1.4.0
dotnet new -i OrchardCore.ProjectTemplates::1.5.0
```
This will use the most stable release of Orchard Core. In order to use the latest `main` branch of Orchard Core, the following command can be used:
```CMD
dotnet new -i OrchardCore.ProjectTemplates::1.4.0-* --nuget-source https://nuget.cloudsmith.io/orchardcore/preview/v3/index.json
dotnet new -i OrchardCore.ProjectTemplates::1.5.0-* --nuget-source https://nuget.cloudsmith.io/orchardcore/preview/v3/index.json
```
## Create a new website
...
...
@@ -25,7 +25,7 @@ dotnet new -i OrchardCore.ProjectTemplates::1.4.0-* --nuget-source https://nuget
#### Generate an Orchard Cms Web Application
!!! warning
Due to a bug in the current published version, the following `dotnet new` commands will require the extra argument `--orchard-version 1.4.0`. For instance, instead of typing `dotnet new occms` use `dotnet new occms --orchard-version 1.4.0`
Due to a bug in the current published version, the following `dotnet new` commands will require the extra argument `--orchard-version 1.5.0`. For instance, instead of typing `dotnet new occms` use `dotnet new occms --orchard-version 1.5.0`
```CMD
dotnet new occms
...
...
@@ -47,7 +47,7 @@ Options:
-ov|--orchard-version Specifies which version of Orchard Core packages to use.
string - Optional
Default: 1.4.0
Default: 1.5.0
```
Logging can be ignored with this command:
...
...
@@ -140,7 +140,7 @@ Options:
-ov|--orchard-version Specifies which version of Orchard Core packages to use.
@@ -18,7 +18,7 @@ There are different ways to create sites and modules for Orchard Core. You can l
In this guide we will use our [Code Generation Templates](../../getting-started/templates/). You can install the latest stable release of the templates using this command:
```dotnet new -i OrchardCore.ProjectTemplates::1.4.0-*```
```dotnet new -i OrchardCore.ProjectTemplates::1.5.0-*```
!!! note
To use the development branch of the template add `--nuget-source https://nuget.cloudsmith.io/orchardcore/preview/v3/index.json`
This release contains security vulnerability fixes. It is recommended you update your existing Orchard Core deployments with this version.
## Breaking Changes
* The `OrchardCore_Media_AmazonS3` config section was changed: `RegionEndpoint` was renamed to `Region` and extracted from `Credentials` section to the root section of `OrchardCore_Media_AmazonS3`, `AccessKeyId` was renamed to `AccessKey`, `ProfileName` was renamed to `Profile`. See [this pull request](https://github.com/OrchardCMS/OrchardCore/pull/11871) for details.
...
...
@@ -58,4 +62,12 @@ ManageIndexes will be now ManageLuceneIndexes
|--------|--------|--------|
| Indexed | Indexed | Indexed meant "Keyword" in Lucene so we migrated these to "Keyword" in the content index settings.
| Analyzed | Keyword | The Analyzed option is removed. Everything that was set as analyzed doesn't need migration because it is now the default. |
| Stored | Stored | Nothing to do. Should work as before |
\ No newline at end of file
| Stored | Stored | Nothing to do. Should work as before |
## YesSQL breaking changes
YesSql is now using the new SQL client which encrypts the connection by default.
If the SQL Server does not have a trusted SSL certificate and you would and want to continue using encrypted communicated using the untrusted server, add `TrustServerCertificate=True` to the connection string.
If you do not want to encrypt the communication at all, you can use `Encrypt=false`.
