Description
QuickTabs Field Collection is a Drupal 7 module that allows a user to use the QuickTabs module to render field collection entity fields. The use case for us has been to allow our end users to create tabs on pages without having to understand the workings behind the scenes.
This issue has screenshots that show a general guide on how to configure and use this module.
Similar modules
There is a similar project called Field Collection Tabs, but it does not use QuickTabs to for its rendering whereas QTFC is more flexible.
Project link
http://drupal.org/sandbox/steven.wichers/1901520
Repo link
git clone --recursive --branch 7.x-0.x git.drupal.org:sandbox/steven.wichers/1901520.git quicktabs_field_collection
Comments
Comment #1
klausiWe are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and I'll take a look at your project right away :-)
Comment #2
jphelan commentedThere are a couple small issues you can address here:
http://ventral.org/pareview/httpgitdrupalorgsandboxstevenwichers1901520git
Otherwise I think the module looks great. I've tested it and seems to do what it says.
Comment #3
klausiMinor coding standard issues are not application blockers. Anything else?
Comment #4
jphelan commentedquicktabs_field_collection.module
Lines 284, 287 & 288 the variable $settings is never defined. I changed it to $formatter_settings and it fixed it.
I get the following error when using ui_tabs renderer. It still works, but you'll probably want to define history in your options.
Notice: Undefined index: history in QuickUiTabs->add_attached() (line 108 of /home/drupal7/public_html/sites/default/modules/quicktabs/plugins/QuickUiTabs.inc).I could not get the Accordion render to work. It give these errors. See related issue in QuickTabs issue queue. http://drupal.org/node/1664468
Setting the options to to the code below fixes the accordion, however you probably want to set the options dependent on what render is selected.
Comment #5
jphelan commentedAlso, I don't believe it's required but you do not have a hook_help function. You might consider adding one.
Comment #6
steven.wichers commented@jphelan:
The bulk of the warnings/errors are from the code I copied out of the QuickTabs module due to the lack of an API for that bit of functionality. I left it relatively untouched on purpose.
Good catch on the variable name. I had renamed the settings variable and missed the other spots (since those settings came later).
In an effort to beef out the settings of the module to include every renderer I ran into a complication with the Drupal 7 admin overlay and the states API. I'm researching a solution. As a temporary measure I put a helper function in place that just sets some defaults, and will add the more advanced renderer configuration later.
Comment #7
steven.wichers commentedI've done a lot of rework (and testing) on the settings implementation and have not encountered any errors. If you update the module to the latest version on the repository you should have new options available to you to configure the different renderers. Until you re-configure the field formatter and save those new settings there will be warning messages (since the way the settings are stored is different). I did not build in a settings converter since the number of people using this module is the people testing it here, and one guy who found the sandbox.
Comment #8
jphelan commentedEverything looks good. No more errors. Code looks good as far as I can tell. I'm not sure if a project requires more then one reviewer to be considered reviewed by the community, so I'll leave it as needs review for that reason.
I only have one minor suggestion but it's not that big of a deal.
The style option is irrelevant for ui_tabs and accordion renderers. You might consider hiding it when those are selected.
Comment #9
stevectorWorks as advertised. I opened a feature request for supporting view modes in the body of the tabs: #1907718: Add support for using View Modes as the body instead of a single field I also think the code could use more inline comments.
Neither of those should hold up full project promotion.
Comment #10
mitchell commentedThanks for your contribution, steven.wichers!
I updated your account to let you promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and get involved!
Thanks to the dedicated reviewers as well.
Comment #11
steven.wichers commentedThanks!
Comment #12.0
(not verified) commentedAdded link to issue with screenshots of module configuration