This notice unfortunately is a bug that we are working on a fix for.
What is happening is that our field now only accepts integer values, not strings. So if you enter just plain integers like 15, 120, 0, 1, etc., this error should not appear.
But if you have a string like “Free” or “Pay at door”, then this error will appear.
We are fixing this! Strings will be allowed eventually again. But that’s what this bug is for now. 🙁
I’m really sorry about the inconveniences arising from this. Please let me know if this information is helpful at all for now, and if you have any more thoughts on this matter.
Sincerely,
George