In other words you only need to copy the edit handler and modify the individual step you are adding or overriding.
I wish I knew that was available before. I'll change my code to that instead of using the cfscript to write the local variables. So instead of all these steps:
======================
5. modify your new copy of edit.cfm and add the following anywhere above the plp call
<cfscript>
Variables.stepDir = "farcry/farcry_core/packages/types/_dmNews/plpEdit/";
Variables.CustomStepDir = "farcry/#application.applicationname#/packages/system/_dmNews/plpEdit/";
</cfscript>
6. in the same file, modify the plp call:
6a. Set stepDir=""
6b. for the existing plp steps change their location to be similar to the following:
<farcry:plpstep name="start" template="#Variables.stepDir#start.cfm">
6c. When you add your own custom steps, have them look similar to the following:
<farcry:plpstep name="extrastep" template="#Variables.CustomStepDir#extrastep.cfm">
======================
I could just shorten it down to:
====================== 5. modify your new copy of edit.cfm and add the following plp step: <farcry:plpstep name="extrastep" Stepdir="farcry/#application.applicationname#/packages/system/_dmNews/plpEdit/" template="extrastep.cfm"> ======================
As long as this will override the Stepdir="xyz" in the plp call.
-Jeff
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
