Thanks Geoff,

I was thinking that an automated fix would be a bit tricky and as this
does not happen very often it is manageable by cleaning the wizards.

Just wanted to get the info into the group in case anyone else was
encountering a similar problem.

Chris.

On Jun 9, 3:41 am, modius <[email protected]> wrote:
> On Jun 8, 5:21 pm, Chris Kent <[email protected]> wrote:
>
> > But, there were a number of records in dmwizard that were created
> > before the new navigator property was added to dmnews and when these
> > content items were edited an error occurred.
>
> The wizard "snapshots" the content object you are working with.  If
> the contributor doesn't "Save" or "Cancel" the wizard -- eg. browses
> away, crashes browser, etc - the wizard will attempt to resume where
> the contributor left off.  If you change the underlying data model in
> the interim its going to error because what it sees in the "snapshot"
> and what is being compared in the database are different.
>
> > Have not had time to look at code to suggest a fix, but a workaround
> > is to clear dmwizard after updating any content types.
>
> You can delete all outstanding or active wizards through the Admin >
> Developer Utils > Reload Application and select "Wizards". Probably
> something that should be part of any update where the model has
> changed.
>
> A potential fix would be to trap this specific error, explain why
> there is a problem, and provide a link to delete and restart the
> Wizard.  Some sort of auto-repair function is likely a lot trickier to
> write given the potential variations.
>
> Hope that helps,
>
> -- geoffhttp://twitter.com/modius
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to