Closed Morgy93 closed 3 years ago
Hi @Morgy93
Indeed, I can reproduce this problem on a clean Magento 2.4.2 installation!
I've only tested this module on Magento 2.4.0 so far, not on 2.4.1 or 2.4.2, so something in those versions has changed which must have caused this problem.
I'll have a look later on for a way to solve this.
Thanks!
Magento 2.4.2 came with this change which starts causing this issue: https://github.com/magento/magento2/commit/2638e0ffae57f351c512e47a0295d4c2d376681a
This feels like a bug in Magento because a Collection isn't being forced to implement a getSelect()
method.
And since we use the Collection to read from a json file and not from the database this might be difficult to implement.
Possible solutions:
This might take a while until fixed since I don't have that much free time, but I'll see what I can do 🙂
Is fixed in version 1.2.1 of this module.
I picked option 4 and introduced a silly workaround for the issue. The other options would be better for future improvements, but would take a lot longer to implement.
Also, we aren't the only ones who run into this problem with Magento 2.4.2, see: https://github.com/magento/magento2/issues/32292
Thanks for the report @Morgy93!
Hello,
on
/baldwin_urldataintegritychecker/catalog_category_urlPath/
I'm getting the following error:All other grids are throwing the same exception.
Using version 1.2.0 of this module and Magento version 2.4.2 - maybe it is incompatible?