Hello,
I have attempted to install this version, and when on the modules page (5.x) the check box for dependantDropdown is not available. "Content (missing)"
I have looked at other CCK modules that are also requiring the content module and they are all working. I have checked the dependencies on your module, and I have both text.module and number.module installed.
I am not sure if this is a bug or not. I am interested in the functionality of this module, and I hope that development continues.
Thanks,
Brian
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | dependantDropdown.info_.patch | 850 bytes | hyperlogos |
| #8 | dependantDropdown.info_.txt | 619 bytes | schnizZzla |
| bug_1.JPG | 56.69 KB | chickenmcnoggin |
Comments
Comment #1
hedb commentedFixed.
replaced Content with content
Comment #2
hedb commentedComment #3
Budrick commentedCan you please make a release 5.x with this fix?
Current 5.x rather confusing - the module cant be activated.
Comment #4
plutado commentedBudrick,
Open up dependantDropdown.info in a text editor and change the uppercase "C" to a lowercase "c" and you're good to go.
Comment #5
Budrick commentedI did.
I just care about other people who might be confused that they cant even enable the module and give up without looking for this issue report.
Comment #6
hedb commentedSorry, all the handling of the CVS + releases is something that went over my head
i'm afraid that i wont get to order my releases
Comment #7
panchoIf this module depends as well on "text" and "number" (as stated in the description), I suggest adding
dependencies = content text numberto your dependantDropdown.infoComment #8
schnizZzla commentedThan you very much for this fix!!!
I'm attaching my dependantDropdown.info (renamed to .txt) for all the lazy people out there.
Comment #9
kuahyeow commentedStill not fixed in the release
Comment #10
hyperlogos commentedJust in case someone is waiting on an actual patch file, a patch is enclosed. Why is this still not fixed in 5.x? It can't even be enabled without this fix! Just because there's an easy workaround (it's easy to you and me, but maybe not to some other user) doesn't make it not a critical bug.
The patch is enclosed. Please apply it so that it makes it into the next release!
Comment #11
paulcoghlan commentedFYI I just posted this...
http://drupal.org/node/124303