[ic] "SOLVED" Update to update: Re: AddAttr only UserTags sometimes work, sometimes fail
jon at endpoint.com
Wed Jul 7 20:54:40 UTC 2010
On Wed, 7 Jul 2010, Chris Keane wrote:
> It turns out that in Parse, the $Order hash doesn't keep a
> catalog-specific Order for each UserTag but that the Order is global. So
> if you have a UserTag:
> UserTag goo Order arg1 arg2
> in one catalog, and
> UserTag goo Order arg2 arg3 arg4
> in a second catalog running on the same server, the $Order hash will get
> overwritten. The behavior indicates that it will be OK until the 2nd
> version is called, thereafter the 2nd version's arguments take
> Anyway, changing all the catalog-customized UserTags to have the same
> arguments seems to have solved the problem.
> I'm sorry this was not a more interesting problem. After being an
> Interchange proponent for 8 years this problem had us moments away from
> ditching Interchange for a more stable and active platform.
Nice find, Chris!
Please don't read into the lack of list help on such a thorny problem that
apparently nobody else has ever run into, that Interchange isn't stable or
active. Just like you, most of us are busy doing our own development and
solving our own problems and only have time to dive into others' problems
if we have an inkling of what might be wrong and how we can help without
taking hours of time.
You happened to come across something obscure that none of us had any
input on. As David said, now that you've found the problem, it's a lot
more likely someone will be able to take the time to fix it.
End Point Corporation
More information about the interchange-users