function twitter_content_extra_fields adds the twitter fieldset to the admin > content > content types > type name > manage fields form ( admin/content/node-type/type name/fields , "content_field_overview_form").
When content module is enabled, this patch gives the site admin the ability to reposition the twitter fieldset on the node add/edit form.
Tested with 6.x-3.x and 6.x-2.x
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | twitter-n604530-12.patch | 756 bytes | damienmckenna |
| #7 | twitter-n604530-7.patch | 651 bytes | damienmckenna |
Comments
Comment #1
sirkitree commentedThis does apply to the 3.x branch, however it does not really pertain to it because there is no field on a content type in 3.x to send a post. It can be done through actions, but there is no field in which your function can apply itself to.
Grepping through the module, 3.x branch, there isn't anywhere that this variable is ever set.
Moving it to 2.x as you say it applies there, but I have not tested 2.x
Comment #2
aaronbaumanThe node-specific functionality moved to twitter_post.module and the variable name changed from "twitter_types" to "twitter_post_types"
The OP is still applicable to 2.x.
Please find 3.x patch attached.
Comment #3
dpearcefl commentedBTW: The variable name is still wrong in 6.x-3.0-beta9
Comment #4
aaronbaumanover 2 years later... here's an updated patch.
Comment #5
davidneedhamCould we get a re-rolled patch with all of these changes and updated for the latest 6.x-5.x-dev?
Comment #6
dddave commentedComment #7
damienmckennaRerolled.
Comment #8
damienmckennaCommitted. Thank you.
Comment #10
damienmckennaThe 7.x-5.x branch could use this.
Comment #11
damienmckennaComment #12
damienmckennaThis works for the 7.x-5.x branch.
Comment #14
damienmckennaCommitted. This isn't needed for the 7.x-6.x branch.
Comment #17
damienmckennaThis was already committed.