This module provides new functionality to split a field into three parts. The code for this module is based on the double_field module developed by Chi.
Jen Ware and Ashley Hall, both PhD students in digital rhetoric and new media, created this module for the 2012 Computers and Writing Conference so that presenters can enter data for their conference presentation that will appear in the printed program.
We needed an easy way for our users to create a node with an abstract field and a "presenter info" field. The triple field module allows us to collect the speaker name, university name, and presentation title for all the members of a particular panel accepted to present at the conference. We set the number of values for the field to unlimited so that users can add as many speakers, universities, and presentation titles as needed within the presenter info field. This also allows us to build specific views more easily for displaying the conference schedule on our drupal site.
This module is useful for anyone who is building a conference web site but may also be useful for anyone who needs to collect data from users in a single field with sub-divisions. This module is similar to the field set module but for use cases when separate fields are not desired, this module may provide a better solution.
Project page is here: http://drupal.org/sandbox/knowledges33ker/1392132
Repository page is here: http://drupalcode.org/sandbox/knowledges33ker/1392132.git/commit/7050be8...
This module is for Drupal 7.x
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | pareview.txt | 5.39 KB | anwar_max |
Comments
Comment #1
jasonrichardsmith@gmail.com commentedHi,
This seems awesome and thanks for contributing to Drupal. I reviewed the code and noticed that it duplicates a lot of the original module. In general we would recommend collaborating with that project instead of creating a new one. May I suggest expanding the double field module to have a N-field module. Also, the field_collection module in D7 adds very similar functionality. Maybe you could look at that project and file any issues for features you'd like to see added?
Duplication is an ever growing issue with Drupal, please read under the section Module Duplication.
I look look forward to your feedback.
Comment #2
misc commented@knowledges33ker has been contacted to ask if the application is abandoned.
http://drupal.org/node/894256
Comment #3
knowledges33ker commentedHello all, no this project hasn't been abandoned, I think I forgot to change the needs work status. We've been testing it on several sites and it's been working well. I like the suggestion provided by jasonrichardsmith and will look into collaborating with the double field module developer! My co-collaborator and I were excited to have expanded the module and wanted to share it with the community!
Comment #4
knowledges33ker commentedComment #5
chi commentedHey, knowledges33ker.
I agree with jasonrichardsmith. It would be better to have one N-Field module instead of Triple field or Quadruple Field. Look this issue: #1273510: More than double field, x# field? for futher information.
Yes, there is Field collection module but it based on Entity API and operate with Fields not with FAPI elements as this one.
I suggest you give users possibility to choose number of subfields.
Good Luck!
Comment #6
sbrattla commentedI absolutely agree with Chi in #5. I've been looking for this kind of module in earlier projects...that is; a module where i could define two, three of four fields depending on the use case. It would be a great feature, and you would most likely see much more use of your module as people will find it suitable for far more scenarios.
Comment #7
jygastaud commentedAs mentioned in the issue link posts by Chi, I thought field group multiple can do that: http://drupal.org/project/field_group_multiple
Comment #8
geertvd commentedI agree with Chi, could you look into adding an x#field module, the field_group_multiple seems nice but it looks like it is used for more advanced edit pages.
Some extra functionality could also be linking the 3 fields to each other.
For example if the maxlength is reached in the first textfield, automatically give focus to the second one.
Off course this should be optional.
Also you've got some code styling issues
http://ventral.org/pareview/httpgitdrupalorgsandboxknowledges33ker139213...
Comment #9
novalnet commentedHi,
Manual Review :
1. It seems README.txt is missing, see the guidelines for in-project documentation.
2. triple_field.info => Please remove version, project and datestamp from .info file.It will be added by drupal.org
3. You should PARREVIEW your script. You have many errors.
See http://ventral.org/pareview/httpgitdrupalorgsandboxknowledges33ker139213...
4. triple_field.install :
25 | ERROR | Spaces must be used to indent lines; tabs are not allowed
25 | ERROR | Line indented incorrectly; expected at least 2 spaces, found 1
25 | ERROR | Array indentation error, expected 4 spaces but found 1
26 | ERROR | Array indentation error, expected 3 spaces but found 6
27 | ERROR | Array indentation error, expected 3 spaces but found 6
28 | ERROR | Array indentation error, expected 3 spaces but found 6
29 | ERROR | Array closing indentation error, expected 1 spaces but found 4
34 | ERROR | Spaces must be used to indent lines; tabs are not allowed
34 | ERROR | Line indented incorrectly; expected at least 2 spaces, found 1
34 | ERROR | Array indentation error, expected 4 spaces but found 1
39 | WARNING | A comma should follow the last multiline array item. Found:
| | $indexes
41 | ERROR | Files must end in a single new line character
Comment #10
aaronelborg commentedHi knowledges33ker.
Looks like the stuff pointed out by Novalnet still hasn't been fixed but I'm sure you're aware of that.
It looks like you're working on the master branch, which is not the preferred way within Drupal. Also, when I do a 'git branch -a' I'd expect to see something similar to this:
* 7.x-1.x
remotes/origin/7.x-1.x
remotes/origin/HEAD -> origin/master
remotes/origin/master
Instead I see:
* master
remotes/origin/HEAD -> origin/master
remotes/origin/master
So it doesn't look like there's a proper, working branch to switch to? You should probably fix that.
Also, there's a 'rogue' 'triple_field' folder within the main 'triple_field' directory that doesn't need to be there.
You don't need to include a 'License.txt' file as the Drupal.org packaging script will add one automatically.
Looks like you've included a 'README' but it's been named 'readme' in lowercase as opposed to upper case which is the convention.
Currently your info file is full of kruft. This would suffice:
You know how you might be able to just create the uber, all-encompassing 'Multi-field Module'? OK....maybe that's a bad name. Maybe the forementioned 'N-field module'? (Oooooh......The "Nth-Field Module"!!!!!)
Give the user a number spinner to choose from and then you could do something like this:
.....so that then you could change the x number of text-boxes to whatever and then nobody would ever have to worry about the 'Quad-field Module' or the even more horrifying 'Penta-Field Module'. I mean, really, imagine this situation by the time Drupal 12 rolls around. Things could get ugly!
THINK OF THE CHILDREN!!!!
;-)
Finally, it's probably beside the point but in your .module file the code sniffer's finding all sorts of problems:
Well, I hope I gave you some good insight.
Is this module still in development? Hope I didn't just waste my time.
Keep on keepin' on, amigo!
-Aaron
Comment #11
patrickd commented@Aaron
Please do not paste the full results into the issue, as giant ‘wall-of-wrong’ posts are extremely demotivating to applicants, rather provide a link to the results (or post as an attachment) in the application thread. thanks
Comment #12
aaronelborg commentedMy apologies, patrickd.
I figured that since I elaborated on a few other things the 'wall of wrong' copy/paste wouldn't be so bad.
Won't do it again.
-still living and learning up in here,
Aaron
Comment #13
knowledges33ker commentedHi everyone,
Thanks for all the helpful feedback. This is my first time going through the process so the learning curve is still pretty steep.
I'm working with a colleague here at UNC who is helping me interpret the comments above and we are now collaborating to develop this into the "n field" module so that (hopefully) we can avoid the problem Aaron mention in #10 above.
Thanks again for all your comments. More soon.
-Ashley
Comment #14
anwar_maxManual Review:
Looks good and you are following proper coding standards. Please try to resolve the automated review issues.
Automated Review:
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
Comment #15
knowledges33ker commentedThanks again all for the really helpful responses. I'm working now to fix the errors in the current version of this to run through the code sniffer and then upload into a version specific branch and will then be working with a colleague to update to an nth field module.
Comment #16
mitchell commented@knowledges33ker: It looks as though Chi and AaronELBorg had some very insightful comments, and that you've taken them into account to extend triple field into n field.
Also, from my investigation, it appears to me that Field Group multiple has gotten the furthest in this arena, so it would be very helpful if you could test that module and report how it suits your needs, too. However, Double Fields also appears to be picking up users, so I hope Chi will help clarify #1671814: What's the relation to Field Group multiple?.
Please let us know if we can help guide you any better, so I'll mark this as waiting for feedback from you until we know which path you intend to take.
Thanks and good luck!!
Comment #17
chi commentedSeems to be fixed. composed field is module from FranciscoLuz that allows you to split a single field into as many sub-fields as you like.
Also there is sandbox project based on Form builder from Swentel.
Comment #18
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.