Please consider adding this as a enhancement to CCK rather than seperate module.

Comments

guypaddock’s picture

guypaddock commented
Status: Active » Postponed (maintainer needs more info)

ajayg, the CCK developers are usually swarmed with bug reports and enhancement requests. In addition, there are a lot of modules out there that extend CCK with widgets and custom field types, rather than being a part of CCK.

Is there a particular criterion for why the functionality provided by this module should be part of CCK instead of stand-alone?

ajayg’s picture

ajayg commented

I think this module is almost like a special input/output filiter for CCK. Rather than adding something on top of CCK, it enables existing CCK to behave differently and with more capability (for site admin). So I thought this belongs to core infrastructure than a separate add-on.

My 2 cents.

sportel’s picture

sportel commented

Hi,

Maybe this post helps:
http://drupal.org/node/212665

Mike.

john.karahalis’s picture

john.karahalis commented
Title: This should be part of CCK rather than a seperate module » This should be part of CCK rather than a seperate module

From GuyPaddock:

I don't think we realized there was such a demand for this functionality. I wouldn't be opposed to it being integrated, but I don't think we have the time to dedicate to the task right now.

john.karahalis’s picture

john.karahalis commented
Title: This should be part of CCK rather than a seperate module » This should be part of CCK rather than a seperate module
Status: Postponed (maintainer needs more info) » Postponed
drupalnesia’s picture

drupalnesia commented

I agree, look at: http://drupal.org/node/912698

CCK should have built in user define field-validation, so we can enter our own PHP code to make validation.