If you want to change the properties before saving you can modify stProperties inside processformobjects. Farcry will save the updated properties. The code you've sent should not be saving after cancel, so I'm not sure how that's happening.
On Fri, Jun 15, 2012 at 10:01 AM, Marco van den Oever < [email protected]> wrote: > Emmm it's a custom edit, i just want to save the changes and ad some > custom actions in it. > The javascript is what you gave me so i thought it was needed in there, > isn't the javascript needed for the custom edit to work? > The processFormObjects is saved to session so i can check if it's saved ok > and then write the data to the item, i have learned that from you :) > > Op vrijdag 15 juni 2012 01:30:34 UTC+2 schreef Blair McK het volgende: > >> I don't understand what you're trying to do. What is the purpose of the >> javascript? Why do you resave the object after processformobjects saves it? >> >> >> On Thu, Jun 14, 2012 at 10:08 PM, Marco van den Oever < >> [email protected]> wrote: >> >>> When i click on edit or save the page reloads and in both actions (also >>> cancel) the changes are saved, also while i am using an exit="true" the >>> page reloads and not go to the items overview: >>> >>> ------- >>> >>> <cfsetting enablecfoutputonly="true" /> >>> <cfimport taglib="/farcry/core/tags/**formtools" prefix="ft" /> >>> <cfimport taglib="/farcry/core/tags/**extjs" prefix="extjs" /> >>> >>> <ft:processForm action="Cancel" exit="true" /> >>> >>> <ft:processForm action="Save"> >>> <ft:processFormObjects typename="advertenties" bSessionOnly="true" /> >>> <!--- if a advertenties object was succesfully saved ---> >>> <cfif len(lSavedObjectIDs)> >>> <!--- set the advertentie object data from session to variable ---> >>> <cfset obj = createObject >>> ('component',application.**stcoapi.advertenties.typePath) /> >>> <cfset advertentie = getData(objectid=**lSavedObjectIDs) /> >>> <cfset stprops = {} /> >>> <cfset stprops.objectid = advertentie.objectid /> >>> <cfset stprops.emailadres = advertentie.emailadres /> >>> <cfset stprops.titel = advertentie.titel /> >>> <cfset stprops.categorie = advertentie.categorie /> >>> <cfset stprops.tekst = advertentie.tekst /> >>> <cfset stprops.foto1 = advertentie.foto1 /> >>> <cfset stprops.foto2 = advertentie.foto2 /> >>> <cfset stprops.foto3 = advertentie.foto3 /> >>> <cfset stprops.foto4 = advertentie.foto4 /> >>> <cfset stprops.website = advertentie.website /> >>> <cfset stprops.ikwij = advertentie.ikwij /> >>> <cfset stprops.hits = advertentie.hits /> >>> <cfset stprops.vergoeding = advertentie.vergoeding /> >>> <cfset stprops.regio = advertentie.regio /> >>> <cfset stprops.ipadres = advertentie.ipadres /> >>> <cfset stprops.actief = advertentie.actief /> >>> <cfset obj.setData(stProperties=**stprops) /> >>> </cfif> >>> </ft:processForm> >>> >>> >>> <ft:form> >>> <ft:object typename="advertenties" objectid="#stobj.objectid#" >>> r_stPrefix="prefix" legend="General Details" /> >>> >>> >>> <extjs:onReady><cfoutput> >>> $j("###prefix#lTypenames").on(**'change', function(){ >>> var el = $j("##editWebskins").load("#**application.url.webtop#/* >>> *facade/workflowFacade.cfc?**method=**renderWorkflowDefWebskins",{ >>> workflowDefID: '#stObj.objectid#', >>> lTypenames: '#prefix#lTypenames' >>> },function(){ >>> el.slideOut(); >>> }); >>> }); >>> </cfoutput></extjs:onReady> >>> >>> >>> <ft:farcryButtonPanel> >>> <ft:farcryButton value="Save" /> >>> <ft:farcryButton value="Cancel" /> >>> </ft:farcryButtonPanel> >>> </ft:form> >>> <cfsetting enablecfoutputonly="false" /> >>> >>> ------- >>> >>> Op donderdag 14 juni 2012 02:30:45 UTC+2 schreef Blair McK het volgende: >>> >>>> The primary problem with that block is the Ext code. This is my >>>> untested replacement. I've removed a lot of irrelevant custom options: >>>> <skin:onReady><cfoutput> >>>> $j("###prefix#lTypenames").on(****'change', function(){ >>>> var el = $j("##editWebskins").load("#**ap** >>>> plication.url.webtop#/**facade/**workflowFacade.cfc?**method=**rend**erWorkflowDefWebskins",{ >>>> >>>> workflowDefID: '#stObj.objectid#', >>>> lTypenames: '#prefix#lTypenames' >>>> },function(){ >>>> el.slideOut(); >>>> }); >>>> }); >>>> </cfoutput></extjs:onReady> >>>> >>>> Blair >>>> >>>> On Wed, Jun 13, 2012 at 11:51 PM, Marco van den Oever < >>>> [email protected]> wrote: >>>> >>>>> Hi all, i have copied/paste/modified a custom edit of a project made >>>>> with farcry 5.0.x. >>>>> I now see that the css is not ok in the webtop edit page. >>>>> >>>>> Anyone has an example on how to handle this, some example: >>>>> >>>>> <ft:form> >>>>> <ft:object typename="advertenties" objectid="#stobj.objectid#" >>>>> r_stPrefix="prefix" legend="General Details" /> >>>>> >>>>> <extjs:onReady> <cfoutput> >>>>> Ext.get("#prefix#lTypenames").****on('change', >>>>> this.onClick, this, { >>>>> buffer: 500, >>>>> fn: function() { >>>>> renderWorkflowDefWebskins('#**st**obj.objectid#', >>>>> Ext.get('#prefix#lTypenames').****dom.value); >>>>> } >>>>> }); >>>>> >>>>> function renderWorkflowDefWebskins(**work**flowDefID,lTypenames) >>>>> { >>>>> >>>>> var el = Ext.get("editWebskins"); >>>>> >>>>> if (workflowDefID != '') { >>>>> >>>>> el.slideOut('t', { >>>>> easing: 'easeOut', >>>>> duration: .5, >>>>> remove: false, >>>>> useDisplay: true, >>>>> callback: function() { >>>>> el.load({ >>>>> url: "#application.url.webtop#/**faca**de/workflowFacade.cfc?** >>>>> method=**r**enderWorkflowDefWebskins", >>>>> scripts: true, >>>>> autoAbort:true, >>>>> callback: function() { >>>>> el.slideIn('t', { >>>>> easing: 'easeIn', >>>>> duration: .5, >>>>> remove: false, >>>>> useDisplay: true >>>>> }) >>>>> }, >>>>> params: { >>>>> workflowDefID: workflowDefID, >>>>> lTypenames: lTypenames >>>>> } >>>>> }); >>>>> } >>>>> }) >>>>> >>>>> >>>>> >>>>> } >>>>> >>>>> } </cfoutput> </extjs:onReady> >>>>> <ft:farcryButtonPanel> >>>>> <ft:farcryButton value="Save" /> >>>>> <ft:farcryButton value="Cancel" /> >>>>> </ft:farcryButtonPanel> >>>>> </ft:form> >>>>> >>>>> Thanks. >>>>> >>>>> -- >>>>> You received this message cos you are subscribed to "farcry-dev" >>>>> Google group. >>>>> To post, email: [email protected] >>>>> To unsubscribe, email: >>>>> farcry-dev+unsubscribe@**googleg**roups.com<farcry-dev%[email protected]> >>>>> For more options: >>>>> http://groups.google.com/**group**/farcry-dev<http://groups.google.com/group/farcry-dev> >>>>> ------------------------------****-- >>>>> Follow us on Twitter: http://twitter.com/farcry >>>> >>>> >>>> -- >>> You received this message cos you are subscribed to "farcry-dev" Google >>> group. >>> To post, email: [email protected] >>> To unsubscribe, email: >>> farcry-dev+unsubscribe@**googlegroups.com<farcry-dev%[email protected]> >>> For more options: >>> http://groups.google.com/**group/farcry-dev<http://groups.google.com/group/farcry-dev> >>> ------------------------------**-- >>> Follow us on Twitter: http://twitter.com/farcry >>> >> >> -- > 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 > -- 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
