Matthias Zeis
Matthias Zeis
As far as I see, `npm install` should be fine for `Resources/app/storefront/package.json` because all packages have exact versions defined. For `Resources/app/administration/package.json` or plugins, this might give unwanted results because `npm...
@AndreasA I am not a npm expert, but from what I know, `npm install` can update packages even when `package-lock.json` exists if there are no exact version constraints. See https://stackoverflow.com/a/70212123/558524...
Hi, can't give a timeline yet but I want to have a look at it!
Did one of you fix it yourself and would be happy to send a PR? If not, is this fix still needed or should I close the issue?
Hi @romainruaud, FYI: We installed Elastic Suite 2.11.3.2 on Magento Open Source 2.4.6-p2, and we still got the error on running `bin/magento setup:upgrade` if the indexers are set to "Update...
I'm arriving late to the party, but if anyone is still looking for this: in modern versions, you use `bin/magento` instead to the above settings to configure the profiler: ~~~...
I'm facing the same issue (EE 1.14.2.0, Aoe_Scheduler 1.5.0). It only appeared after we made these changes: * Switched all indexes to be updated when scheduled * Added the Solr-Extension...
I updated an old installation with the current master, didn't have a `var/aoe_profiler.xml` file yet and entries came in immediately. After I added the file using the default content with...
@robbieaverill We are doing that at the moment but using `dev-master` (even with a defined commit) has some disadvantages opposed to tags.