You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
- description: Added a new overview page for [Klarna's payment method](https://devdocs.magento.com/guides/v2.4/graphql/payment-methods/klarna.html)
26
+
and a new reference page for Klarna's [`createKlarnaPaymentsSession`](https://devdocs.magento.com/guides/v2.4/graphql/mutations/create-klarna-payments-session.html)
to add a review and the [productReviewRatingsMetadata query](https://devdocs.magento.com/guides/v2.4/graphql/queries/product-review-ratings-metadata.html)
79
+
to retrieve information about the reviews infrastructure.
- description: Added GraphQL support for rewards points. Use the [`applyRewardPointsToCart`](https://devdocs.magento.com/guides/v2.4/graphql/mutations/apply-reward-points.html)
120
+
and [`removeRewardPointsFromCart`](https://devdocs.magento.com/guides/v2.4/graphql/mutations/remove-reward-points.html)
121
+
mutation to manage reward points within a cart. The [cart](https://devdocs.magento.com/guides/v2.4/graphql/queries/cart.html),
- description: Added GraphQL Vault support with the [Payflow Pro Vault](https://devdocs.magento.com/guides/v2.4/graphql/payment-methods/payflow-pro-vault.html)
Copy file name to clipboardExpand all lines: src/cloud/project/project-routes-more-redir.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,9 @@ The following demonstrates how to manage redirection rules on your {{site.data.v
12
12
13
13
{% include cloud/note-route-all-placeholder.md %}
14
14
15
+
{:.bs-callout-warning}
16
+
For {{ site.data.var.ece }} projects, configuring large numbers of non-regex redirects and rewrites in the `routes.yaml` file can cause performance issues. If your `routes.yaml` file is 32KB or larger, offload your non-regex redirects and rewrites to Fastly. See [Offload non-regex redirects to Fastly instead of Nginx (routes)](https://support.magento.com/hc/en-us/articles/360035192891-Offload-non-regex-redirects-to-Fastly-instead-of-Nginx-routes-) in the _Magento Help Center_.
17
+
15
18
## Whole-route redirects {#cloud-route-whole}
16
19
17
20
Using whole-route redirects, you can define simple routes using the `routes.yaml` file. For example, you can redirect from an apex domain to a `www` subdomain as follows:
|[`{{site.data.var.ct}}` release notes]| {{site.data.var.ct-release}}<br/>2002.0.23| A set of scripts and tools designed to manage and deploy Cloud projects |[{{site.data.var.ct}}][ece package]|
17
-
|[`{{site.data.var.mcp-prod}}` release notes]| {{site.data.var.mcp-release}} | A set of patches which improve the integration of all Magento versions with Cloud environments. This package includes Magento patches and available hotfixes that are applied when you use `{{site.data.var.ct}}` to deploy |[{{site.data.var.mcp}}][Patches package]|
18
-
|[`{{site.data.var.mcd-prod}}` release notes]| {{site.data.var.mcd-release}} | Functionality and configuration files for Docker images to deploy Magento Commerce to a local Cloud environment |[{{site.data.var.mcd}}][Docker package]|
19
-
|[`{{site.data.var.mcc-prod}}` release notes]| {{site.data.var.mcc-release}} | Extended Magento Commerce core functionality for sites deployed on the Cloud platform |[{{site.data.var.mcc}}][Components package]|
17
+
|[`{{site.data.var.mcp-prod}}` release notes]| {{site.data.var.mcp-release}} | A set of patches which improve the integration of all Magento versions with Cloud environments. This package includes Magento patches and available hotfixes that are applied when you use `{{site.data.var.ct}}` to deploy |[{{site.data.var.mcp-package}}][Patches package]|
18
+
|[`{{site.data.var.mcd-prod}}` release notes]| {{site.data.var.mcd-release}} | Functionality and configuration files for Docker images to deploy Magento Commerce to a local Cloud environment |[{{site.data.var.mcd-package}}][Docker package]|
19
+
|[`{{site.data.var.mcc-prod}}` release notes]| {{site.data.var.mcc-release}} | Extended Magento Commerce core functionality for sites deployed on the Cloud platform |[{{site.data.var.mcc-package}}][Components package]|
20
20
21
21
When you update to `{{site.data.var.ct}}` 2002.1.0 or later, you automatically update to the latest versions of the other packages, which are dependencies for `{{site.data.var.ct}}`.
Copy file name to clipboardExpand all lines: src/cloud/release-notes/mcp-release-notes.md
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,17 @@ To ensure that your project has all required patches, update to the [latest vers
19
19
{:.bs-callout-info}
20
20
See [Apply patches]({{site.baseurl}}/cloud/project/project-patch.html) for instructions on applying patches to your Magento projects.
21
21
22
+
<!--Add release notes below-->
23
+
24
+
## v1.0.7
25
+
*Release date: October 14, 2020*<br/>
26
+
27
+
-**Redis patches for Magento 2.3.0 to 2.3.5, 2.4.0**–Updated the Redis patches to support adding products to a category when implementing a Level 2 cache. <!--MCLOUD-6659-->
28
+
29
+
-**Braintree VBE patch**–Fixes an issue that generated an error when an Administrator tried to view a Braintree Settlement Report. <!--MCLOUD-6684-->
30
+
31
+
- Now, the `ece-patches apply` command uses the Unix `patch` command to apply patches if Git is not available on the host system. <!--MCLOUD-7069-->
Copy file name to clipboardExpand all lines: src/contributor-guide/contributing.md
+83-1Lines changed: 83 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -206,7 +206,11 @@ When you want to verify an issue or pull request, use the `instance` command to
206
206
@magento give me {$version} instance
207
207
```
208
208
209
-
For `version`, the currently supported values are latest [version tags](https://github.com/magento/magento2/tags) and the 2.4-develop branch.
209
+
Replace `{$version}` with the version tag for the version required. The currently supported values are the latest [version tags](https://github.com/magento/magento2/tags) and the 2.4-develop branch. For example:
210
+
211
+
```text
212
+
@magento give me 2.4.0 instance
213
+
```
210
214
211
215
**Actions:** The following actions complete the command:
212
216
@@ -248,6 +252,84 @@ Admins access will be shared via comment on GitHub.
In some cases a custom environment is required to test an issue or a pull request. You can create a custom environment by appending custom configuration settings to the PR comment to [Deploy a vanilla Magento instance](#vanilla-pr) or [Deploy an instance based on PR changes](#deploy-pr).
258
+
259
+
#### Magento edition
260
+
261
+
Append the following text to your PR comment to specify the Magento Commerce edition to use when you [Deploy a vanilla Magento instance](#vanilla-pr) or [Deploy an instance based on PR changes](#deploy-pr).
262
+
263
+
```text
264
+
with edition {$edition}
265
+
```
266
+
267
+
Replace `{$edition}` with either of the following values:
268
+
269
+
-`ee` deploys the Magento Commerce edition
270
+
-`b2b` deploys Magento Commerce with B2B modules.
271
+
272
+
For example, append the following text to the PR comment to deploy a {{site.data.var.ee}} instance with B2B modules:
273
+
274
+
```text
275
+
with edition b2b
276
+
```
277
+
278
+
#### Environment
279
+
280
+
Append the following text to your PR comment to specify the version for applications and services to use when you [Deploy a vanilla Magento instance](#vanilla-pr) or [Deploy an instance based on PR changes](#deploy-pr).
281
+
282
+
```text
283
+
with env PHP {$phpVersion}, search-engine ElasticSearch {$searchEngineVersion}, database {$dbEngine} {$dbEngineVersion}
284
+
```
285
+
286
+
Replace variables in the command with the following values as needed for your environment:
287
+
288
+
-`{$phpVersion}`–Specify the PHP version for the instance.
289
+
290
+
-`{$searchEngineVersion}`–Specify the Elasticsearch version for the instance.
291
+
292
+
-`{$dbEngine}`–Specify the database type, either `MariaDB` or `MySQL`.
293
+
294
+
-`{$dbEngineVersion}`–Specify the version of the database engine for the instance.
295
+
296
+
For example, append the following text to the PR comment to deploy an instance with PHP 7.4, Elasticsearch version 7, and MariaDB version 10.4.
297
+
298
+
```text
299
+
with env PHP 7.4, search-engine Elasticsearch 7, database MariaDB 10.4
300
+
```
301
+
302
+
{:.bs-callout-info}
303
+
We generally recommend that you deploy the default environment. Use the custom configuration options only when you require a special configuration to test specfic use cases.
304
+
305
+
#### Add extensions
306
+
307
+
Append the following text to your PR comment to specify extensions to add to an instance when you [Deploy a vanilla Magento instance](#vanilla-pr) or [Deploy an instance based on PR changes](#deploy-pr).
308
+
309
+
```text
310
+
with extensions {$extensionRepo}
311
+
```
312
+
313
+
Replace `{$extensionRepo}` with one or more extension repositories to include when compiling your instance. If you specify multiple repositories, use a comma after each repository. You can specify a specific branch in a repository using the pattern: `org/repo-name:branch-name`. For example:
314
+
315
+
```text
316
+
with extensions magento/security-package:1.0-develop, magento/security-package-ee
317
+
```
318
+
319
+
#### Remove extensions
320
+
321
+
Append the following text to your PR comment to specify extensions that you want to remove from the instance when you [Deploy a vanilla Magento instance](#vanilla-pr) or [Deploy an instance based on PR changes](#deploy-pr).
322
+
323
+
```text
324
+
without extensions {$extensionRepo}
325
+
```
326
+
327
+
Replace `{$extensionRepo}` with one or more extension repositories to remove before compiling your instance. If you specify multiple repositories, use a comma after each repository. For example:
328
+
329
+
```text
330
+
without extensions magento/adobe-stock-integration
331
+
```
332
+
251
333
### Combine multiple pull requests {#combine-pr}
252
334
253
335
To optimize the pull request queue, enter a command with a series of related pull request numbers to merge and test the code. If all tests pass, the entered PRs are merged into the current PR.
Copy file name to clipboardExpand all lines: src/guides/v2.3/config-guide/prod/config-reference-var-name.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -242,7 +242,7 @@ content='
242
242
243
243
* To use values you set in the `$_ENV` array, you must set `variables_order = "EGPCS"` in your `php.ini` file. For details, see [PHP documentation](http://us.php.net/manual/en/ini.core.php#ini.variables-order).
244
244
245
-
* For Magento Commerce Cloud, if you are attempting to override Magento configuration settings using the [Project Web Interface]((https://devdocs.magento.com/guides/v2.3/cloud/project/project-webint-basic.html#project-conf-env-var), you must prepend the variable name with `env:`. For example:
245
+
* For Magento Commerce Cloud, if you are attempting to override Magento configuration settings using the [Project Web Interface](https://devdocs.magento.com/cloud/project/project-webint-basic.html#project-conf-env-var), you must prepend the variable name with `env:`. For example:
Copy file name to clipboardExpand all lines: src/guides/v2.3/frontend-dev-guide/themes/theme-structure.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -136,7 +136,7 @@ The directories and files structure described below is the most extended one. It
136
136
</td>
137
137
<td colspan="1">required for a theme, but optional if it exists in the parent theme</td>
138
138
<td colspan="1">
139
-
This file contains configuration for all storefront product images and thumbnails.
139
+
This file contains configurations for all storefront product images and thumbnails. It also contains product page, gallery widget configurations such as navigation options, fullscreen options and breakpoint conditions.
140
140
</td>
141
141
</tr>
142
142
<tr>
@@ -197,7 +197,7 @@ The directories and files structure described below is the most extended one. It
0 commit comments