I discovered a Drupal bug that affects our selector variable.
The bug: when creating a new Boolean field like Selector, Content Type asks you which value you want to assign to “On value” and “Off value” (here: https://edgeryders.eu/en/admin/structure/types/manage/post/fields/field_selector). The help text says default is “1” and “0” respectively. But this is not true: if you leave the fields blank, it will assign the empty string ("") to both “On” and “Off value”. Once you have data in that field, you cannot change this setting anymore.
- All posts created since 2014-12-05 (included) show up as having Selector == ""
- Posts created up to 2014-12-05 with Selector == "" are included in the Stewardship conversation.
- Posts created up to 2014-12-05 with Selector == Null are not included in the Stewardship conversation.
What we need to do:
- Create a new field, call it SelectorNew.
- Set its values to "1" (On value) and "0" (Off value), writing those values explicitly in the respective fields.
- Write a SQL query that says (pseudocode)
for each post:
if not Selector(post) == Null AND creation_date < 2014-12-05:
SelectorNew(post) == “1”
At that point, we can delete Selector and keep working with the Assembl process on SelectorNew.