diff --git a/guides/plugins/apps/administration/add-custom-action-button.md b/guides/plugins/apps/administration/add-custom-action-button.md index b0d63683a..c6d905e69 100644 --- a/guides/plugins/apps/administration/add-custom-action-button.md +++ b/guides/plugins/apps/administration/add-custom-action-button.md @@ -10,7 +10,7 @@ To get those buttons, you start in the `admin` section of your manifest file. Th ```xml - + ... @@ -175,7 +175,7 @@ To use custom endpoints as the target url for action buttons you can define the ```xml - + ... diff --git a/guides/plugins/apps/administration/add-custom-modules.md b/guides/plugins/apps/administration/add-custom-modules.md index 7d2e52488..bd0518766 100644 --- a/guides/plugins/apps/administration/add-custom-modules.md +++ b/guides/plugins/apps/administration/add-custom-modules.md @@ -9,17 +9,17 @@ Creating custom modules takes place at the `` section of your `manifest.x To configure your module you can set it up with with some additional attributes. * `name` \(required\): The technical name of the module. This is the name your module is referenced with. +* `parent` \(required\): The Administration navigation id of the menu item that serves as the parent menu item. * `source` \(optional\): The URL to your app servers endpoint from which the module is served from. This can be omitted if you want to define a menu item that should serve as a parent menu item for other app modules. -* `parent` \(optional\): The administration navigation id from the menu item that serves as the parrent menu item. If omitted your module will be listed under the "My apps" menu entry. **This field will be required in future versions as we are going to remove the "My Apps" menu item** * `position` \(optional\): A numeric index that sets the position of your menu entry regarding to it's siblings. Additionally you can define `label` elements inside of your `module` element, to set up how your module will be displayed in the admin menu. {% code title="manifest.xml" %} -```markup +```xml - + ... @@ -73,13 +73,13 @@ With Shopware 6.4.0.0 we added a third level in the admin menu structure. This c When you define a module, it gets automatically loaded by the administration. Additionally the administration creates a menu entry for your module. You can reference this menu entry and set it as the parent menu entry for your other modules. -The navigation id of your modules uses always pattern `app--`. So, within your manifest you can add a reference to modules that you just created: +The navigation id of your modules always uses the pattern `app--`. So, within your manifest you can add a reference to modules that you just created: {% code title="manifest.xml" %} -```markup +```xml - + myApp ... @@ -120,9 +120,9 @@ To avoid mixing other modules with your main module, we decided to separate the {% code title="manifest.xml" %} -```markup +```xml - + myApp ... diff --git a/guides/plugins/apps/app-base-guide.md b/guides/plugins/apps/app-base-guide.md index 7c2a3b303..4094b5daf 100644 --- a/guides/plugins/apps/app-base-guide.md +++ b/guides/plugins/apps/app-base-guide.md @@ -28,7 +28,7 @@ The manifest file is the central point of your app. It defines the interface bet ```xml - + MyExampleApp @@ -87,7 +87,7 @@ The registration request is made as a `GET` request against a URL you provide in ```xml - + ... @@ -267,7 +267,7 @@ Sample permissions to read, create and update products, delete orders, as well a ```xml - + ... @@ -302,7 +302,7 @@ To use webhooks in your app, you need to implement a `` element in you ```xml - + ... diff --git a/guides/plugins/apps/custom-data/custom-entities.md b/guides/plugins/apps/custom-data/custom-entities.md index 668d38da7..89550b84d 100644 --- a/guides/plugins/apps/custom-data/custom-entities.md +++ b/guides/plugins/apps/custom-data/custom-entities.md @@ -48,7 +48,7 @@ you need the appropriate [permissions](../../../../resources/references/app-refe ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware/platform/trunk/src/Core/Framework/App/Manifest/Schema/manifest-2.0.xsd"> diff --git a/guides/plugins/apps/custom-data/custom-fields.md b/guides/plugins/apps/custom-data/custom-fields.md index cd68b8ba4..f3be55a04 100644 --- a/guides/plugins/apps/custom-data/custom-fields.md +++ b/guides/plugins/apps/custom-data/custom-fields.md @@ -7,7 +7,7 @@ To make use of the custom fields register your custom field sets in your manifes ```markup - + ... diff --git a/guides/plugins/apps/flow-builder/add-custom-flow-actions-from-app-system.md b/guides/plugins/apps/flow-builder/add-custom-flow-actions-from-app-system.md index 5bdf7dd70..025e91330 100644 --- a/guides/plugins/apps/flow-builder/add-custom-flow-actions-from-app-system.md +++ b/guides/plugins/apps/flow-builder/add-custom-flow-actions-from-app-system.md @@ -52,7 +52,7 @@ The manifest file is the central point of your app. It defines the interface bet ```xml - + FlowBuilderActionApp diff --git a/guides/plugins/apps/payment.md b/guides/plugins/apps/payment.md index 407246ecc..8aa17270f 100644 --- a/guides/plugins/apps/payment.md +++ b/guides/plugins/apps/payment.md @@ -22,9 +22,9 @@ Below you can see three different definitions of payment methods. {% code title="manifest.xml" %} -```markup +```xml - + PaymentApp diff --git a/guides/plugins/apps/rule-builder/add-custom-rule-conditions.md b/guides/plugins/apps/rule-builder/add-custom-rule-conditions.md index 00a52cb39..aa12a5538 100644 --- a/guides/plugins/apps/rule-builder/add-custom-rule-conditions.md +++ b/guides/plugins/apps/rule-builder/add-custom-rule-conditions.md @@ -30,7 +30,7 @@ App Rule Conditions are defined in the `manifest.xml` file of your app: ```markup - + ... diff --git a/guides/plugins/apps/starter/add-api-endpoint.md b/guides/plugins/apps/starter/add-api-endpoint.md index c7129f775..57da951c2 100644 --- a/guides/plugins/apps/starter/add-api-endpoint.md +++ b/guides/plugins/apps/starter/add-api-endpoint.md @@ -40,7 +40,7 @@ Next, we will put our basic configuration into the file we just created. ```xml - + MyApiExtension diff --git a/guides/plugins/apps/starter/product-translator.md b/guides/plugins/apps/starter/product-translator.md index 48ff1195d..f9ab15dc1 100644 --- a/guides/plugins/apps/starter/product-translator.md +++ b/guides/plugins/apps/starter/product-translator.md @@ -78,7 +78,7 @@ Let's start by filling in all the meta information: ```xml - + product-translator @@ -105,7 +105,7 @@ Next, we will define the `` part of the manifest. This part describes how ```xml - + @@ -129,7 +129,7 @@ Permissions are needed as this app will need to read product descriptions and tr ```xml - + @@ -158,7 +158,7 @@ in its shops: ```xml - + diff --git a/guides/plugins/apps/starter/starter-admin-extension.md b/guides/plugins/apps/starter/starter-admin-extension.md index d88ffbad8..5d3856b3d 100644 --- a/guides/plugins/apps/starter/starter-admin-extension.md +++ b/guides/plugins/apps/starter/starter-admin-extension.md @@ -41,7 +41,7 @@ Next, we will put our basic configuration into the file we just created. ```xml - + SimpleNotification @@ -122,7 +122,7 @@ In order to do that, we have to add an `admin` section to our `manifest.xml` fil ```xml - + diff --git a/guides/plugins/apps/storefront/cookies-with-apps.md b/guides/plugins/apps/storefront/cookies-with-apps.md index e93f2929c..1bb2226dc 100644 --- a/guides/plugins/apps/storefront/cookies-with-apps.md +++ b/guides/plugins/apps/storefront/cookies-with-apps.md @@ -14,7 +14,7 @@ To add new cookies to the cookie consent manager, you can add a `cookies` sectio ```xml - + ExampleAppWithCookies 1.0.0 @@ -54,7 +54,7 @@ To add a cookie group, you can add a `groups` section within your `cookies` sect ```xml - + ExampleAppWithCookies 1.0.0 diff --git a/resources/references/app-reference/manifest-reference.md b/resources/references/app-reference/manifest-reference.md index 2a95fdc04..60ff92fb0 100644 --- a/resources/references/app-reference/manifest-reference.md +++ b/resources/references/app-reference/manifest-reference.md @@ -3,7 +3,7 @@ {% code title="manifest.xml" %} ```xml - + MyExampleApp