Looks like you have the right idea at the end.
Processformobjects is a loop tag - it finds all forms that were submitted
for the given criteria (typename/objectid) and processes each. A couple of
points:
- If there aren't errors the data gets saved as well
- If you do manual processing inside the loop and don't want the
object automatically saved you can break the save with ft:break
- You can manually raise an error with ft:advice
- Changes made to the properties struct are saved
Blair
On Tue, Mar 4, 2008 at 4:09 PM, Matthew Williams <
[EMAIL PROTECTED]> wrote:
>
> Ah, yes, makes sense. Then, rather than extending farUser, I'm going
> to give this a whirl. dmCSS still uses the old method of rendering
> edits (where there is an _dmCSS/edit.cfm). I just extended farUser
> into my project and created an edit for it. I've got the following
> code inserted for the form display. I'm just not sure how I'm going
> to get the form to process. I'm going to have a slosh through
> processform and formobjects and see how I can get this to work.
>
> <ft:form action="">
> <ft:object stobject="#stobj#" typename="farUser"
> format="edit"
> helptext="HTML not allowed. Links will be automatically activated." /
> >
> <cfset oProfile = createObject("component",
> application.types.dmProfile.typePath)>
> <cfset stProfile = oProfile.getProfileAPT(#stObj.userid#)>
>
> <ft:object objectid="#stProfile.objectid#"
>
> lexcludefields="bReceiveEmail,label,username,userdirectory,overviewhome,objectid,notes,bactive"
> typename="dmProfile" format="edit" helptext="HTML not allowed. Links
> will be automatically activated." />
> <ft:farcrybutton value="Save" class="button" bInPanel="0"
> />
> </ft:form>
>
> The data all submits correctly, but the dmProfile does not process
> correctly. I've tried the following, but it's not working. I'm
> assuming it's due to the fact that there are two values in
> farcryformprefixes and that they don't have the same type. Worst
> case, really, is that I just populate the struct for dmProfile by hand
> and just process it that way. Still, saves me a ton of time. Since
> the typename is passed, I'll just have to work out the best way to
> separate out the content. Dang I love the fact that 90% of this is
> all built in ;).
>
> <ft:processform action="Save" >
> <!--- process action items --->
> <ft:processformobjects typename="farUser" r_stproperties="stprops">
> </ft:processformobjects>
> <ft:processformobjects typename="dmProfile"
> r_stproperties="stprops2">
> </ft:processformobjects>
>
> </ft:processform>
>
>
> Matthew Williams
> Geodesic GraFX
> www.geodesicgrafx.com/blog
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"farcry-dev" group.
To post to this group, send email to farcry-dev@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
