[development] Adding to Profile forms - is hardcoding the only way?

[Carl Mc Dade]

   Hmm,

After reading my own post I saw that I left out a critical point. The original fields are being created with profile.module. I have brought up the subject of changing this but for now I wanted to know if Forms API can hook into the dynamic creation of form fields handled by the profile.module

Sorry about that. The previous post was badly formulated.

I also thought of using straight markup to create a custom textarea with the HTML  added but  profile.module does not have this ability. Is anyone working on this type of functionality?

- Carl

Adrian Rossouw <adrian at bryght.com> wrote: take a look at how the filter forms work.

There's help text in the node_example.module about it too.

Essentially you need to create a grouping array, move the original element into it , and then put your new field into that. 
This is all perfectly possible with form_alter


On 8/10/06, Carl Mc Dade <carl_mcdade at yahoo.com> wrote: I am adding a markup field to a Profile form but only want the field to show after a certain textarea. The idea is to use the links in the markup field to enter text in the textarea above it. I have set in the working code and have no problem with it but am questioning the fact that hardcoding this in seems to be the only way. 

Is there a way of doing this using the FormsAPI? a grouping syntax? Something like show this field only if a related field is present?

Is there a hook for FormsAPI that would help? 


TIA


 

 Carl Mc Dade
____________________________
 Web Developer for Hire
 http://www.heroforhire.net
 info at heroforhire.net

 
 



    

---------------------------------
Yahoo! Messenger with Voice.  Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less. 



 

 		
---------------------------------
Do you Yahoo!?
 Next-gen email? Have it all with the  all-new Yahoo! Mail Beta.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20060810/2ea2b09a/attachment.htm