I am currently working on my CI drupal build profile using features. What happened however was that the enabled attribute on the search index remained in a permanent dirty state. As shown in the screengrab, only the type was wrong. I started debugging using Xdebug, but got nowhere (the advanced logic of features exporting is beyond me at the moment). I fixed this for the moment by implementing the export function on the SearchApiIndex class, and there casting the enabled attribute to an int before executing the parent export logic.
I hope this helps.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | search-api-index-enabled-int-cast.patch | 651 bytes | joostpluijmers |
| wrong-type.jpg | 28.47 KB | joostpluijmers |
Comments
Comment #1
joostpluijmers commentedComment #2
joostpluijmers commentedUpdated patch path to the modules base path instead of /includes.
Comment #3
drunken monkeyThat's really curious, you're right. However, the question is of course why the initial export would have a different type for the "enabled" property.
In any case, the proposed workaround is certainly not the correct fix here, even if it is a bug somewhere. The fix should either be in Entity API or in Features, and certainly not hard-coded for a single property (when, e.g., "read_only" could easily have the same problem). (Also, your fix would override everyone else's index features, as the property seems to be a string normally.) But first you'd need to find out what caused the property to be initially exported as an integer.
Comment #4
legolasboThis issue has not seen activity in over 2,5 years. I am therefore closing this issue to clean up the issue queue. Feel free to re-open and update this issue if you feel this issue is still relevant and of importance.