Open simoncarre opened 3 years ago
Hello, i've the same problem with update 4.0.61 -> 4.0.126 #15807
did somebody solve this issue?
For me no solution was found, I was forced to reload a save.
Had the same problem in Akeneo 3.2.75. Solved it by applying this patch
--- src/Oro/Bundle/PimDataGridBundle/Resources/public/js/datafilter/filters-column.ts 2022-01-21 18:03:55.817217480 +0100
+++ src/Oro/Bundle/PimDataGridBundle/Resources/public/js/datafilter/filters-column.ts 2022-01-21 18:04:14.893072191 +0100
@@ -217,7 +217,7 @@
for (let groupName in groupedFilters) {
const group: GridFilter[] = groupedFilters[groupName];
const groupElement = this.renderFilterGroup(group, groupName);
- list.appendChild($(groupElement).get(0));
+ list.appendChild($(groupElement).get(0) as any);
}
filterColumn.append(list);
I'm applying the patch via composer.json by running composer require cweagans/composer-patches
and adding this to the "extra" section in composer.json (make sure you add a trailing comma to the line before composer-exit-on-patch-failure:
"composer-exit-on-patch-failure": true,
"patches": {
"akeneo/pim-community-dev": {
"Fix: https://github.com/akeneo/pim-community-dev/issues/15644": "patches/issue-15644.TS2345.argument.of.type.HTMLElement.undefined.is.not.assignable.to.parameter.of.type.Node.patch"
}
}
Looks like it was fixed in later versions via this commit on november 9th 2021: https://github.com/akeneo/pim-community-dev/commit/d4f70f9284cd3e33fd62087c98e1a8781d7f60ef#diff-f37e965cacebaf85f2b2abd78827ffd29691498affb012a8c39ffee0104d2d6e
Hi Akeneo team,
I have an issue when deploying an Akeneo project in version 3.2.84 (during
yarn run webpack
command) :I performed the following steps:
package.json
file with current version : https://github.com/akeneo/pim-community-standard/blob/3.2/package.jsonyarn.lock
andnode_modules
But the issue persists. Do you have an idea of a fix before a possible migration to Akeneo 4.0? Thank you in advance.