From 9313e06a4d532dd73ad5ae3a2158b4e6927677a7 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:06:37 +0000 Subject: [PATCH 01/20] corrrects some spelling and filename errors in `source-code.md` in v10, 12, 13 --- 10/umbraco-cms/fundamentals/code/source-control.md | 10 +++++----- 12/umbraco-cms/fundamentals/code/source-control.md | 4 ++-- 13/umbraco-cms/fundamentals/code/source-control.md | 4 ++-- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/10/umbraco-cms/fundamentals/code/source-control.md b/10/umbraco-cms/fundamentals/code/source-control.md index 0c4619d41c3..8d13d5dd0e1 100644 --- a/10/umbraco-cms/fundamentals/code/source-control.md +++ b/10/umbraco-cms/fundamentals/code/source-control.md @@ -63,15 +63,15 @@ appsettings-schema.json ## Umbraco CMS .NETCore ## -# Dont commit Umbraco TEMP folder containing Examine Indexes, NuCache etc +# Don't commit Umbraco TEMP folder containing Examine Indexes, NuCache etc **/umbraco/Data/TEMP/ -# Dont commit files that are generated and cached from the default ImageSharp location +# Don't commit files that are generated and cached from the default ImageSharp location **/umbraco/mediacache/ # Umbraco backoffice language files # Nuget package Umbraco.Cms.StaticAssets will copy them in during dotnet build -# Customize langguage files in /config/lang/{language}.user.xml +# Customize language files in /config/lang/{language}.user.xml **/umbraco/config/lang/ # JSON Schema file for appsettings @@ -213,9 +213,9 @@ Any supporting custom code for your application should be in version control, eg #### Config -Your site's `apsettings.json` and `appsettings.Development.json` files contain the configuration for your Umbraco site. +Your site's `appsettings.json` and `appsettings.Development.json` files contain the configuration for your Umbraco site. -In general, it is recommended to add these to source control. When you do this, be sure that the file(s) doesn't contain any secrets, like API keys and connection strings. These can be added as needed, but ommitted from any commits made to source control. +In general, it is recommended to add these to source control. When you do this, be sure that the file(s) doesn't contain any secrets, like API keys and connection strings. These can be added as needed, but omitted from any commits made to source control. #### DocumentType - Backoffice Structure Changes diff --git a/12/umbraco-cms/fundamentals/code/source-control.md b/12/umbraco-cms/fundamentals/code/source-control.md index 14349242a4a..226242e7641 100644 --- a/12/umbraco-cms/fundamentals/code/source-control.md +++ b/12/umbraco-cms/fundamentals/code/source-control.md @@ -139,9 +139,9 @@ Any supporting custom code for your application should be in version control, eg #### Config -Your site's `apsettings.json` and `appsettings.Development.json` files contain the configuration for your Umbraco site. +Your site's `appsettings.json` and `appsettings.Development.json` files contain the configuration for your Umbraco site. -In general, it is recommended to add these to source control. When you do this, be sure that the file(s) doesn't contain any secrets, like API keys and connection strings. These can be added as needed, but ommitted from any commits made to source control. +In general, it is recommended to add these to source control. When you do this, be sure that the file(s) doesn't contain any secrets, like API keys and connection strings. These can be added as needed, but omitted from any commits made to source control. #### DocumentType - Backoffice Structure Changes diff --git a/13/umbraco-cms/fundamentals/code/source-control.md b/13/umbraco-cms/fundamentals/code/source-control.md index 14349242a4a..226242e7641 100644 --- a/13/umbraco-cms/fundamentals/code/source-control.md +++ b/13/umbraco-cms/fundamentals/code/source-control.md @@ -139,9 +139,9 @@ Any supporting custom code for your application should be in version control, eg #### Config -Your site's `apsettings.json` and `appsettings.Development.json` files contain the configuration for your Umbraco site. +Your site's `appsettings.json` and `appsettings.Development.json` files contain the configuration for your Umbraco site. -In general, it is recommended to add these to source control. When you do this, be sure that the file(s) doesn't contain any secrets, like API keys and connection strings. These can be added as needed, but ommitted from any commits made to source control. +In general, it is recommended to add these to source control. When you do this, be sure that the file(s) doesn't contain any secrets, like API keys and connection strings. These can be added as needed, but omitted from any commits made to source control. #### DocumentType - Backoffice Structure Changes From 1fe4ceeefbe7ab1e1540f54945a41784f98f1b66 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:16:32 +0000 Subject: [PATCH 02/20] Typo corrections in Umb Heartcore directory --- umbraco-heartcore/README.md | 2 +- umbraco-heartcore/api-documentation/redirect.md | 2 +- .../dot-net-core/content-management-sample.md | 2 +- umbraco-heartcore/client-libraries/node-js.md | 2 +- .../getting-started/backoffice-users-and-api-keys.md | 2 +- .../getting-started/creating-a-heartcore-project.md | 6 +++--- .../deployment-workflow/content-transfer.md | 2 +- .../deployment-workflow/structure-deployment.md | 2 +- umbraco-heartcore/getting-started/using-the-forms-api.md | 4 ++-- .../tutorials/creating-a-custom-grid-editor.md | 2 +- umbraco-heartcore/tutorials/querying-with-graphql.md | 8 ++++---- umbraco-heartcore/versions-and-updates.md | 2 +- 12 files changed, 18 insertions(+), 18 deletions(-) diff --git a/umbraco-heartcore/README.md b/umbraco-heartcore/README.md index c6fe4b65934..d681519e49b 100644 --- a/umbraco-heartcore/README.md +++ b/umbraco-heartcore/README.md @@ -2,7 +2,7 @@ Umbraco Heartcore is a headless Software As A Service (SAAS) offered by Umbraco. The service enables you to create and manage content and media in the Umbraco backoffice and make it available to any platforms, devices, channels and so forth. -
Getting startedGet started working with Umbraco Heartcoreheadless.pngcontent.md
Umbraco Heartcore APIsSee the different APIs available in Umbraco Heartcorecode (1) (1) (1).pngBroken link
Client librariesTest out your Umbraco Hearcore project with the premade client librariesdevices.pngBroken link
+
Getting startedGet started working with Umbraco Heartcoreheadless.pngcontent.md
Umbraco Heartcore APIsSee the different APIs available in Umbraco Heartcorecode (1) (1) (1).pngBroken link
Client librariesTest out your Umbraco Heartcore project with the pre-made client librariesdevices.pngBroken link
{% embed url="https://www.youtube.com/embed/Rujaw1VWUaQ?rel=0" %} How to create a Heartcore Trial diff --git a/umbraco-heartcore/api-documentation/redirect.md b/umbraco-heartcore/api-documentation/redirect.md index df3fb4d6443..6ec00873340 100644 --- a/umbraco-heartcore/api-documentation/redirect.md +++ b/umbraco-heartcore/api-documentation/redirect.md @@ -33,7 +33,7 @@ Umb-Project-Alias: {project-alias} ## Errors -If an error occours, you will receive a HTTP status code along with an API error code and an error message in the response body. +If an error occurs, you will receive a HTTP status code along with an API error code and an error message in the response body. | Status Code | Error Code | Message | | ----------- | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/umbraco-heartcore/client-libraries/dot-net-core/content-management-sample.md b/umbraco-heartcore/client-libraries/dot-net-core/content-management-sample.md index 1f018fe3fd6..7e7007ca82d 100644 --- a/umbraco-heartcore/client-libraries/dot-net-core/content-management-sample.md +++ b/umbraco-heartcore/client-libraries/dot-net-core/content-management-sample.md @@ -29,7 +29,7 @@ This sample guide will cover how you can access and work with the [Content Manag } ``` {% endcode %} -3. Register the `ContentManagementService` to your dependency injection container. The registration of the `ContentManagementService` is handled by the `AddUmbracoHeartocore` extension method. +3. Register the `ContentManagementService` to your dependency injection container. The registration of the `ContentManagementService` is handled by the `AddUmbracoHeartcore` extension method. {% code title="Program.cs / Startup.cs" %} ```` diff --git a/umbraco-heartcore/client-libraries/node-js.md b/umbraco-heartcore/client-libraries/node-js.md index be1a44b287b..856eca18039 100644 --- a/umbraco-heartcore/client-libraries/node-js.md +++ b/umbraco-heartcore/client-libraries/node-js.md @@ -29,7 +29,7 @@ const { Client } = require('@umbraco/headless-client') //Connecting to the Heartcore project on Cloud const client = new Client({ projectAlias: 'demo-headless' }) -//If protection is turned on you will have to add the API Key that has been asigned to your user +//If protection is turned on you will have to add the API Key that has been assigned to your user client.setAPIKey('') //Create an async function to fetch all content from the root of the project diff --git a/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md b/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md index 1bcba5ebaef..d2fe35fd393 100644 --- a/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md +++ b/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md @@ -38,4 +38,4 @@ You are able to see a list of all your created API Keys and all relevant informa ![List of all APIs](images/listOfAPIs.png) - + diff --git a/umbraco-heartcore/getting-started/creating-a-heartcore-project.md b/umbraco-heartcore/getting-started/creating-a-heartcore-project.md index adafff7ea48..f9e5b41427d 100644 --- a/umbraco-heartcore/getting-started/creating-a-heartcore-project.md +++ b/umbraco-heartcore/getting-started/creating-a-heartcore-project.md @@ -121,7 +121,7 @@ So far, we've created a single Document Type with some text fields and a media p We will now expand on our site by adding a **Document Type Collection**. 1. Right-click on the Document Types folder and choose **+ Create...**. - * Or select the three elipses on the right, when hovering the folder. + * Or select the three ellipses on the right, when hovering the folder. 2. Choose the second option: **Document Type Collection...**. {% hint style="info" %} @@ -184,7 +184,7 @@ In this next step of the tutorial, we will start creating content. The content w 1. Go to the **Content** section. 2. Right-click on the Content tree and choose **+ Create...**. - * Or select the three elipses on the right, when hovering the Content tree. + * Or select the three ellipses on the right, when hovering the Content tree. ![Creating our first content node](images/Create-First-Content.png) @@ -214,7 +214,7 @@ So far, our Content section should look like this: ![Welcome to Umbraco Heartcore Content node](images/Welcome-to-Heartcore-Content.png) 1. Right-click the root node, _Welcome to Umbraco Heartcore_, and choose **Create...** - * Or select the three elipses next to the node when hovering. + * Or select the three ellipses next to the node when hovering. 2. Select to create a **Blog Area**. 3. Give it a name: _Blog_. 4. (Optional) Add some text to the _BlogDescription_ property. diff --git a/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md b/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md index 7869008a05d..929b4a9e725 100644 --- a/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md +++ b/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md @@ -16,4 +16,4 @@ The screenshot above is from the Content section on a Development environment. R **Queue for transfer** gives you the option to queue all content in the Content tree for transfer to the next environment (Staging or Live). It is also possible to right-click single nodes in the content structure in order to only queue some of it for transfer. -**Restore** gives you the option to restore all content from environments right of the current evironment. In some cases you might not want to restore all content as once, in which case you should use the _Partial restore_ option instead, which you can find by right-clicking a node in the content tree. +**Restore** gives you the option to restore all content from environments right of the current environment. In some cases you might not want to restore all content as once, in which case you should use the _Partial restore_ option instead, which you can find by right-clicking a node in the content tree. diff --git a/umbraco-heartcore/getting-started/deployment-workflow/structure-deployment.md b/umbraco-heartcore/getting-started/deployment-workflow/structure-deployment.md index 606daad692a..c6ab1287342 100644 --- a/umbraco-heartcore/getting-started/deployment-workflow/structure-deployment.md +++ b/umbraco-heartcore/getting-started/deployment-workflow/structure-deployment.md @@ -12,6 +12,6 @@ A deployment from one environment (source) to another (target) goes through the 2. If changes are found, these are pulled down and merged into the source environment 3. The changes on the source environment is then pushed to the target environment -This process migth take a few minutes, depending on the amount of changes being deployed. +This process might take a few minutes, depending on the amount of changes being deployed. Once your structure has been deployed, it will be possible to transfer your content and media as well. This is done from the Umbraco Backoffice - read more about this in the [Content transfer/restore article](content-transfer.md). diff --git a/umbraco-heartcore/getting-started/using-the-forms-api.md b/umbraco-heartcore/getting-started/using-the-forms-api.md index 2cc7dfaa45c..aeff75d1b0c 100644 --- a/umbraco-heartcore/getting-started/using-the-forms-api.md +++ b/umbraco-heartcore/getting-started/using-the-forms-api.md @@ -188,7 +188,7 @@ Below is an example of the payload body when sending an entry back to the form r ```json { - "name": "Jonh Smith", + "name": "John Smith", "email": "johnsmith@example.org", "dataConsent": "on" } @@ -226,7 +226,7 @@ Given that the form contains a Name, Email and Data Content field we can submit ```typescript const entry = { - "name": "Jonh Smith", + "name": "John Smith", "email": "johnsmith@example.org", "dataConsent": "on" } diff --git a/umbraco-heartcore/tutorials/creating-a-custom-grid-editor.md b/umbraco-heartcore/tutorials/creating-a-custom-grid-editor.md index beb334114f5..3ccdeeae2e7 100644 --- a/umbraco-heartcore/tutorials/creating-a-custom-grid-editor.md +++ b/umbraco-heartcore/tutorials/creating-a-custom-grid-editor.md @@ -395,7 +395,7 @@ Now that we have a working editor, let's add a couple of images to our page. Whe Note down the **Id** from the **Info** tab. We will need that in a bit. * Go to the **Settings** section. -* Exapnd the **Headless** node. +* Expand the **Headless** node. * Open the [API Browser](../getting-started/api-browser.md) * Type in `https://cdn.umbraco.io/content/` in the Explorer URL bar, replacing `` with the id we copied before. * Click **Go!**. diff --git a/umbraco-heartcore/tutorials/querying-with-graphql.md b/umbraco-heartcore/tutorials/querying-with-graphql.md index 218489f9e7b..6d5fca6b23a 100644 --- a/umbraco-heartcore/tutorials/querying-with-graphql.md +++ b/umbraco-heartcore/tutorials/querying-with-graphql.md @@ -98,7 +98,7 @@ Add a new group called **Unique Selling Points** with the following properties: | Name | Alias | Property Editor | Property Editor Configuration | | --------------------- | ------------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Title | uniqueSellingPointsTitle | Textstring |

Document Types:
Use defaulst

| +| Title | uniqueSellingPointsTitle | Textstring |

Document Types:
Use defaults

| | Unique Selling Points | uniqueSellingPoints | Nested Content |

Document Types:
Element Type: Unique Selling Point, Group: Content, Template: {{title}}
Confirm Deletes: checked
Show icons: not checked
Hide label: checked

| ![Nested Content Configured with Unique Selling Points](images/nested-content-unique-selling-points.png) @@ -274,7 +274,7 @@ Since Nested Content is an interface named `Element` we can query the fields by Now try to write a query that fetches the `title`, `text`, `link` and `image` fields for the Unique Selling Points property. -### Quering the Main Navigation and Footer +### Querying the Main Navigation and Footer The only thing we are missing now to be able to render the complete page is the main navigation and the footer. @@ -417,7 +417,7 @@ Now that we have all the individual parts we can combine it all into a single qu query($url: String!) { content(url: $url) { ...Hero - ...UnigueSellingPoints + ...UniqueSellingPoints ...Elements } global: frontpage(url: "/home/") { @@ -462,7 +462,7 @@ fragment Elements on ElementsComposition { } } -fragment UnigueSellingPoints on UniqueSellingPointsComposition { +fragment UniqueSellingPoints on UniqueSellingPointsComposition { uniqueSellingPointsTitle uniqueSellingPoints { ... on UniqueSellingPoint { diff --git a/umbraco-heartcore/versions-and-updates.md b/umbraco-heartcore/versions-and-updates.md index b444cbe8632..6e3ec68c72e 100644 --- a/umbraco-heartcore/versions-and-updates.md +++ b/umbraco-heartcore/versions-and-updates.md @@ -7,7 +7,7 @@ Umbraco HQ will regularly be adding new features to the CMS and new capabilities We follow semver in terms of versioning, which means you can be sure that existing APIs will continue to work as expected without breaking. If a breaking change is required then the major version will be incremented, but the previous major version will continue to work. {% hint style="info" %} -For API calls, it's advisable **to employ the `api-version` header to indicate the API version you intend to use**. If no version is specified the latest vesrion of the API will be used. +For API calls, it's advisable **to employ the `api-version` header to indicate the API version you intend to use**. If no version is specified the latest version of the API will be used. Learn more about which versions of the API is available as well as what version each endpoint uses in the[ Umbraco Heartcore API Documentation.](api-documentation/) {% endhint %} From b3701e9e52ed365c1d229a611140a22b31df8ddb Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:27:37 +0000 Subject: [PATCH 03/20] Umbraco Cloud typo corrections --- umbraco-cloud/databases/cloud-database/README.md | 2 +- umbraco-cloud/deployment/deploy-dashboard.md | 2 +- .../getting-started/migrate-existing-site/README.md | 4 ++-- .../getting-started/the-umbraco-cloud-portal/README.md | 4 ++-- .../the-umbraco-cloud-portal/organizations.md | 4 ++-- .../manual-upgrades/manual-upgrade-deploy.md | 2 +- umbraco-cloud/security.md | 4 ++-- umbraco-cloud/set-up/legacy-umbraco-visual-studio-setup.md | 2 +- .../set-up/manage-subscriptions/new-shop/README.md | 2 +- .../set-up/project-settings/umbraco-cicd/Troubleshooting.md | 6 +++--- .../set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md | 2 +- umbraco-cloud/set-up/project-settings/usage.md | 6 +++--- .../troubleshooting/deployments/dependency-exceptions.md | 2 +- 13 files changed, 21 insertions(+), 21 deletions(-) diff --git a/umbraco-cloud/databases/cloud-database/README.md b/umbraco-cloud/databases/cloud-database/README.md index fd40c2ab8ef..0bdd3b2153c 100644 --- a/umbraco-cloud/databases/cloud-database/README.md +++ b/umbraco-cloud/databases/cloud-database/README.md @@ -27,7 +27,7 @@ Once the firewall is open, it's time to fire up SQL Management Studio and connec To connect, choose "Connect Database Engine" and copy the values from the Connection Details page on Umbraco Cloud. You'll find handy "copy" shortcut buttons to the right of each value. In the "Connect to Server" dialog in SQL Management Studio, choose "SQL Server Authentication" as the authentication type. Remember to click the "Options" button before you connect. Paste the name of your database in the "Database" input field; otherwise, security settings on Umbraco Cloud will prevent you from connecting. You can see it all in this short video: {% embed url="https://www.youtube.com/embed/yrCNsW-8_nU?rel=0" %} -How to connecto to a Umbraco Cloud Database +How to connect to to a Umbraco Cloud Database {% endembed %} ### Moving on diff --git a/umbraco-cloud/deployment/deploy-dashboard.md b/umbraco-cloud/deployment/deploy-dashboard.md index 9fd72359032..8629ee3273f 100644 --- a/umbraco-cloud/deployment/deploy-dashboard.md +++ b/umbraco-cloud/deployment/deploy-dashboard.md @@ -44,7 +44,7 @@ Running this operation will download a zip file with all the Deploy artifacts re This operation is useful if you want to move to another Umbraco instance and migrate the data with you. -

Donwload the Deploy artifacts

+

Download the Deploy artifacts

## Configuration Details diff --git a/umbraco-cloud/getting-started/migrate-existing-site/README.md b/umbraco-cloud/getting-started/migrate-existing-site/README.md index 807cdf587bd..95c9cdcd89e 100644 --- a/umbraco-cloud/getting-started/migrate-existing-site/README.md +++ b/umbraco-cloud/getting-started/migrate-existing-site/README.md @@ -136,13 +136,13 @@ Merging your existing site into the Umbraco Cloud project is a matter of moving * When copying your `\umbraco\` folder, make sure you **do not delete** the `\umbraco\Licenses\umbracoDeploy.lic` file * If you have any custom code in your project, you should copy that code over too. 2. Merge Appsettings.JSON files from your existing site with the cloud site. - * Make sure that you merge your Appsetting.JSON files with the ones from your existing site so that the settings you used are moved over to your Cloud project + * Make sure that you merge your `appsettings.json` files with the ones from your existing site so that the settings you used are moved over to your Cloud project 3. Merge your Program.cs and Startup.cs with the one from your existing site 4. Merge your `ProjectName.csproj` with the `UmbracoProject.csproj` - especially if you have any packages installed on your project. 5. If you are using SQLite * Make sure the `Umbraco.sqlite.db`, `Umbraco.sqlite.db-shm` and `Umbraco.sqlite.db-wal` files from your project replaces the ones provided with your Umbraco Cloud project * You can find them in `/umbraco/Data/Umbraco.sqlite.db` -6. If you are using a local SQL server make sure to update the connection string in the `Appsettings.JSON` for the Umbraco Cloud project. +6. If you are using a local SQL server make sure to update the connection string in the `appsettings.JSON` for the Umbraco Cloud project. That's it! Now that you've merged your existing site with the local clone of the Cloud project, make sure the project runs and verify that diff --git a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md index a30ce8953b0..20dde72eadd 100644 --- a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md +++ b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md @@ -79,7 +79,7 @@ In the [Settings](../../set-up/project-settings/) section, you will find a lot m ### Manage Subscriptions -For customers who have joined Umbraco Cloud before the 5th of May, 2021, can manage their subscriptions from Umbraco Shop. Umbraco Shop can be accessed through [Umbraco.com](https://umbraco.com). You can also click on the **Manage Subscriptions** link from the **Profile** dropdown on the Umbraco Cloud Portal. Find out more in the [Manage Subcriptions](../../set-up/manage-subscriptions/) article. +For customers who have joined Umbraco Cloud before the 5th of May, 2021, can manage their subscriptions from Umbraco Shop. Umbraco Shop can be accessed through [Umbraco.com](https://umbraco.com). You can also click on the **Manage Subscriptions** link from the **Profile** dropdown on the Umbraco Cloud Portal. Find out more in the [Manage Subscriptions](../../set-up/manage-subscriptions/) article. Customers who have joined Umbraco Cloud after the 5th of May, 2021, can manage their subscriptions directly through Umbraco Cloud. Find out more in the [Payments on Umbraco Cloud](../../set-up/manage-subscriptions/new-shop/) article. @@ -91,7 +91,7 @@ On Umbraco Cloud, you can receive an invitation from different projects. These p * Invited by * The expiration date of the invite * Invitation status -* Otions to approve, reject, or delete the invitations that have expired. +* Options to approve, reject, or delete the invitations that have expired. ![Project Invites](images/project-invites.png) diff --git a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/organizations.md b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/organizations.md index a9e9598a69a..0de06f7302a 100644 --- a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/organizations.md +++ b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/organizations.md @@ -27,7 +27,7 @@ In the **Members** section, you can view current members, pending invites, and s
-Members added to your ogranization can see different details about their organization based on the user group they are added to. Currently there are three different groups, **Read**, **Write** and **Admin**. +Members added to your organization can see different details about their organization based on the user group they are added to. Currently there are three different groups, **Read**, **Write** and **Admin**. Below you can see what each user group has access to under the organization they are a part of. Organization Members with **Admin Access** can do the following in the organization: @@ -43,7 +43,7 @@ Organization Members with **Admin Access** can do the following in the organizat * See subscriptions * See organization Members * See payment history -* Handle Multi Factor Autentication (MFA) for users +* Handle Multi Factor Authentication (MFA) for users * Handle payment methods * Change permissions for Members * Remove role from users diff --git a/umbraco-cloud/product-upgrades/manual-upgrades/manual-upgrade-deploy.md b/umbraco-cloud/product-upgrades/manual-upgrades/manual-upgrade-deploy.md index 0a5406c2b8a..cbb26713f8e 100644 --- a/umbraco-cloud/product-upgrades/manual-upgrades/manual-upgrade-deploy.md +++ b/umbraco-cloud/product-upgrades/manual-upgrades/manual-upgrade-deploy.md @@ -6,7 +6,7 @@ description: >- # Manual upgrade of Umbraco Deploy -Deploy on Coud will either be automatically upgraded with patch releases or it can be done through the portal when new minors are available. +Deploy on Cloud will either be automatically upgraded with patch releases or it can be done through the portal when new minors are available. In rare cases, Deploy might not be on the latest patch or minor and you will need to upgrade Deploy manually. diff --git a/umbraco-cloud/security.md b/umbraco-cloud/security.md index e8c66e31101..525f209c33f 100644 --- a/umbraco-cloud/security.md +++ b/umbraco-cloud/security.md @@ -52,7 +52,7 @@ You can add the header by modifying system.webServer/rewrite/outboundRules secti ``` -Alternatively this can be done in Startup.cs inside of the **ConfigueServices** method with the following C#: +Alternatively this can be done in Startup.cs inside of the **ConfigureServices** method with the following C#: ```csharp public void ConfigureServices(IServiceCollection services) @@ -80,7 +80,7 @@ In order to integrate older external applications to access Umbraco Cloud Websit For ASP.NET applications, inspect the `` element of web.config to find the version of the .NET Framework your application is using. .NET applications on .NET 4.7+ are using the OS specified TLS protocols. In Windows 8 & 10, Windows Server 2012 & 2016 TLS 1.2+ is used by default, therefore no actions necessary. .NET applications lower then 4.7 require updates to ensure they can communicate using TLS 1.2 by default. -More information specifically from Microsoft about .Net applications and TLS support can be found [in Microsofts official docs](https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#audit-your-code-and-make-code-changes). For other application frameworks/languages we encourage to lookup their respective documentations. +More information specifically from Microsoft about .Net applications and TLS support can be found [in Microsoft's official docs](https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#audit-your-code-and-make-code-changes). For other application frameworks/languages we encourage to lookup their respective documentations. ### HTTP diff --git a/umbraco-cloud/set-up/legacy-umbraco-visual-studio-setup.md b/umbraco-cloud/set-up/legacy-umbraco-visual-studio-setup.md index 723f8c55a82..3afc8ea1db0 100644 --- a/umbraco-cloud/set-up/legacy-umbraco-visual-studio-setup.md +++ b/umbraco-cloud/set-up/legacy-umbraco-visual-studio-setup.md @@ -55,7 +55,7 @@ Download the UaaS.cmd tool from [umbra.co/uaas-cmd](https://umbra.co/uaas-cmd) a {% endhint %} {% hint style="warning" %} -**Important**: Be aware if you run the Uaas.cmd tool as an adminstrator it will generate the files in your Windows/System folder. +**Important**: Be aware if you run the Uaas.cmd tool as an administrator it will generate the files in your Windows/System folder. {% endhint %} This is a recommended setup. If you don't like the setup then you can play with it and make it your own. There's nothing magic about this setup. It is adding a few files to your Umbraco Cloud website to give you a flying start to begin working with Visual Studio. diff --git a/umbraco-cloud/set-up/manage-subscriptions/new-shop/README.md b/umbraco-cloud/set-up/manage-subscriptions/new-shop/README.md index 087adeca93d..077348c1d18 100644 --- a/umbraco-cloud/set-up/manage-subscriptions/new-shop/README.md +++ b/umbraco-cloud/set-up/manage-subscriptions/new-shop/README.md @@ -18,7 +18,7 @@ To manage your subscription on Umbraco Cloud, go to the menu in the top right co You will see an overview of your organization on Umbraco Cloud. From here you can see the information about the organization. -To see the subscribtions running under your organization click on "Subscriptions" in the side menu +To see the subscriptions running under your organization click on "Subscriptions" in the side menu ![Your subscriptions](../images/subscriptions.png) diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/Troubleshooting.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/Troubleshooting.md index 2647a681fb0..251391fda07 100644 --- a/umbraco-cloud/set-up/project-settings/umbraco-cicd/Troubleshooting.md +++ b/umbraco-cloud/set-up/project-settings/umbraco-cicd/Troubleshooting.md @@ -6,16 +6,16 @@ We currently have a size limit set to 134217728 bytes or about ~128 MB. -Make sure that the package you are trying to upload does not contain anything unnessary. +Make sure that the package you are trying to upload does not contain anything unnecessary. -You can see an example of how you could zip your repository before uploading it, by refering to our [Github](samplecicdpipeline/github-actions.md) or [Azure Devops](samplecicdpipeline/azure-devops.md) samples. +You can see an example of how you could zip your repository before uploading it, by referring to our [Github](samplecicdpipeline/github-actions.md) or [Azure Devops](samplecicdpipeline/azure-devops.md) samples. ## Deployment failed ### Cannot apply update because the following packages would be downgraded: Package: Umbraco.{abc}, Version: {x.y.z} The service goes through all .csproj-files contained in the uploaded package, and compares that to the versions running in your left-most cloud environment. -We do this to try to prevent you from downgrading the crutial Umbraco packages used by cloud. +We do this to try to prevent you from downgrading the crucial Umbraco packages used by cloud. We recommend that you align versions of the mentioned package in your csproj-files to the version mentioned in the error or a later version. diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md index eb065f50d89..33f3acfe1fc 100644 --- a/umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md +++ b/umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md @@ -261,7 +261,7 @@ The response from this API call will return the same deployment object in JSON f ### Get Deployments -The endpoint lets you retrieve a list of completed deployments. It can only list deployments that has been run throug the api. +The endpoint lets you retrieve a list of completed deployments. It can only list deployments that has been run through the api. The API allows you to filter and limit the number of returned deployments using query parameters: - _Skip_ : optional, zero or positive integer diff --git a/umbraco-cloud/set-up/project-settings/usage.md b/umbraco-cloud/set-up/project-settings/usage.md index c835da61abe..72cd7c23202 100644 --- a/umbraco-cloud/set-up/project-settings/usage.md +++ b/umbraco-cloud/set-up/project-settings/usage.md @@ -2,7 +2,7 @@ In the Umbraco Cloud Settings menu you can find a page called _Usage_. -On the Usage page, you will find an usage overview that displays your usage and evalues it against the plan limitations of your project. On the page you will also find top 10 for the bandwidth usage of your project that can give you important insight into where you can optimally optimize resource management. +On the Usage page, you will find an usage overview that displays your usage and evaluates it against the plan limitations of your project. On the page you will also find top 10 for the bandwidth usage of your project that can give you important insight into where you can optimally optimize resource management. ## Usage overview @@ -24,9 +24,9 @@ The first is displaying the 10 resources that are contributing the most to the t
-### Top 10 - Bandwidth Usage Referers +### Top 10 - Bandwidth Usage Referrers -The second you will find, is a top 10 of the HTTP referers causing the most bandwidth. A referer is the name of an optional HTTP header field that identifies the address of the web page, from which the resource has been requested. It is the bandwidth generated from these resource requests that counts in the monthly usage limit of the project. +The second you will find, is a top 10 of the HTTP Referrers causing the most bandwidth. A referer is the name of an optional HTTP header field that identifies the address of the web page, from which the resource has been requested. It is the bandwidth generated from these resource requests that counts in the monthly usage limit of the project. ![top 10 bandwidth](../images/Top10BandwidthReferer2.png) diff --git a/umbraco-cloud/troubleshooting/deployments/dependency-exceptions.md b/umbraco-cloud/troubleshooting/deployments/dependency-exceptions.md index 86f540d2eec..92c1ee002ab 100644 --- a/umbraco-cloud/troubleshooting/deployments/dependency-exceptions.md +++ b/umbraco-cloud/troubleshooting/deployments/dependency-exceptions.md @@ -3,7 +3,7 @@ if you delete a content node which might have a reference to another node and you delete the node you are referencing to, you will encounter the following error when trying to transfer the node: -![Dependecy exception](images/dependency-exception-updated.png) +![Dependency exception](images/dependency-exception-updated.png) The error indicates that on the `Home page`, a picker, for example, refers to another content item. This other content item has either been deleted or is in the recycle bin in the environment you're deploying from. From 3691603eb3a6ebf99ac0db6161441c8aab23b0a6 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:35:17 +0000 Subject: [PATCH 04/20] new backoffice typo corrections --- new-backoffice/extending/extension-types/conditions.md | 4 ++-- new-backoffice/extending/extension-types/section-view.md | 2 +- new-backoffice/extending/extension-types/store.md | 6 +++--- new-backoffice/extending/umbraco-element/README.md | 2 +- .../getting-started-with-the-new-backoffice.md | 2 +- .../adding-functionality-to-the-dashboard.md | 2 +- umbraco-cloud/security.md | 2 +- 7 files changed, 10 insertions(+), 10 deletions(-) diff --git a/new-backoffice/extending/extension-types/conditions.md b/new-backoffice/extending/extension-types/conditions.md index c7343c254b1..857f3131074 100644 --- a/new-backoffice/extending/extension-types/conditions.md +++ b/new-backoffice/extending/extension-types/conditions.md @@ -63,9 +63,9 @@ export class MyExtensionCondition extends UmbBaseController implements UmbExtens constructor(args: UmbConditionControllerArguments) { super(args.host); - // This condition aproves after 10 seconds + // This condition approves after 10 seconds setTimeout(() => { - this.permitted = strue; + this.permitted = true; args.onChange(); }, 10000); } diff --git a/new-backoffice/extending/extension-types/section-view.md b/new-backoffice/extending/extension-types/section-view.md index cab85ce7338..78c3a76c884 100644 --- a/new-backoffice/extending/extension-types/section-view.md +++ b/new-backoffice/extending/extension-types/section-view.md @@ -1,6 +1,6 @@ --- description: >- - Append a secondary view for a Section, use it for additonal features or + Append a secondary view for a Section, use it for additional features or information. --- diff --git a/new-backoffice/extending/extension-types/store.md b/new-backoffice/extending/extension-types/store.md index 75ec3c3f919..040a89d4585 100644 --- a/new-backoffice/extending/extension-types/store.md +++ b/new-backoffice/extending/extension-types/store.md @@ -39,7 +39,7 @@ class MyImplementation extends UmbLitElement { constructor() { super(); - // Notice the consume callback is triggered initially and everytime the Context is changed. + // Notice the consume callback is triggered initially and every time the Context is changed. this.consume('MyStoreContextAlias', (context) => { this._myProductStore = context; @@ -69,7 +69,7 @@ class MyProductStore { getByKey(id: string) { - // Request data via a Resource to then take part of this state when recieved. + // Request data via a Resource to then take part of this state when received. tryExecuteAndNotify(this.host, ProductResource.getByKey({id})).then(({ data }) => { if (data) { this.#products.append(data.items); @@ -93,7 +93,7 @@ class MyImplementation extends UmbLitElement { constructor() { super(); - // Notice the consume callback is triggered initially and everytime the Context is changed. + // Notice the consume callback is triggered initially and every time the Context is changed. this.consume('MyStoreContextAlias', (context) => { this._myProductStore = context; diff --git a/new-backoffice/extending/umbraco-element/README.md b/new-backoffice/extending/umbraco-element/README.md index e74919973a8..41f80b005a2 100644 --- a/new-backoffice/extending/umbraco-element/README.md +++ b/new-backoffice/extending/umbraco-element/README.md @@ -10,7 +10,7 @@ This page is a work in progress. This provides a few methods to connect with the Backoffice, giving you the ability to: -* Consume a Contex — [Learn more about Consuming Contexts](../context-api/) +* Consume a Context — [Learn more about Consuming Contexts](../context-api/) * Provide Context — TBD * Observe a State — [Learn more on States](../states.md#observe-a-state-via-umbraco-element-or-umbraco-controller) * Localization — [Learn about Localization](../localization/use-localizations.md#localize-controller) diff --git a/new-backoffice/getting-started/getting-started-with-the-new-backoffice.md b/new-backoffice/getting-started/getting-started-with-the-new-backoffice.md index 47c8f70f71c..ae8d07ab202 100644 --- a/new-backoffice/getting-started/getting-started-with-the-new-backoffice.md +++ b/new-backoffice/getting-started/getting-started-with-the-new-backoffice.md @@ -8,7 +8,7 @@ description: This is how you get started with the new Backoffice and Umbraco 14. The new Backoffice of Umbraco is currently targeting version 14 of Umbraco, which is expected to be released in May 2024. -There are a few ways to check out the new Backoffice, while it is being developed. This may interest you if you are a package or extension developer looking to get an early headstart to upgrade your extensions. +There are a few ways to check out the new Backoffice, while it is being developed. This may interest you if you are a package or extension developer looking to get an early head-start to upgrade your extensions. Read on to get an overview of the different ways in which you can check up on the development of the Backoffice. diff --git a/new-backoffice/tutorials/creating-a-custom-dashboard/adding-functionality-to-the-dashboard.md b/new-backoffice/tutorials/creating-a-custom-dashboard/adding-functionality-to-the-dashboard.md index febbebc41bf..91f1dd6b581 100644 --- a/new-backoffice/tutorials/creating-a-custom-dashboard/adding-functionality-to-the-dashboard.md +++ b/new-backoffice/tutorials/creating-a-custom-dashboard/adding-functionality-to-the-dashboard.md @@ -36,7 +36,7 @@ Now that we have the Auth token, we can consume it in the constructor to obtain {% hint style="info" %} -The entire `welcome-dashbord.element.ts` file is available for reference at the end of the step to confirm your placement for code snippets. +The entire `welcome-dashboard.element.ts` file is available for reference at the end of the step to confirm your placement for code snippets. {% endhint %} diff --git a/umbraco-cloud/security.md b/umbraco-cloud/security.md index 525f209c33f..6090b1f7b4a 100644 --- a/umbraco-cloud/security.md +++ b/umbraco-cloud/security.md @@ -217,7 +217,7 @@ All of the Umbraco APIs use this route as a prefix, including Umbraco Deploy. So You will notice that the regex `^umbraco/backoffice/(.*)|^umbraco` also stops people from going to `yoursite.com/umbraco`, so even the login screen will not show up. Even if you remove the `|^umbraco` part in the end, it should be no problem. You'll get a login screen but any login attempts will be blocked before they reach Umbraco. This is because the login posts to `umbraco/backoffice/UmbracoApi/Authentication/PostLogin`, e.g. it's using the backoffice URL. -The Autoupgrader on Umbraco Cloud needs to have access to the site to succesfully run the upgrade process and apply new patches, by adding these two IP's it ensures that the site is accessible and the autoupgrader can apply the newly released patches. +The Autoupgrader on Umbraco Cloud needs to have access to the site to successfully run the upgrade process and apply new patches, by adding these two IP's it ensures that the site is accessible and the autoupgrader can apply the newly released patches. The last IP address is an example. You can add the addresses that your organization uses as new items to this list. From 7ac4681f8c2b8774fd8b913041cfa7b93bd18994 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:52:07 +0000 Subject: [PATCH 05/20] typo fixes in Generic documentation --- generic/contribute/structure.md | 2 +- generic/getting-started/managing-an-umbraco-project.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/generic/contribute/structure.md b/generic/contribute/structure.md index 286f6a22dc7..f7dddfa4761 100644 --- a/generic/contribute/structure.md +++ b/generic/contribute/structure.md @@ -6,7 +6,7 @@ In this article you will get an overview of the file structure as well as a few ## By product and topic -The overall structure of the Umbraco documenation is divided by product. Each Umbraco product has its own directories with articles and images. +The overall structure of the Umbraco documentation is divided by product. Each Umbraco product has its own directories with articles and images. Diving one step deeper, each individual topic is contained in its own directory. diff --git a/generic/getting-started/managing-an-umbraco-project.md b/generic/getting-started/managing-an-umbraco-project.md index a841c38da93..df0cd04fc60 100644 --- a/generic/getting-started/managing-an-umbraco-project.md +++ b/generic/getting-started/managing-an-umbraco-project.md @@ -14,7 +14,7 @@ In this section you will find information on the key concepts and requirements o [Is Umbraco right for me?](https://umbraco.com/why-choose-umbraco/) -[What commerical options are available from Umbraco?](https://umbraco.com/products/) +[What commercial options are available from Umbraco?](https://umbraco.com/products/) [Information on planning an Umbraco project](http://127.0.0.1:5000/s/OdQETpqkO0Kcv8KMquKL/fundamentals/setup/requirements) From 5bb4952f579d141dddf00e6cd42a2c620492c0fb Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:52:30 +0000 Subject: [PATCH 06/20] typo fixes in `workflow-settings` v10, 12, 13 --- 10/umbraco-workflow/workflow-section/workflow-settings.md | 2 +- 12/umbraco-workflow/workflow-section/workflow-settings.md | 2 +- 13/umbraco-workflow/workflow-section/workflow-settings.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-workflow/workflow-section/workflow-settings.md b/10/umbraco-workflow/workflow-section/workflow-settings.md index da19e101f6b..68a1d1343a1 100644 --- a/10/umbraco-workflow/workflow-section/workflow-settings.md +++ b/10/umbraco-workflow/workflow-section/workflow-settings.md @@ -22,7 +22,7 @@ You can configure the **General** Settings from the **Workflow** section in the * **Implicit** - All steps where the original Change Author is _not_ a member of the group must be completed. Steps where the original Change Author is a member of the approving group will be completed automatically and noted in the workflow history as not required. * **Exclude** - Similar to Explicit. All steps must be completed but the original Change Author is not included in the notifications or shown in the dashboard tasks. * **Approval threshold** - Sets the global approval threshold to One, Most or All: - * **One** - Pending task requires approval from any member of the assigned approval group. This is the default behaviour for all installations (trial and licensed). + * **One** - Pending task requires approval from any member of the assigned approval group. This is the default behavior for all installations (trial and licensed). * **Most** - Pending task requires an absolute majority of group members. For example, a group with three members requires two approvals and a group with four members requires three approvals. * **All** - Pending task requires approval from all group members. * **Rejection resets approvals** - When true, and the approval threshold is Most or All, rejecting a task resets the previous approvals for the workflow stage. diff --git a/12/umbraco-workflow/workflow-section/workflow-settings.md b/12/umbraco-workflow/workflow-section/workflow-settings.md index 86e00f2fab8..866ab31abaf 100644 --- a/12/umbraco-workflow/workflow-section/workflow-settings.md +++ b/12/umbraco-workflow/workflow-section/workflow-settings.md @@ -22,7 +22,7 @@ You can configure the **General** Settings from the **Workflow** section in the * **Implicit** - All steps where the original Change Author is _not_ a member of the group must be completed. Steps where the original Change Author is a member of the approving group will be completed automatically and noted in the workflow history as not required. * **Exclude** - Similar to Explicit. All steps must be completed but the original Change Author is not included in the notifications or shown in the dashboard tasks. * **Approval threshold** - Sets the global approval threshold to One, Most or All: - * **One** - Pending task requires approval from any member of the assigned approval group. This is the default behaviour for all installations (trial and licensed). + * **One** - Pending task requires approval from any member of the assigned approval group. This is the default behavior for all installations (trial and licensed). * **Most** - Pending task requires an absolute majority of group members. For example, a group with three members requires two approvals and a group with four members requires three approvals. * **All** - Pending task requires approval from all group members. * **Rejection resets approvals** - When true, and the approval threshold is Most or All, rejecting a task resets the previous approvals for the workflow stage. diff --git a/13/umbraco-workflow/workflow-section/workflow-settings.md b/13/umbraco-workflow/workflow-section/workflow-settings.md index 86e00f2fab8..866ab31abaf 100644 --- a/13/umbraco-workflow/workflow-section/workflow-settings.md +++ b/13/umbraco-workflow/workflow-section/workflow-settings.md @@ -22,7 +22,7 @@ You can configure the **General** Settings from the **Workflow** section in the * **Implicit** - All steps where the original Change Author is _not_ a member of the group must be completed. Steps where the original Change Author is a member of the approving group will be completed automatically and noted in the workflow history as not required. * **Exclude** - Similar to Explicit. All steps must be completed but the original Change Author is not included in the notifications or shown in the dashboard tasks. * **Approval threshold** - Sets the global approval threshold to One, Most or All: - * **One** - Pending task requires approval from any member of the assigned approval group. This is the default behaviour for all installations (trial and licensed). + * **One** - Pending task requires approval from any member of the assigned approval group. This is the default behavior for all installations (trial and licensed). * **Most** - Pending task requires an absolute majority of group members. For example, a group with three members requires two approvals and a group with four members requires three approvals. * **All** - Pending task requires approval from all group members. * **Rejection resets approvals** - When true, and the approval threshold is Most or All, rejecting a task resets the previous approvals for the workflow stage. From 13321722036cfe20d396bd9c7dc615d6b9f4d332 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:53:31 +0000 Subject: [PATCH 07/20] typo fixes in `umbraco-ui\upgrade` v10, 12, 13 --- 10/umbraco-ui-builder/upgrading/upgrade.md | 2 +- 12/umbraco-ui-builder/upgrading/upgrade.md | 2 +- 13/umbraco-ui-builder/upgrading/upgrade.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-ui-builder/upgrading/upgrade.md b/10/umbraco-ui-builder/upgrading/upgrade.md index 3624a2dbea2..711a4715aed 100644 --- a/10/umbraco-ui-builder/upgrading/upgrade.md +++ b/10/umbraco-ui-builder/upgrading/upgrade.md @@ -41,6 +41,6 @@ If you are using one or more of the below sub-packages, they also need to be upg | Umbraco.UIBuilder.Core | Core UI Builder functionality that doesn't require any infrastructure-specific dependencies | | Umbraco.UIBuilder.Infrastructure | Infrastructure-specific project containing implementations of core UI Builder functionality | | Umbraco.UIBuilder.Web | The core UI Builder logic that requires a web context | -| Umbraco.UIBuilder.Web.StaticAssets | The static asstes for the UI Builder presentation layer | +| Umbraco.UIBuilder.Web.StaticAssets | The static assets for the UI Builder presentation layer | | Umbraco.UIBuilder.Startup | The main logic for registering UI Builder with Umbraco | | Umbraco.UIBuilder | The main UI Builder package | \ No newline at end of file diff --git a/12/umbraco-ui-builder/upgrading/upgrade.md b/12/umbraco-ui-builder/upgrading/upgrade.md index 3624a2dbea2..711a4715aed 100644 --- a/12/umbraco-ui-builder/upgrading/upgrade.md +++ b/12/umbraco-ui-builder/upgrading/upgrade.md @@ -41,6 +41,6 @@ If you are using one or more of the below sub-packages, they also need to be upg | Umbraco.UIBuilder.Core | Core UI Builder functionality that doesn't require any infrastructure-specific dependencies | | Umbraco.UIBuilder.Infrastructure | Infrastructure-specific project containing implementations of core UI Builder functionality | | Umbraco.UIBuilder.Web | The core UI Builder logic that requires a web context | -| Umbraco.UIBuilder.Web.StaticAssets | The static asstes for the UI Builder presentation layer | +| Umbraco.UIBuilder.Web.StaticAssets | The static assets for the UI Builder presentation layer | | Umbraco.UIBuilder.Startup | The main logic for registering UI Builder with Umbraco | | Umbraco.UIBuilder | The main UI Builder package | \ No newline at end of file diff --git a/13/umbraco-ui-builder/upgrading/upgrade.md b/13/umbraco-ui-builder/upgrading/upgrade.md index 3624a2dbea2..711a4715aed 100644 --- a/13/umbraco-ui-builder/upgrading/upgrade.md +++ b/13/umbraco-ui-builder/upgrading/upgrade.md @@ -41,6 +41,6 @@ If you are using one or more of the below sub-packages, they also need to be upg | Umbraco.UIBuilder.Core | Core UI Builder functionality that doesn't require any infrastructure-specific dependencies | | Umbraco.UIBuilder.Infrastructure | Infrastructure-specific project containing implementations of core UI Builder functionality | | Umbraco.UIBuilder.Web | The core UI Builder logic that requires a web context | -| Umbraco.UIBuilder.Web.StaticAssets | The static asstes for the UI Builder presentation layer | +| Umbraco.UIBuilder.Web.StaticAssets | The static assets for the UI Builder presentation layer | | Umbraco.UIBuilder.Startup | The main logic for registering UI Builder with Umbraco | | Umbraco.UIBuilder | The main UI Builder package | \ No newline at end of file From 29349d122d662991d01de9157fb9b622c12833c4 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:53:48 +0000 Subject: [PATCH 08/20] typo fixes in `global-filters` v10, 12, 13 --- 10/umbraco-ui-builder/filtering/global-filters.md | 2 +- 12/umbraco-ui-builder/filtering/global-filters.md | 2 +- 13/umbraco-ui-builder/filtering/global-filters.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-ui-builder/filtering/global-filters.md b/10/umbraco-ui-builder/filtering/global-filters.md index d51e0d075d0..6ead9ff183f 100644 --- a/10/umbraco-ui-builder/filtering/global-filters.md +++ b/10/umbraco-ui-builder/filtering/global-filters.md @@ -10,7 +10,7 @@ If you want to work with a subset of data within a given collection then this is Applying a global filter is controlled via the [collections](../collections/overview.md) configuration. -### **SetFilter(Lambda whereClauseExression) : CollectionConfigBuilder<TEntityType>** +### **SetFilter(Lambda whereClauseExpression) : CollectionConfigBuilder<TEntityType>** Sets the filter **where clause** expression. Expression must be a `boolean` expression. diff --git a/12/umbraco-ui-builder/filtering/global-filters.md b/12/umbraco-ui-builder/filtering/global-filters.md index d51e0d075d0..6ead9ff183f 100644 --- a/12/umbraco-ui-builder/filtering/global-filters.md +++ b/12/umbraco-ui-builder/filtering/global-filters.md @@ -10,7 +10,7 @@ If you want to work with a subset of data within a given collection then this is Applying a global filter is controlled via the [collections](../collections/overview.md) configuration. -### **SetFilter(Lambda whereClauseExression) : CollectionConfigBuilder<TEntityType>** +### **SetFilter(Lambda whereClauseExpression) : CollectionConfigBuilder<TEntityType>** Sets the filter **where clause** expression. Expression must be a `boolean` expression. diff --git a/13/umbraco-ui-builder/filtering/global-filters.md b/13/umbraco-ui-builder/filtering/global-filters.md index d51e0d075d0..6ead9ff183f 100644 --- a/13/umbraco-ui-builder/filtering/global-filters.md +++ b/13/umbraco-ui-builder/filtering/global-filters.md @@ -10,7 +10,7 @@ If you want to work with a subset of data within a given collection then this is Applying a global filter is controlled via the [collections](../collections/overview.md) configuration. -### **SetFilter(Lambda whereClauseExression) : CollectionConfigBuilder<TEntityType>** +### **SetFilter(Lambda whereClauseExpression) : CollectionConfigBuilder<TEntityType>** Sets the filter **where clause** expression. Expression must be a `boolean` expression. From 93e731d7bfd770b62b198abf6db6954531fc16fd Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:54:02 +0000 Subject: [PATCH 09/20] typo fixes in `filterable-properties` v10, 12, 13 --- 10/umbraco-ui-builder/filtering/filterable-properties.md | 2 +- 12/umbraco-ui-builder/filtering/filterable-properties.md | 2 +- 13/umbraco-ui-builder/filtering/filterable-properties.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-ui-builder/filtering/filterable-properties.md b/10/umbraco-ui-builder/filtering/filterable-properties.md index 7e86c1c014c..0c61d0b18e4 100644 --- a/10/umbraco-ui-builder/filtering/filterable-properties.md +++ b/10/umbraco-ui-builder/filtering/filterable-properties.md @@ -55,7 +55,7 @@ filterConfig.SetOptions(new Dictionary { ## Defining options with custom compare clauses for a filterable property -### **AddOption(object key, string label, Lambda compareExpresion) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** +### **AddOption(object key, string label, Lambda compareExpression) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** ````csharp // Example diff --git a/12/umbraco-ui-builder/filtering/filterable-properties.md b/12/umbraco-ui-builder/filtering/filterable-properties.md index 7e86c1c014c..0c61d0b18e4 100644 --- a/12/umbraco-ui-builder/filtering/filterable-properties.md +++ b/12/umbraco-ui-builder/filtering/filterable-properties.md @@ -55,7 +55,7 @@ filterConfig.SetOptions(new Dictionary { ## Defining options with custom compare clauses for a filterable property -### **AddOption(object key, string label, Lambda compareExpresion) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** +### **AddOption(object key, string label, Lambda compareExpression) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** ````csharp // Example diff --git a/13/umbraco-ui-builder/filtering/filterable-properties.md b/13/umbraco-ui-builder/filtering/filterable-properties.md index 7e86c1c014c..0c61d0b18e4 100644 --- a/13/umbraco-ui-builder/filtering/filterable-properties.md +++ b/13/umbraco-ui-builder/filtering/filterable-properties.md @@ -55,7 +55,7 @@ filterConfig.SetOptions(new Dictionary { ## Defining options with custom compare clauses for a filterable property -### **AddOption(object key, string label, Lambda compareExpresion) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** +### **AddOption(object key, string label, Lambda compareExpression) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** ````csharp // Example From 2bf85b31cee118a737af85163d22f4e42e975bce Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:54:17 +0000 Subject: [PATCH 10/20] typo fixes in `collections\the-basics` v10, 12, 13 --- 10/umbraco-ui-builder/collections/the-basics.md | 4 ++-- 12/umbraco-ui-builder/actions/the-basics.md | 6 +++--- 13/umbraco-ui-builder/collections/the-basics.md | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/10/umbraco-ui-builder/collections/the-basics.md b/10/umbraco-ui-builder/collections/the-basics.md index 1cbe103ef89..e512e8e2198 100644 --- a/10/umbraco-ui-builder/collections/the-basics.md +++ b/10/umbraco-ui-builder/collections/the-basics.md @@ -60,7 +60,7 @@ collectionConfig.SetIconColor("blue"); Within Umbraco, it is expected that an entity has a name property. So we need to let Umbraco UI Builder know which property to use for the name. If the entity doesn't have a name property, then it needs to know how to construct a name from an entity's other properties. We do this by using either the `SetNameProperty` or `SetNameFormat` methods on a `Collection` config builder instance. -### **SetNameProperty(Lambda nameProperytyExpression) : CollectionConfigBuilder<TEntityType>** +### **SetNameProperty(Lambda namePropertyExpression) : CollectionConfigBuilder<TEntityType>** Sets which property of your entity to use as the name property. Property must be of type `string`. By defining a property as the name property, its value will be used as the label for the entity in trees and list views. It will also be editable in the header region of the editor interface. The property will also automatically be added to the searchable properties collection and be used for the default sort property. @@ -124,7 +124,7 @@ By default, in Umbraco UI Builder any entity that is deleted via the Umbraco UI ### **SetDeletedProperty(Lambda deletedPropertyExpression) : CollectionConfigBuilder<TEntityType>** -Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actualy deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. +Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actually deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. ````csharp // Example diff --git a/12/umbraco-ui-builder/actions/the-basics.md b/12/umbraco-ui-builder/actions/the-basics.md index 6d9cf13e3ab..430a66c1a40 100644 --- a/12/umbraco-ui-builder/actions/the-basics.md +++ b/12/umbraco-ui-builder/actions/the-basics.md @@ -67,7 +67,7 @@ public class MyAction : Action { settingsConfig.AddFielset("General", fieldsetConfig => fieldsetConfig .AddField(s => s.RecipientName).SetLabel("Recipient Name") - .AddField(s => s.ReceipientEmail).SetLabel("Recipient Email")) + .AddField(s => s.RecipientEmail).SetLabel("Recipient Email")) } public override ActionResult Execute(string collectionAlias, object[] entityIds, MyActionSettings settings) @@ -78,8 +78,8 @@ public class MyAction : Action public class MyActionSettings { - public string ReceipientName { get; set; } - public string ReceipientEmail { get; set; } + public string RecipientName { get; set; } + public string RecipientEmail { get; set; } } ```` diff --git a/13/umbraco-ui-builder/collections/the-basics.md b/13/umbraco-ui-builder/collections/the-basics.md index 1cbe103ef89..e512e8e2198 100644 --- a/13/umbraco-ui-builder/collections/the-basics.md +++ b/13/umbraco-ui-builder/collections/the-basics.md @@ -60,7 +60,7 @@ collectionConfig.SetIconColor("blue"); Within Umbraco, it is expected that an entity has a name property. So we need to let Umbraco UI Builder know which property to use for the name. If the entity doesn't have a name property, then it needs to know how to construct a name from an entity's other properties. We do this by using either the `SetNameProperty` or `SetNameFormat` methods on a `Collection` config builder instance. -### **SetNameProperty(Lambda nameProperytyExpression) : CollectionConfigBuilder<TEntityType>** +### **SetNameProperty(Lambda namePropertyExpression) : CollectionConfigBuilder<TEntityType>** Sets which property of your entity to use as the name property. Property must be of type `string`. By defining a property as the name property, its value will be used as the label for the entity in trees and list views. It will also be editable in the header region of the editor interface. The property will also automatically be added to the searchable properties collection and be used for the default sort property. @@ -124,7 +124,7 @@ By default, in Umbraco UI Builder any entity that is deleted via the Umbraco UI ### **SetDeletedProperty(Lambda deletedPropertyExpression) : CollectionConfigBuilder<TEntityType>** -Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actualy deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. +Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actually deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. ````csharp // Example From 93fd5ad1957ca574b33de9ecf7f24be638a07e3f Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:54:47 +0000 Subject: [PATCH 11/20] typo fixes in `ui-builder\actions\basics` v10, 12, 13 --- 10/umbraco-ui-builder/actions/the-basics.md | 6 +++--- 12/umbraco-ui-builder/collections/the-basics.md | 4 ++-- 13/umbraco-ui-builder/actions/the-basics.md | 6 +++--- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/10/umbraco-ui-builder/actions/the-basics.md b/10/umbraco-ui-builder/actions/the-basics.md index 6d9cf13e3ab..430a66c1a40 100644 --- a/10/umbraco-ui-builder/actions/the-basics.md +++ b/10/umbraco-ui-builder/actions/the-basics.md @@ -67,7 +67,7 @@ public class MyAction : Action { settingsConfig.AddFielset("General", fieldsetConfig => fieldsetConfig .AddField(s => s.RecipientName).SetLabel("Recipient Name") - .AddField(s => s.ReceipientEmail).SetLabel("Recipient Email")) + .AddField(s => s.RecipientEmail).SetLabel("Recipient Email")) } public override ActionResult Execute(string collectionAlias, object[] entityIds, MyActionSettings settings) @@ -78,8 +78,8 @@ public class MyAction : Action public class MyActionSettings { - public string ReceipientName { get; set; } - public string ReceipientEmail { get; set; } + public string RecipientName { get; set; } + public string RecipientEmail { get; set; } } ```` diff --git a/12/umbraco-ui-builder/collections/the-basics.md b/12/umbraco-ui-builder/collections/the-basics.md index 1cbe103ef89..e512e8e2198 100644 --- a/12/umbraco-ui-builder/collections/the-basics.md +++ b/12/umbraco-ui-builder/collections/the-basics.md @@ -60,7 +60,7 @@ collectionConfig.SetIconColor("blue"); Within Umbraco, it is expected that an entity has a name property. So we need to let Umbraco UI Builder know which property to use for the name. If the entity doesn't have a name property, then it needs to know how to construct a name from an entity's other properties. We do this by using either the `SetNameProperty` or `SetNameFormat` methods on a `Collection` config builder instance. -### **SetNameProperty(Lambda nameProperytyExpression) : CollectionConfigBuilder<TEntityType>** +### **SetNameProperty(Lambda namePropertyExpression) : CollectionConfigBuilder<TEntityType>** Sets which property of your entity to use as the name property. Property must be of type `string`. By defining a property as the name property, its value will be used as the label for the entity in trees and list views. It will also be editable in the header region of the editor interface. The property will also automatically be added to the searchable properties collection and be used for the default sort property. @@ -124,7 +124,7 @@ By default, in Umbraco UI Builder any entity that is deleted via the Umbraco UI ### **SetDeletedProperty(Lambda deletedPropertyExpression) : CollectionConfigBuilder<TEntityType>** -Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actualy deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. +Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actually deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. ````csharp // Example diff --git a/13/umbraco-ui-builder/actions/the-basics.md b/13/umbraco-ui-builder/actions/the-basics.md index 6d9cf13e3ab..430a66c1a40 100644 --- a/13/umbraco-ui-builder/actions/the-basics.md +++ b/13/umbraco-ui-builder/actions/the-basics.md @@ -67,7 +67,7 @@ public class MyAction : Action { settingsConfig.AddFielset("General", fieldsetConfig => fieldsetConfig .AddField(s => s.RecipientName).SetLabel("Recipient Name") - .AddField(s => s.ReceipientEmail).SetLabel("Recipient Email")) + .AddField(s => s.RecipientEmail).SetLabel("Recipient Email")) } public override ActionResult Execute(string collectionAlias, object[] entityIds, MyActionSettings settings) @@ -78,8 +78,8 @@ public class MyAction : Action public class MyActionSettings { - public string ReceipientName { get; set; } - public string ReceipientEmail { get; set; } + public string RecipientName { get; set; } + public string RecipientEmail { get; set; } } ```` From 579f969bb6e26ad7ce6597695b74df95f3c44258 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:55:07 +0000 Subject: [PATCH 12/20] typo fixes in `actions\action-visibility` v10, 12, 13 --- 10/umbraco-ui-builder/actions/action-visibility.md | 4 ++-- 12/umbraco-ui-builder/actions/action-visibility.md | 4 ++-- 13/umbraco-ui-builder/actions/action-visibility.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/10/umbraco-ui-builder/actions/action-visibility.md b/10/umbraco-ui-builder/actions/action-visibility.md index 9f7091f4233..99086bb89b4 100644 --- a/10/umbraco-ui-builder/actions/action-visibility.md +++ b/10/umbraco-ui-builder/actions/action-visibility.md @@ -4,11 +4,11 @@ description: Controlling the visibility of actions in Umbraco UI Builder, the ba # Action Visibility -By default actions are not visible in the UI and you must expressly define when and where an action should display. This can be achived in two ways, either on the action definition itself or at the point of registration on the collections config. +By default actions are not visible in the UI and you must expressly define when and where an action should display. This can be achieved in two ways, either on the action definition itself or at the point of registration on the collections config. ## Controlling the default action visibility -To define the default visbility of an action at the action level you can do this by overriding the `IsVisible` method of the `Action<>` base class. +To define the default visibility of an action at the action level you can do this by overriding the `IsVisible` method of the `Action<>` base class. ````csharp // Example diff --git a/12/umbraco-ui-builder/actions/action-visibility.md b/12/umbraco-ui-builder/actions/action-visibility.md index 9f7091f4233..99086bb89b4 100644 --- a/12/umbraco-ui-builder/actions/action-visibility.md +++ b/12/umbraco-ui-builder/actions/action-visibility.md @@ -4,11 +4,11 @@ description: Controlling the visibility of actions in Umbraco UI Builder, the ba # Action Visibility -By default actions are not visible in the UI and you must expressly define when and where an action should display. This can be achived in two ways, either on the action definition itself or at the point of registration on the collections config. +By default actions are not visible in the UI and you must expressly define when and where an action should display. This can be achieved in two ways, either on the action definition itself or at the point of registration on the collections config. ## Controlling the default action visibility -To define the default visbility of an action at the action level you can do this by overriding the `IsVisible` method of the `Action<>` base class. +To define the default visibility of an action at the action level you can do this by overriding the `IsVisible` method of the `Action<>` base class. ````csharp // Example diff --git a/13/umbraco-ui-builder/actions/action-visibility.md b/13/umbraco-ui-builder/actions/action-visibility.md index 9f7091f4233..99086bb89b4 100644 --- a/13/umbraco-ui-builder/actions/action-visibility.md +++ b/13/umbraco-ui-builder/actions/action-visibility.md @@ -4,11 +4,11 @@ description: Controlling the visibility of actions in Umbraco UI Builder, the ba # Action Visibility -By default actions are not visible in the UI and you must expressly define when and where an action should display. This can be achived in two ways, either on the action definition itself or at the point of registration on the collections config. +By default actions are not visible in the UI and you must expressly define when and where an action should display. This can be achieved in two ways, either on the action definition itself or at the point of registration on the collections config. ## Controlling the default action visibility -To define the default visbility of an action at the action level you can do this by overriding the `IsVisible` method of the `Action<>` base class. +To define the default visibility of an action at the action level you can do this by overriding the `IsVisible` method of the `Action<>` base class. ````csharp // Example From 645dae250812f2587e27043dd707bd9ffd8529e8 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:56:09 +0000 Subject: [PATCH 13/20] typo fixes in `magic-strings` v10, 12, 13 --- 10/umbraco-forms/developer/magic-strings.md | 2 +- 12/umbraco-forms/developer/magic-strings.md | 2 +- 13/umbraco-forms/developer/magic-strings.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-forms/developer/magic-strings.md b/10/umbraco-forms/developer/magic-strings.md index 2fbdae9849f..6acfb3ca4cb 100644 --- a/10/umbraco-forms/developer/magic-strings.md +++ b/10/umbraco-forms/developer/magic-strings.md @@ -93,7 +93,7 @@ Umbraco Forms ships with the following filters: | Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | | HTML encode a string | `html` | | `[#field \| html]` | -The format strings used for fomrmatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. +The format strings used for formatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. Further magic string format functions can be [created in code](extending/adding-a-magic-string-format-function.md) for use in forms. diff --git a/12/umbraco-forms/developer/magic-strings.md b/12/umbraco-forms/developer/magic-strings.md index 739092cb2a4..4ab8372d881 100644 --- a/12/umbraco-forms/developer/magic-strings.md +++ b/12/umbraco-forms/developer/magic-strings.md @@ -93,7 +93,7 @@ Umbraco Forms ships with the following filters: | Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | | HTML encode a string | `html` | | `[#field \| html]` | -The format strings used for fomrmatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. +The format strings used for formatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. Further magic string format functions can be [created in code](extending/adding-a-magic-string-format-function.md) for use in forms. diff --git a/13/umbraco-forms/developer/magic-strings.md b/13/umbraco-forms/developer/magic-strings.md index 739092cb2a4..4ab8372d881 100644 --- a/13/umbraco-forms/developer/magic-strings.md +++ b/13/umbraco-forms/developer/magic-strings.md @@ -93,7 +93,7 @@ Umbraco Forms ships with the following filters: | Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | | HTML encode a string | `html` | | `[#field \| html]` | -The format strings used for fomrmatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. +The format strings used for formatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. Further magic string format functions can be [created in code](extending/adding-a-magic-string-format-function.md) for use in forms. From 14733554313ab55aa0ed044450dd11b6dffb653d Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 10:57:11 +0000 Subject: [PATCH 14/20] typo fixes in `changelog-archive` v10, 12, 13 --- 10/umbraco-ui-builder/changelog-archive/changelog.md | 2 +- 12/umbraco-ui-builder/changelog-archive/changelog.md | 2 +- 13/umbraco-ui-builder/changelog-archive/changelog.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-ui-builder/changelog-archive/changelog.md b/10/umbraco-ui-builder/changelog-archive/changelog.md index ca626c1c287..82b8c320984 100644 --- a/10/umbraco-ui-builder/changelog-archive/changelog.md +++ b/10/umbraco-ui-builder/changelog-archive/changelog.md @@ -29,7 +29,7 @@ description: Changelog for Konstrukt, the backoffice UI builder for Umbraco. - Added marketplace updates. - Update the Konstrukt type finder to use a non-obsolete constructor. -- Updated to use `IComposer` instead of `IUserCompser` as the latter has been removed in v11. +- Updated to use `IComposer` instead of `IUserComposer` as the latter has been removed in v11. - Fixed parent ID not being passed to create dialog for associated entities. - Removed settings section restriction on the licensing info endpoint as it would cause errors when the licensing banner is shown in other sections. diff --git a/12/umbraco-ui-builder/changelog-archive/changelog.md b/12/umbraco-ui-builder/changelog-archive/changelog.md index ca626c1c287..82b8c320984 100644 --- a/12/umbraco-ui-builder/changelog-archive/changelog.md +++ b/12/umbraco-ui-builder/changelog-archive/changelog.md @@ -29,7 +29,7 @@ description: Changelog for Konstrukt, the backoffice UI builder for Umbraco. - Added marketplace updates. - Update the Konstrukt type finder to use a non-obsolete constructor. -- Updated to use `IComposer` instead of `IUserCompser` as the latter has been removed in v11. +- Updated to use `IComposer` instead of `IUserComposer` as the latter has been removed in v11. - Fixed parent ID not being passed to create dialog for associated entities. - Removed settings section restriction on the licensing info endpoint as it would cause errors when the licensing banner is shown in other sections. diff --git a/13/umbraco-ui-builder/changelog-archive/changelog.md b/13/umbraco-ui-builder/changelog-archive/changelog.md index ca626c1c287..82b8c320984 100644 --- a/13/umbraco-ui-builder/changelog-archive/changelog.md +++ b/13/umbraco-ui-builder/changelog-archive/changelog.md @@ -29,7 +29,7 @@ description: Changelog for Konstrukt, the backoffice UI builder for Umbraco. - Added marketplace updates. - Update the Konstrukt type finder to use a non-obsolete constructor. -- Updated to use `IComposer` instead of `IUserCompser` as the latter has been removed in v11. +- Updated to use `IComposer` instead of `IUserComposer` as the latter has been removed in v11. - Fixed parent ID not being passed to create dialog for associated entities. - Removed settings section restriction on the licensing info endpoint as it would cause errors when the licensing banner is shown in other sections. From 61dd00bfd745ead2b6646ecb6432fe5a33b91d20 Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 11:07:39 +0000 Subject: [PATCH 15/20] removes spurious 'actually' to pass Vale --- 10/umbraco-ui-builder/collections/the-basics.md | 2 +- 12/umbraco-ui-builder/collections/the-basics.md | 2 +- 13/umbraco-ui-builder/collections/the-basics.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/10/umbraco-ui-builder/collections/the-basics.md b/10/umbraco-ui-builder/collections/the-basics.md index e512e8e2198..eb7a1ba61a3 100644 --- a/10/umbraco-ui-builder/collections/the-basics.md +++ b/10/umbraco-ui-builder/collections/the-basics.md @@ -124,7 +124,7 @@ By default, in Umbraco UI Builder any entity that is deleted via the Umbraco UI ### **SetDeletedProperty(Lambda deletedPropertyExpression) : CollectionConfigBuilder<TEntityType>** -Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actually deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. +Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. ````csharp // Example diff --git a/12/umbraco-ui-builder/collections/the-basics.md b/12/umbraco-ui-builder/collections/the-basics.md index e512e8e2198..eb7a1ba61a3 100644 --- a/12/umbraco-ui-builder/collections/the-basics.md +++ b/12/umbraco-ui-builder/collections/the-basics.md @@ -124,7 +124,7 @@ By default, in Umbraco UI Builder any entity that is deleted via the Umbraco UI ### **SetDeletedProperty(Lambda deletedPropertyExpression) : CollectionConfigBuilder<TEntityType>** -Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actually deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. +Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. ````csharp // Example diff --git a/13/umbraco-ui-builder/collections/the-basics.md b/13/umbraco-ui-builder/collections/the-basics.md index e512e8e2198..eb7a1ba61a3 100644 --- a/13/umbraco-ui-builder/collections/the-basics.md +++ b/13/umbraco-ui-builder/collections/the-basics.md @@ -124,7 +124,7 @@ By default, in Umbraco UI Builder any entity that is deleted via the Umbraco UI ### **SetDeletedProperty(Lambda deletedPropertyExpression) : CollectionConfigBuilder<TEntityType>** -Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of actually deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. +Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. ````csharp // Example From f7b83f5040379f5895014762aeec85a60c81864b Mon Sep 17 00:00:00 2001 From: LFLaverty Date: Wed, 17 Jan 2024 11:19:15 +0000 Subject: [PATCH 16/20] rewrites some sections to bring word count below 25 words --- .../getting-started/the-umbraco-cloud-portal/README.md | 2 +- umbraco-cloud/security.md | 2 +- umbraco-cloud/set-up/project-settings/usage.md | 4 ++-- .../getting-started/deployment-workflow/content-transfer.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md index 20dde72eadd..75d28535098 100644 --- a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md +++ b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md @@ -79,7 +79,7 @@ In the [Settings](../../set-up/project-settings/) section, you will find a lot m ### Manage Subscriptions -For customers who have joined Umbraco Cloud before the 5th of May, 2021, can manage their subscriptions from Umbraco Shop. Umbraco Shop can be accessed through [Umbraco.com](https://umbraco.com). You can also click on the **Manage Subscriptions** link from the **Profile** dropdown on the Umbraco Cloud Portal. Find out more in the [Manage Subscriptions](../../set-up/manage-subscriptions/) article. +For customers who joined Umbraco Cloud before 5th of May, 2021, subscriptions can be managed from Umbraco Shop. Umbraco Shop can be accessed through [shop.umbraco.com](https://shop.umbraco.com). You can also click on the **Manage Subscriptions** link from the **Profile** dropdown on the Umbraco Cloud Portal. Find out more in the [Manage Subscriptions](../../set-up/manage-subscriptions/) article. Customers who have joined Umbraco Cloud after the 5th of May, 2021, can manage their subscriptions directly through Umbraco Cloud. Find out more in the [Payments on Umbraco Cloud](../../set-up/manage-subscriptions/new-shop/) article. diff --git a/umbraco-cloud/security.md b/umbraco-cloud/security.md index 6090b1f7b4a..8637e8fccdb 100644 --- a/umbraco-cloud/security.md +++ b/umbraco-cloud/security.md @@ -217,7 +217,7 @@ All of the Umbraco APIs use this route as a prefix, including Umbraco Deploy. So You will notice that the regex `^umbraco/backoffice/(.*)|^umbraco` also stops people from going to `yoursite.com/umbraco`, so even the login screen will not show up. Even if you remove the `|^umbraco` part in the end, it should be no problem. You'll get a login screen but any login attempts will be blocked before they reach Umbraco. This is because the login posts to `umbraco/backoffice/UmbracoApi/Authentication/PostLogin`, e.g. it's using the backoffice URL. -The Autoupgrader on Umbraco Cloud needs to have access to the site to successfully run the upgrade process and apply new patches, by adding these two IP's it ensures that the site is accessible and the autoupgrader can apply the newly released patches. +The Autoupgrader on Umbraco Cloud needs to have access to the site to successfully run the upgrade process and apply new patches. By adding these two IP's it ensures that the site is accessible and the autoupgrader can apply the newly released patches. The last IP address is an example. You can add the addresses that your organization uses as new items to this list. diff --git a/umbraco-cloud/set-up/project-settings/usage.md b/umbraco-cloud/set-up/project-settings/usage.md index 72cd7c23202..190517fbc33 100644 --- a/umbraco-cloud/set-up/project-settings/usage.md +++ b/umbraco-cloud/set-up/project-settings/usage.md @@ -2,7 +2,7 @@ In the Umbraco Cloud Settings menu you can find a page called _Usage_. -On the Usage page, you will find an usage overview that displays your usage and evaluates it against the plan limitations of your project. On the page you will also find top 10 for the bandwidth usage of your project that can give you important insight into where you can optimally optimize resource management. +On the Usage page, you will find an overview that displays your usage and evaluates it against the plan limitations of your project. On the page you will also find top 10 for the bandwidth usage of your project. This can give you important insight into where you can optimize resource management. ## Usage overview @@ -26,7 +26,7 @@ The first is displaying the 10 resources that are contributing the most to the t ### Top 10 - Bandwidth Usage Referrers -The second you will find, is a top 10 of the HTTP Referrers causing the most bandwidth. A referer is the name of an optional HTTP header field that identifies the address of the web page, from which the resource has been requested. It is the bandwidth generated from these resource requests that counts in the monthly usage limit of the project. +The second displays the top 10 HTTP Referrers causing the most bandwidth. A referer is an optional HTTP header field identifying the address of the web page from which the resource was requested. It is the bandwidth generated from these resource requests that counts in the monthly usage limit of the project. ![top 10 bandwidth](../images/Top10BandwidthReferer2.png) diff --git a/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md b/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md index 929b4a9e725..0860ba0fc58 100644 --- a/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md +++ b/umbraco-heartcore/getting-started/deployment-workflow/content-transfer.md @@ -16,4 +16,4 @@ The screenshot above is from the Content section on a Development environment. R **Queue for transfer** gives you the option to queue all content in the Content tree for transfer to the next environment (Staging or Live). It is also possible to right-click single nodes in the content structure in order to only queue some of it for transfer. -**Restore** gives you the option to restore all content from environments right of the current environment. In some cases you might not want to restore all content as once, in which case you should use the _Partial restore_ option instead, which you can find by right-clicking a node in the content tree. +**Restore** gives you the option to restore all content from environments right of the current environment. In some cases you might not want to restore all content as once, in which case you should use the _Partial restore_ option instead. _Partial restore_ can be found by right-clicking a node in the content tree. From 9e5e1811c5129c66f5c744284f336d93b2548b78 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Mon, 29 Jan 2024 14:31:23 +0100 Subject: [PATCH 17/20] Update umbraco-cloud/getting-started/migrate-existing-site/README.md --- umbraco-cloud/getting-started/migrate-existing-site/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/getting-started/migrate-existing-site/README.md b/umbraco-cloud/getting-started/migrate-existing-site/README.md index 95c9cdcd89e..adb455e9624 100644 --- a/umbraco-cloud/getting-started/migrate-existing-site/README.md +++ b/umbraco-cloud/getting-started/migrate-existing-site/README.md @@ -135,7 +135,7 @@ Merging your existing site into the Umbraco Cloud project is a matter of moving * If your existing site uses Umbraco Forms, make sure you **do not overwrite** the `\umbraco\Licenses\umbracoForms.lic` file * When copying your `\umbraco\` folder, make sure you **do not delete** the `\umbraco\Licenses\umbracoDeploy.lic` file * If you have any custom code in your project, you should copy that code over too. -2. Merge Appsettings.JSON files from your existing site with the cloud site. +2. Merge `appsettings.json` files from your existing site with the cloud site. * Make sure that you merge your `appsettings.json` files with the ones from your existing site so that the settings you used are moved over to your Cloud project 3. Merge your Program.cs and Startup.cs with the one from your existing site 4. Merge your `ProjectName.csproj` with the `UmbracoProject.csproj` - especially if you have any packages installed on your project. From ffde63efbcb6d9a8e2c0a22b98cc32143a088399 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Mon, 29 Jan 2024 14:31:32 +0100 Subject: [PATCH 18/20] Update umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md --- .../getting-started/the-umbraco-cloud-portal/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md index 75d28535098..6881e11a16d 100644 --- a/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md +++ b/umbraco-cloud/getting-started/the-umbraco-cloud-portal/README.md @@ -79,7 +79,7 @@ In the [Settings](../../set-up/project-settings/) section, you will find a lot m ### Manage Subscriptions -For customers who joined Umbraco Cloud before 5th of May, 2021, subscriptions can be managed from Umbraco Shop. Umbraco Shop can be accessed through [shop.umbraco.com](https://shop.umbraco.com). You can also click on the **Manage Subscriptions** link from the **Profile** dropdown on the Umbraco Cloud Portal. Find out more in the [Manage Subscriptions](../../set-up/manage-subscriptions/) article. +For customers who joined Umbraco Cloud before 5th of May 2021, subscriptions can be managed from Umbraco Shop. Umbraco Shop can be accessed through [shop.umbraco.com](https://shop.umbraco.com). You can also click on the **Manage Subscriptions** link from the **Profile** dropdown on the Umbraco Cloud Portal. Find out more in the [Manage Subscriptions](../../set-up/manage-subscriptions/) article. Customers who have joined Umbraco Cloud after the 5th of May, 2021, can manage their subscriptions directly through Umbraco Cloud. Find out more in the [Payments on Umbraco Cloud](../../set-up/manage-subscriptions/new-shop/) article. From 41e544d6d44055b055bf7b4e52cea69191749440 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Mon, 29 Jan 2024 14:31:39 +0100 Subject: [PATCH 19/20] Update umbraco-cloud/security.md --- umbraco-cloud/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/security.md b/umbraco-cloud/security.md index 8637e8fccdb..f8e3412ced0 100644 --- a/umbraco-cloud/security.md +++ b/umbraco-cloud/security.md @@ -80,7 +80,7 @@ In order to integrate older external applications to access Umbraco Cloud Websit For ASP.NET applications, inspect the `` element of web.config to find the version of the .NET Framework your application is using. .NET applications on .NET 4.7+ are using the OS specified TLS protocols. In Windows 8 & 10, Windows Server 2012 & 2016 TLS 1.2+ is used by default, therefore no actions necessary. .NET applications lower then 4.7 require updates to ensure they can communicate using TLS 1.2 by default. -More information specifically from Microsoft about .Net applications and TLS support can be found [in Microsoft's official docs](https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#audit-your-code-and-make-code-changes). For other application frameworks/languages we encourage to lookup their respective documentations. +More information specifically from Microsoft about .Net applications and Transport Layer Security (TLS) support can be found [in Microsoft's official docs](https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#audit-your-code-and-make-code-changes). For other application frameworks/languages we encourage to lookup their respective documentations. ### HTTP From be0bf2172dd9a0964e03a24679a40909521e49c8 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Mon, 29 Jan 2024 14:31:45 +0100 Subject: [PATCH 20/20] Update umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md --- .../getting-started/backoffice-users-and-api-keys.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md b/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md index d2fe35fd393..e76c639c938 100644 --- a/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md +++ b/umbraco-heartcore/getting-started/backoffice-users-and-api-keys.md @@ -38,4 +38,6 @@ You are able to see a list of all your created API Keys and all relevant informa ![List of all APIs](images/listOfAPIs.png) - +{% embed url="https://www.youtube.com/embed/QHrFcEibYrE?rel=0" %} +Umbraco Heartcore: API keys +{% endembed %}