The issue wasn't that the label property wasn't deployed, but that it was empty (null string). At least, that's how I understood it. Those are two different issues, and the empty-ness issue I would imagine is much harder to debug. In the end, simply setting "bAutoLabel" (component wise) or "bLabel" (for a property) would solve that issue. Check the actual names, but those two tags can be used in FC to specify the label.
Tomek On Thu, Jun 25, 2009 at 11:43 AM, Marco van den Oever < [email protected]> wrote: > > That is indeed good to know, i am wondering, isn't there a way that > these kind of stuff is more clear to debug? So if there is something > missing that should be there there is a sort of checker / error > reporter that tels you there's something missing. > > That shouldn't be to hard and save a lot of time and frustration. > > Idea? > > http://bugs.farcrycms.org/browse/FC-1904 > > On Jun 25, 5:29 pm, Tomek Kott <[email protected]> wrote: > > didn't know that, and that's good to know! Glad you got it fixed. > > > > Tomek > > > > On Thu, Jun 25, 2009 at 8:34 AM, Phil Kemp <[email protected]> > wrote: > > > > > I found the solution. > > > > > In the FarCry core code, there is a clause which translates to "if the > > > label > > > field is emtpy, don't do workflow action". My type definition didn't > have a > > > label property and hence, no workflow actions. > > > -- > > > View this message in context: > > >http://www.nabble.com/Custom-type-won%27t-approve-tp24143221s621p2420. > .. > > > Sent from the FarCry - Dev mailing list archive at Nabble.com. > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry -~----------~----~----~----~------~----~------~--~---
