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
Copy file name to clipboardExpand all lines: patches.json
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@
23
23
},
24
24
"MDVA-30052": {
25
25
"magento/magento2-base": {
26
-
"Customer data section invalidation logic has been improved. This release introduces a new way of invalidating all customer sections data that avoids a known issue with local storage when custom `sections.xml` invalidations are active. (Previously, private content (local storage) was not correctly populated when you had a custom *etc/frontend/sections.xml* with action invalidations).": {
26
+
"Fixes the issue with private content (local storage) not being populated correctly, which resulted in performance problems.": {
"Product and catalog caches will expire as scheduled. Previously, caches expire daily, as сron runs the 'catalogrule_apply_all' task once a day which re-indexes all the catalog rules and its dependent indexers and clears the cache for all products and categories.": {
35
+
"Fixes the issue with product and catalog caches expiring daily, though being scheduled to expire differently.": {
"Code was not storing false values for custom attributes in Elastic Search, so filter was possible using 'No' for boolean attributes using layered navigation. To address that, some boolean checks have been replaces for null checks, and an array_filter call has been erased completely as no callback function was provided in it, thus always returning false as 'all entries of array equal to FALSE (see converting to boolean) will be removed'.": {
44
+
"Fixes the issue with layered navigation, where the 'No' value for boolean type product attributes was not included in layered navigation if Elasticsearch was used as a search engine.": {
"Big data customer export issue. Memory leak prevented by adding clearing of Customer objects in \\Magento\\Framework\\Model\\ResourceModel\\Db\\VersionControl\\Snapshot class": {
53
+
"Fixes an issue where exporting of big amounts of data failed because of memory leak.": {
"After the company has been created through the API, the intended plugin will check if the company is created and dispatch the two emails accordingly.": {
62
+
"Fixes a B2B issue where no required new company emails are sent out if a company is created by API.": {
"Issue fixed: Two gift card codes can be seen for the order.\nRoot Cause: cron jobs called \\Magento\\GiftCard\\Observer\\GenerateGiftCardAccountsInvoice::execute() and this method did not check if giftcard codes already were generated during invoice creation.": {
71
+
"Fixes an issue where gift card orders contained two codes instead one.": {
0 commit comments