Editing the configuration of configurable fields (e.g., "Aggregated fields" and "Rendered HTML output") will currently result in an uncaught exception (serializing the database connection), at least in some cases. This was most likely caused by #2650986: Fix entity loading in SearchApiFieldTrait.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2910918-2--fix_field_config_form.patch | 7.52 KB | drunken monkey |
| #2 | 2910918-2--fix_field_config_form--tests_only.patch | 5.03 KB | drunken monkey |
Comments
Comment #2
drunken monkeyOK, apparently this is just due to the index being serialized with the
$propertiesproperty, which can apparently contain a reference to the database under some circumstances. I regrettably wasn't able to reproduce this in theIntegrationTest, but just added a more direct check in theEntitySerializationTest. Also, doing this I stumbled over a few more bugs, and also improvedIntegrationTesta bit, so still something, I'd say.Comment #4
borisson_Only one thing that raised my eyebrows.
Are you sure about this change?
Comment #5
drunken monkeyThanks a lot for reviewing!
Kinda? I agree, normally we should use the interface. But a), we're explicitly testing that class, so it makes sense to specify it; and b), on a more practical note,
__sleep()is otherwise "not found on this class" by the IDE, because it's of course not listed on the interface. So I think I'm more in favor of this change, though I know it looks a bit weird.Comment #6
borisson_Ok, that sounds good! I was just wondering to make sure that you didn't accidentally make that change :)
Comment #8
drunken monkeySure, makes sense, of course. Thanks again for reviewing!
Committed.