Posted by radman16 on November 24, 2008 at 3:02am
| Project: | CCK Validation |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
Are there plans to port this to D6?
Comments
#1
Yes, I second the "interest" in porting this to Drupal 6. This is a great feature to have available in CCK fields.
Scott
#2
Greetings,
After posting #1 above, I just came across the Validation API module that may offer the same functionality. You can find it here: http://drupal.org/project/validation_api
Scott
#3
I've tested CCK Validation on my test site and it is working in Drupal 6 without modification. Only modifying the .info file to make Drupal 6 recognize it.
#4
radman16,
Great - thank you!
Scott
#5
Hmmm, I tried modifying the.info file, but Drupal 6.8 is still not recognizing this module :-/.
#6
I'm using 6.8 with no problem. Here is my .info file:
; $Id: cck_validation.info,v 1.2 2008/01/30 01:44:53 derhasi Exp $
name = CCK Validation
description = "Allows the user to add custom validation to content-types."
dependencies[] = content
package = CCK
core = 6.x
#7
Thanks radman16 for providing the info.
But for Drupal6 I'd propose to use Rules Module, it has a lot more features, and is more extensible.
So I won't do a official port to D6, but using the info seems to work.
#8
Ups... I just posted a support request... please ignore it..
Thank you
#9
@derhasi: please add me into your maintainer list, I like to port this module to D6.
#7: implementation with and without Rules is different, mean directly add validation in field simpler than using Rules modules.
#7: Also, not all websites come with Rules module.
#7: To make Plugin Manager module works, we need a D6 version.
#10
#11
@drupal-id, you could post a patch file in this issue, so it can be reviewed. So we could talk about a clean port to Drupal 6. Maybe it would help, that I clean up the drupal 5 code a little bit before (especially codings standards). Please give me feedback on that.
Generally there is really no need to develop this module anymore, as - as I allready said- rules module covers all functionality. What I would support was an upgrade-path to port this module to a ruleset. I see no reason for not using rules. If there was one, you also should disable cck.
#12
+1
#13
#5 The same. Does not work
#14
@all, why would you prefer a D6 Version over using Rules instead?
If you give me some advantages of your sight, I could put these aspects in a D6 version, so it would not be duplicate to functionality Rules handles.
#15
Subscribe
#16
@derhasi:
Rules is complicated, while CCK need a straight validation and how to handle 10 content-types with total 200 cck-fields there (can the UI of Rules separated per content-types?), if you wish to give me access to CVS/Git then:
I will release 6.x-1.0-alpha1 version first, based on #3 by radman16 credit. This is important for Plugin Manager (PM) since PM will fail to find 6.x while you only create a 5.x version
Then revised the code based on D6 if necessary
Add Ajax warning or Inline validation message?
Frankly I didn't need this because I can altered/created my own module but not all Drupal users understand how to coding in Drupal. Believe me, once we deliver this to D6 then we will open users opinions, suggestions, complains and ideas which will make this module better day by day. Cheers.
#17
@drupal-id, simply post the patch file, so I can review it
#18
This is CCK Validation 6.x-1.0-alpha1
- only revised .info file to meet Drupal 6.x, thanks to radman16
IMHO, rather than make a new field-type (called as Validation), I think better we provide a validation for existing field-type. Currently I directly alter the nodeapi(), hope I have spare time this month, of course this will implementend to 6.x-2.x version, let's users guide us the right direction.
#19
+1 Sub