Does a drupal 6 version of this module existe ? May be this module is included in the CCK module but I didn't find it.
Can you help me ?
Thx
Ben

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Tamar Badichi-Levy’s picture

I believe we should wait until the cck module for drupal 6 is ready and stable before working on a drupal 6 version of this module. What do you think?

bneel’s picture

U probably right

designerbrent’s picture

Category: feature » task
Status: Active » Needs work
FileSize
32.79 KB

Here is an initial port of the module. The only thing that is not working is the option to keep the child after the parent.

designerbrent’s picture

FileSize
32.85 KB

Fixing some spelling errors and some missing form_ids.

designerbrent’s picture

FileSize
32.77 KB

More code cleanups, removal of trailing spaces, and debug code removal.

bneel’s picture

I'll try as soon as I can. Thanks a lot for your investment.
Benjamin

Babalu’s picture

subscribe

crosalot’s picture

Priority: Normal » Minor
Status: Needs work » Patch (to be ported)
FileSize
19.79 KB

I,m rookie. I try out port this module form drupal5 to drupal6 for review.

Babalu’s picture

i used the #8 patch, but
is not compatible with the drupal 6.4 core :(

designerbrent’s picture

Status: Patch (to be ported) » Needs review

the code is already ported.

scottrigby’s picture

Hi - Has anyone tried #5? I'll be happy to test something when that wil be helpful, but dont' want to just shoot in the dark. Thanks :)

scottrigby’s picture

#5 is alive - works for me in Drupal 6.5, with cck-6.x-2.0-rc10... the basics (haven't tried every scenario) but this is exactly what I needed - thanks!

daneyuleb’s picture

Version: 5.x-1.4-beta » 5.x-1.x-dev
Category: task » support
Priority: Minor » Normal

The 6.x version works for me when I use cck fields in my profile (via Content Profile) on the Profile page...but....the same dependencies don't work on the Registration form (using the Registration form functionality of Content Profile).

So...when the user registers, the dependent field is seen no matter what, but once he's registered and goes to his profile, and edits it, it works as expected.

Somehow, on the registration form, it must be querying the db based on a slightly different field name, maybe? And missing the dependency?

If anyone has any solution for this I'd be truly grateful....

-Daniel

scottrigby’s picture

Status: Needs review » Needs work

Daniel, I added an issue in the Content Profile module as well #330048: hiding fields on registration using CPReg & Dependent Fields modules?
This issue is definitely something we need to look at more closely, since CP is the way profiles as nodes is moving in D6. I'm marking as code needs work for this reason.
Thanks in advance for looking more closely at this :)
Scott

daneyuleb’s picture

More than I can figure out, I'm afraid. For me, it's working fine on the Content Profile edit page, but not the registration, but it's beyond me as to why. Hopefully, someone with more skills will take a look at it and get it to work.

-Daniel

lelizondo’s picture

Component: Documentation » Code

dependent fields don't work with bio, at least the last time I tried.. and if it's not working for bio I don't think we should be waiting to get this fixed to have at least a dev version of this module on the project page and not only a patch..

daneyuleb’s picture

Bio isn't available for Drupal 6, so I'm not sure how that applies in a thread about porting this module to 6.x...

lelizondo’s picture

I thought I was clear enough. I'll try to explain myself. If you're using drupal 5.x, dependent fields and bio, dependent fields won't work on the bio node when the user is creating or editing an account. The same problem reported here but with bio and drupal 5.x

So my point is that if dependent fields isn't working for bio on drupal 5.x it shouldn't be an issue to delay the 6.x release version of this module.

likewhoa’s picture

patch works and tested it on drupal-6.8

chrisjejbrown’s picture

Can someone tell me what to do with these patch files? I have replaced the dependent.info file with the contents of the patch and also uploaded the patch as a seperate file. The module still shows as being incompatible with Drupal 6.8 core. Any help appreciated as I really need this to work.

lelizondo’s picture

you have to apply the patch to the 5.x files.

http://drupal.org/patch/apply

watbe’s picture

subscribing...

Can someone please upload the patched version? I'm using Windows and I find it rather difficult to use .patches.

This would be greatly appreciated,

Wayne

likewhoa’s picture

just install cygwin it shouldn't take more than 10mins to install, open the shell and run patch -p1 <dependent-d6_upgrade2.patch in the module directory.

lpt6’s picture

Hi i have patached the d5 version and seems cannot get the setting saved after chosen the dependent field in the setup

------------
My Blog: www.his25.com
www.shuodui.com.cn

AaronBauman’s picture

Status: Needs work » Needs review
FileSize
40.32 KB

combined patch -- including #5 above.
Addresses #24, values not being saved.

Also, i d6-ified the javascript file. much cleaner now.

not thoroughly tested, but works for me so far on d6.10

haven't tested against #14 -- content_profile_register issue.
imo that should be a separate issue.

lelizondo’s picture

I think the drupal 6.x version of this module can and should be released without having to solve #14. As I said, when using Bio/nodeprofile and Dependent fields with Drupal 5.x, dependent fields won't work on the registration process, so my point is that if that's something this module didn't do on drupal 5.x (I understand that Content profile wasn't available for Drupal 5.x, but they are similar modules), it could be released (at least a dev version) without fully working with Content Profiles in Drupal 6.x. and then leave #14 as a separate issue as aaronbauman said. After reading #330048: hiding fields on registration using CPReg & Dependent Fields modules? it seems that the issue evolved into something else.

lpt6’s picture

thx, let me try it first
------------
My Blog: www.his25.com
www.shuodui.com.cn

lelizondo’s picture

Status: Needs review » Reviewed & tested by the community

I just found two minor bugs but honestly I don't know if it's worth reporting them. The module does work, with some bugs but it's good enough for a dev release.

I think the bug reported in #13 and #14 about this module not working with Content Profile stopped this module from going into a 6.x-dev release when it was only a minor bug.

Although I'm reporting 2 1 minor bugs, I don't think they should stop the module from moving forward. I hope this bugs could be fixed in a 6.x-dev version and not in the #25 patch.

Bug 1. In 5.x it is possible to select multiple dependent scenarios (field instances) for one field. With this version it's not possible.

Bug 2. The dependent field only show up when the field instance it's a select list. Example, I have two fields, field_x and field_y, field_y it's dependent from field_x, field_y will hide and show if field_x it's of the type 'Select list', but it won't work if field_x it's of the type 'radios buttons'.

I'm using CCK 6.x-2.2 and Drupal 6.11

Thanks

Edited.

mitchell’s picture

Conditional Fields works well on 6.x, btw.

scottrigby’s picture

@lelizondob: Re #29, How can you select multiple dependent scenarios? I just patched 5.x-1.x-dev with #25 and I don't see how to select multiple conditions for a dependent field (box is not multi-select)?

Re #27, i agree that #14 should not hold up a dev release.

lelizondo’s picture

@scottrigby: I posted this a long time ago. let me try to remember the site I was using this.

rvallejo’s picture

I used the combined patch from #25 on core 6.13 , but found a conflict with the CCK Fieldgroup Tabs module (or maybe just the jQuery Tabs?) - node add/edit page is blank (javascript for the tabs not executing?). Actually, seems like its messing up other javascript functions too: date popup calendar, collapse and expand fieldgroups, wysiwyg editors, pathauto; seems like all scripts loaded after dependent.js just aren't doing anything. I'm getting this error in Firefox:

Error: $(this).attr("name") is undefined
Source File: sites/all/modules/dependent/dependent.js?i
Line: 55

Are others getting anything similar, or maybe I just copied something wrong from the patch?

Also, for future features, would be great to see some Unlimited Values functionality, ie, contact information including name, email, phone, etc. where you might want to include multiple contacts but keep all information grouped by contact rather than field type.

AaronBauman’s picture

Status: Reviewed & tested by the community » Closed (fixed)

6.x dev snapshot released!
http://drupal.org/cvs?commit=274792

Thanks, designerbrent and crosalot and all the reviewers and testers

re: #29, #33
rvallejo, lelizondob: Please try the dev snapshot release. I believe this is resolved.

re: #31,
scottribgy: multiple dependencies are not currently supported. Please check the issue queue to see if this feature request is in yet, or create a new issue.

any issues i missed: please check the issue queue or open a new issue.