In order to set the position in the node form I have added the hook_content_extra_fields that allows defining the position for any content type that has twitter feature on.
I added as well compatibility for Vertical Tabs (for D6 is needed the vertical tabs form, for future upgrades to D7 is already included)
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | twitter_3.x_cck_weight_vertical_tabs.patch | 1.12 KB | jcmarco |
| #6 | twitter_cck_weight_vertical_tabs_2.patch | 1 KB | jcmarco |
| #4 | twitter_cck_weight_vertical_tabs_2.patch | 1023 bytes | jcmarco |
| #2 | twitter_cck_weight_vertical_tabs.patch | 1.21 KB | jcmarco |
| twitter_cck_weight_vertical_tabs.patch | 1.21 KB | jcmarco |
Comments
Comment #1
dave reidNote the patch should use a group value of "additional_settings" and not "additional settings"
Comment #2
jcmarco commentedComment #3
dave reidIf someone is using Twitter without CCK, I think this will cause an error with an undefined function:
I don't think you need to grab the weight and put in the fieldset as CCK will do it for you.
Comment #4
jcmarco commentedDave, you are right!
Just adding the hook_content_extra_fields you can manage the twitter field in the cck form.
New patch without the #weight (solving possible issues when no using the cck module)
Comment #5
dave reidMinor nitpick that I should have caught the first time, the comment on the new hook needs to have a () at the end of the function name:
Wrong:
Implementation of hook_content_extra_fields.Right:
Implementation of hook_content_extra_fields().Comment #6
jcmarco commentedThank you for your review
Comment #7
dave reidLooks good.
Comment #8
jcmarco commentedRe-rolled for 3.x release.
Hopefully this time goes in.
Comment #9
michaek commentedIt'll be in the next push!
Comment #10
michaek commentedPatch applied, pushing soon!