I am a newbie and am fumbling my way though FarCry. Apologies for the 'duh' factor of any of my questions in advance.
Requirement: A Second editable HTML area for the dmHTML type... literally two 'body' areas for each HTML type page in the CMS. I have read up on examples re: extending core funcitonality and have searched and found some posts related to extending core functionality in the forum and found some things useful but I am still stuck. I learnt how to add a new attribute to the dmHTML type... I made my own dmHTML.cfc file and saved it in my project directory: \$my_project$\packages\types... this file only has a few lines... it references the core HTML type.... "FarCry, please inherit the properties and methods of the core dmHTML object and allow me to extend on that"... inheritance, great, so far so good. In that file I added a new property called 'MoreInfo' with type="longchar" (since I looked up the type details for the core object dmHTML and the data type was longchar, so I figured I'd use the same!) At that point I have a custom type and the admin area of FarCry allowed me to deploy the new type... all goes well, FarCry seems to know about my new type attribute and I have succesfully extended the core datatype 'dmHTML'. Horray! However, extending the admin interface to allow me to see an extra step in the edit flow is beyond me... I thought I could copy accross the folder _dmHTML into my project folder \$my_project$\packages\types and work with that... but I'm getting stuck with how that should hold together... here is why: 1. I copy accross the folder /_dmhtml and inside there are quite a few files... the sub folder plpEdit folder appears to contain template pages that directly relate to the edit pages in the edit sequence. 2. What first got me stumped is the <widgets:plp tag in the _dmHTML\edit.cfm page... is that a custom tag? 3. I usually have a good go at fumbling my way through so I thought I would add an extra line in the sequence of 5 already existing <widgets:plpstep ..... lines. So I added my own <widgets:plpstep.... line, replicating the one used for the Body but changing variable names and template names... I could see that I needed to create my own 'step' for the new 'plpStep' I had just added... and that file seemed to be one of those living in the /_dmhtml/plpEdit folder. 4. I duplicated the body.cfm file that is in \_dmhtml\plpEdit and gave it the name of the template I defined in my new plpStep. Nothing happens in the edit screen... there is no difference in the edit flow... I cannot use my new field. One thing I noticed that seems significant is the 'hard coded' reference in the edit.cfm file for the 'stepDir' (reads to me: the folder where the steps for the edit process will be found).... this is fixed at /farcry/farcry_core/packages/types/_dmhtml/plpEdit so I'm thinking this is half my problem. Then my thinking goes... well, if I am going to change that stepDir folder to my project directory it means I have to copy accross all step template files and then I'm not really doing the 'inheritance' thing properly (I recall reading several posts that say I should only need to copy accross files from the core system when I am making changes to those parts of the inherited flow). So I suppose my overall hope is that someone can help me to understand how to enhance farcry core funcionality with a multi step widget thingy that is already part of the core process (all examples I've found extend some simple part of the system like adding a text box to a form... no mention of the <widgets:plpstep peice of the puzzle). I feel a bit silly because i was told it would be easy to add another editble HTML 'body' to the existing dmHTML object... have I really gone down the wrong path!? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
