Closed (fixed)
Project:
Invite
Version:
7.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 May 2016 at 17:32 UTC
Updated:
24 Nov 2016 at 14:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
ryan osītis commentedThat is indeed what the problem was.
Comment #3
ryan osītis commentedComment #4
SpartyDan commentedThe status field might already exist on the invite table with incorrect settings. For example 'not null' might be set to FALSE when it needs to be set to true.
Therefore, we need to check if the status field exists in the invite table. If it does drop it.
We could update the properties of the status field but dropping it and re-adding is easier. Dropping the status field has no negative consequences for our data because this update hook is going to overwrite all the values in the status field later in the hook.
I believe that this is a more robust solution than #2 because it doesn't assume that the field exists and is properly formatted.
Comment #5
SpartyDan commentedCommitted to 7.x-4.x
Thank you!