Closed jeremyboggs closed 11 years ago
Updating this issue to more accurately report the problem. It has nothing to do with whether the timeline is public or not.
The trickier thing will be to fix the screwed up values for the query on existing records. It'd be a shame to have to ask folks to just create new timelines.
The model is set up so that every time a NeatlineTime record gets saved, the value for the query gets serialized. This means it even serializes an already-serialized value, thus making the query invalid for retrieving items. This is Jeremy's fault, and he should fix this nonsense.