@graphcommerce/docs 7.1.0-canary.30 → 7.1.0-canary.32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Change Log
2
2
 
3
+ ## 7.1.0-canary.32
4
+
5
+ ## 7.1.0-canary.31
6
+
7
+ ### Minor Changes
8
+
9
+ - [#2106](https://github.com/graphcommerce-org/graphcommerce/pull/2106) [`9f8c3cac2`](https://github.com/graphcommerce-org/graphcommerce/commit/9f8c3cac214006315055f37cf8d4a783eb99a7ec) - Split off Magento known issues to separate page ([@hnsr](https://github.com/hnsr))
10
+
3
11
  ## 7.1.0-canary.30
4
12
 
5
13
  ## 7.1.0-canary.29
@@ -0,0 +1,54 @@
1
+ ---
2
+ menu: Known issues
3
+ ---
4
+
5
+ # Known issues
6
+
7
+ An overview of bugs and limitations you may run into with Magento's GraphQL API:
8
+
9
+ ## Cart-related mutations result in `Can not find cart with ID` or `Cart isn't active` errors
10
+
11
+ Affected Magento versions:
12
+
13
+ - `2.4.7`: only `2.4.7-beta1`
14
+ - `2.4.6`: all versions
15
+
16
+ This is caused by a regression which results in some GraphQL errors no longer
17
+ getting a category extension string (such as `graphql-no-such-entity`).
18
+ Normally, these errors are handling by automatically creating a new cart, but
19
+ without the proper error category this error-handling logic is nog triggered.
20
+
21
+ As a workaround, you can apply
22
+ [cart-error-category.patch](./patches/cart-error-category.patch).
23
+
24
+ See also
25
+ https://github.com/magento/magento2/commit/49cbe774020d3dfa6ee2b8702376a947801c9971
26
+
27
+ ## Customer is forced to sign up, even if already registered
28
+
29
+ Affected Magento versions:
30
+
31
+ - `2.4.7` and all future release series
32
+ - `2.4.6`: `2.4.6-p1` and up
33
+ - `2.4.5`: `2.4.5-p3` and up
34
+ - `2.4.4`: `2.4.4-p4` and up
35
+
36
+ During customer login, GraphCommerce queries Magento to determine whether the
37
+ customer account already exists or not. If not, the sign-up form is shown
38
+ instead.
39
+
40
+ In affected Magento versions, the behavior of the `isEmailAvailable` query that
41
+ is used to do this was made dependent on the `Enable Guest Checkout Login`
42
+ configuration setting. If disabled, this query will always return `true`,
43
+ resulting in the sign-up form always being shown, even if the customer already
44
+ exists.
45
+
46
+ To solve this, the following setting must be set to `Yes`:
47
+ `Stores -> Configuration -> Sales -> Checkout -> Checkout Options -> Enable Guest Checkout Login`
48
+
49
+ See also
50
+ https://developer.adobe.com/commerce/php/development/backward-incompatible-changes/highlights/#isemailavailable-api
51
+
52
+ ## Next steps
53
+
54
+ - [Overview](./readme)
package/magento/readme.md CHANGED
@@ -7,6 +7,12 @@ menu: Overview
7
7
  To integrate with Magento, most of the functionality should work out-of-the box
8
8
  if Magento exposes a working GraphQL API.
9
9
 
10
+ Some additional configuration may be required, which is documented below.
11
+
12
+ Currently, the GraphQL API also has some bugs and limitations which in some
13
+ cases requires a patch to work around, please see
14
+ [Known issues](./known-issues.md)
15
+
10
16
  ## Magento configuration
11
17
 
12
18
  ### Configure Base Link Url to get emails working
@@ -64,16 +70,6 @@ Remove the URL suffixes from products and categories. (default is `.html`)
64
70
  `Stores -> Configuration -> Catalog -> Catalog -> Search Engine Optimization -> Product URL Suffix`
65
71
  `Stores -> Configuration -> Catalog -> Catalog -> Search Engine Optimization -> Category URL Suffix`
66
72
 
67
- ### Enable guest checkout login
68
-
69
- During customer login, GraphCommerce queries Magento to determine whether the
70
- customer account already exists. To do this the following setting must be set to
71
- Yes:
72
- `Stores -> Configuration -> Sales -> Checkout -> Checkout Options -> Enable Guest Checkout Login`
73
-
74
- If this is not set correctly, customers will not be able to log in, since they
75
- will always be prompted to create a new account.
76
-
77
73
  ## Optional packages
78
74
 
79
75
  - [Store Pickup / MSI](https://github.com/graphcommerce-org/graphcommerce/tree/main/packages/magento-cart-pickup)
@@ -92,22 +88,4 @@ will always be prompted to create a new account.
92
88
 
93
89
  - [Full feature list](../feature-list.md)
94
90
  - [SEO Migration](./seo-migration.md)
95
-
96
- ## Known issues
97
-
98
- An overview of bugs and limitations you may run into with Magento's GraphQL API:
99
-
100
- ### Cart-related mutations result `Can not find cart with ID` or `Cart isn't active` errors
101
-
102
- This is caused by a regression in Magento 2.4.6, which results in some GraphQL
103
- errors no longer getting a category extension string (such as
104
- `graphql-no-such-entity`). Normally, these errors are handling by automatically
105
- creating a new cart, but without the proper error category this error-handling
106
- logic is nog triggered.
107
-
108
- As a workaround, you can apply
109
- [cart-error-category.patch](./patches/cart-error-category.patch). This
110
- regression is fixed as of Magento 2.4.7-beta2.
111
-
112
- See also
113
- https://github.com/magento/magento2/commit/49cbe774020d3dfa6ee2b8702376a947801c9971
91
+ - [Known issues](./known-issues.md)
package/package.json CHANGED
@@ -2,10 +2,10 @@
2
2
  "name": "@graphcommerce/docs",
3
3
  "homepage": "https://www.graphcommerce.org/docs",
4
4
  "repository": "github:graphcommerce-org/graphcommerce/docs",
5
- "version": "7.1.0-canary.30",
5
+ "version": "7.1.0-canary.32",
6
6
  "sideEffects": true,
7
7
  "devDependencies": {
8
- "@graphcommerce/prettier-config-pwa": "7.1.0-canary.30"
8
+ "@graphcommerce/prettier-config-pwa": "7.1.0-canary.32"
9
9
  },
10
10
  "prettier": "@graphcommerce/prettier-config-pwa"
11
11
  }