- 🇨🇿Czech Republic siva01
I have search_api 1.28.0 and patch fix that issue for me.
- Status changed to Needs review
about 1 year ago 1:33pm 29 March 2023 - 🇵🇹Portugal rutiolma
This patch fixes the problem but in my case it introduces a huge overload. I tried a similar approach which seems to be lighter.
The last submitted patch, 7: fix_could_not_load_warning-3313569-7.patch, failed testing. View results →
- last update
about 1 year ago 521 pass, 2 fail - last update
about 1 year ago 538 pass - 🇦🇹Austria drunken monkey Vienna, Austria
Thanks a lot for reporting this issue and already finding a solution.
Both your analysis and the solution make sense, even though it’s of course unfortunate that we have to load a potentially large number of entities just to get their translations. But yes, no way around that, I fear – unless we just want people to have to live with the error in the log messages, which doesn’t really do any harm, either, as far as I can see. (Also, there is no error at all if “Index items immediately” is disabled.)
So maybe we should actually make this fix optional? Not sure. I might at least mention it in the release notes for the next release.Anyways, attached is a slightly modified version of the patch, complete with a regression test. Please test/review, and tell me your opinion on the above.
The last submitted patch, 10: 3313569-10--referenced_entity_tracking_translations--tests_only.patch, failed testing. View results →