Re: Re: Setting a custom field in flowscript alters value of another field

> Paul Focke <paul@...> writes:
>
>>
>>
>> Are you experiencing the same problems when adding custom fields through the
> default daisy editor?
>
> Hi Paul,
>
> Thanks for the reply! I ran some tests in the default Daisy editor and I believe
> I'm seeing the same behavior (so that if I add a custom field and save, my date
> field decrements by one, if I add two custom fields, it decrements by two, etc.)
>
> I'm confident that our code isn't touching the date field - if we comment out
> the setCustomField() call (and no other code) the date field doesn't get updated.
>
> We're running Daisy 2.2 - strangely, as far as I can tell, this only started
> happening recently, and we didn't make any changes (to the extension or to Daisy
> itself) that I know of.
>
> Thanks for the tip on the hit count, too! We weren't aware of that - our
> navigation trees are pretty small - generally ~40-80 documents in a tree for a
> site - and statically defined (no queries). I'm not sure whether switching
> implementations would be worth it right now, but I'll make sure to note it for
> the future!
>
> We've actually moved to a different implementation for this date field for now,
> so it's not urgent for us to get this fixed. I'm still curious as to what
> the problem could have been, though :). Let me know if I can provide any more
> information!
>
> Thanks,
>
> Nick
>