The edit method includes the edit.cfm file with a relative path. Since you haven't reimplented the method in the extended component, calls to edit will use the core method and therefore the core edit.cfm. You will need to re-implement the 'edit' method in your custom type component. Just copy the method exactly.

Blair

On 9/25/06, Helgi Rudd <[EMAIL PROTECTED]> wrote:

I am continuing the fumble and found I can add my own <widgets:plpstep
that points to my own step directory, for that step only (hence
retaining all the rest of the step code from the FarCry core,
inheritance still applies).

I don't have the new step showing up in the admin CMS interface yet
though, is it to do with the NAME of the plpStep and how that relates
to the plpstep widget thingy?  I've added a new plpStep as follows:

        <widgets:plpstep
stepDir="/farcry/farcry_rad/packages/types/_dmhtml/plpEdit"
name="MoreInfo" template="moreinfo.cfm">

This is a new plpStep that is supposed to show my new step... I've made
a copy of the body.cfm file that is in the core \types_dmhtml\_plpEdit
folder and called it moreinfo.cfm

Why doesn't this step show up in the edit process of any HTML page in
the FarCry CMS now?  I thought I had it here, I really did!



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to