aha that would be it, thanks Blair.

On Sep 26, 11:00 am, "Blair McKenzie" <[EMAIL PROTECTED]> wrote:
> In FC 3 wizard (or PLP) data was stored in temporary files in the core/plp
> directory somewhere. I have found that if I add a new property to a type
> then try to resume a previous wizard I would get that error. Basically when
> you go to edit a type that hasn't been finished off, all the data comes from
> the file instead of the database. So the data is old, but the save handler
> etc, is using the new schema.
>
> Try clearing out the PLP stores. At worst, you will lose your place in a few
> edit wizards.
>
> Blair
>
> On 9/26/07, bsmith <[EMAIL PROTECTED]> wrote:
>
>
>
> > aha hacking through farcry is fun :) thanks for your help Jake.
>
> > On Sep 26, 10:09 am, "Jake Churchill" <[EMAIL PROTECTED]> wrote:
> > > I could see that being a problem also.  Might need to test for valid
> > values
> > > and if they don't exist, create a blank wddx packet to mimic it coming
> > from
> > > the DB.  I tend to hack my way through things though so this might not
> > be
> > > the best option :)
>
> > > On 9/25/07, bsmith <[EMAIL PROTECTED]> wrote:
>
> > > > To hazard a guess, it could be that where the data is coming from is
> > > > actually a wddx package held in the database, instead of simply being
> > > > pulled from the table... ?
>
> > > > On Sep 26, 9:54 am, bsmith <[EMAIL PROTECTED]> wrote:
> > > > > It's fine on insert, as well as on edit for most of the records, but
> > > > > some of them (created before the new property existed) fail when
> > > > > trying to reference the new property... it is pretty strange.
>
> > > > > B.
>
> > > > > On Sep 25, 7:52 pm, "Jake Churchill" <[EMAIL PROTECTED]> wrote:
>
> > > > > > Does the error only happen when updating an existing record or
> > does it
> > > > also
> > > > > > happen on insert?  My guess is that there's an error in your edit
> > form
> > > > and
> > > > > > output.propertyName is not getting defaulted to anything.
>
> > > > > > -----Original Message-----
> > > > > > From: [email protected] [mailto:
> > [EMAIL PROTECTED]
> > > > On
>
> > > > > > Behalf Of bsmith
> > > > > > Sent: Tuesday, September 25, 2007 1:13 AM
> > > > > > To: farcry-dev
> > > > > > Subject: [farcry-dev] Re: New Custom Type, Property Not found on
> > Edit
> > > > (FC3)
>
> > > > > > Ah, this is actually on Farcry 3.0.2
>
> > > > > > On Sep 25, 1:07 pm, "Derek Westfall" <[EMAIL PROTECTED]> wrote:
> > > > > > > In-process editing wizard?
>
> > > > > > > If you delete the associated row from the dmWizard table that
> > should
> > > > take
> > > > > > > care of it.
>
> > > > > > > Derek
>
> > > > > > > > -----Original Message-----
> > > > > > > > From: [email protected]
> > > > > > > > [mailto:[EMAIL PROTECTED] On Behalf Of bsmith
> > > > > > > > Sent: Monday, September 24, 2007 9:53 PM
> > > > > > > > To: farcry-dev
> > > > > > > > Subject: [farcry-dev] New Custom Type, Property Not found on
> > > > > > > > Edit (FC3)
>
> > > > > > > > Hi All,
>
> > > > > > > > I've added a property to my custom type, deployed it and it
> > > > > > > > works fine when I add new records to the type, or update
> > > > > > > > certain records.
>
> > > > > > > > However, on certain records the edit form fails telling me
> > > > > > > > that output.
> > > > > > > > (PropertyName) is not defined.
>
> > > > > > > > I've found I can solve this by deleting and recreating the
> > > > > > > > record, but what is the reason that this property doesn't
> > > > > > > > exist for certain records?
>
> > > > > > > > I figured it'd be an in-memory cache, but updating the app
> > > > > > > > has not had any effect.
>
> > > > > > > > Any ideas?
>
> > > > > > > > B.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to