Active
Project:
Twitter
Version:
7.x-5.x-dev
Component:
Twitter API
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Jul 2011 at 12:32 UTC
Updated:
19 May 2015 at 18:15 UTC
Jump to comment: Most recent
Comments
Comment #1
michaek commentedYou know, I'm really not sure! I don't have my head wrapped around the entire codebase yet, but I will check into that for you.
Comment #2
michaek commentedThis is only a partial answer: the module currently checks "!empty($node->status)" which means it won't post to Twitter if the node is not published. However, it's not checking to see if (for example) an Anonymous user can view the node, so I don't think it will correctly detect a published but "private" node.
Maybe this use case could be addressed by selecting a user role that should be able to see a node in order to control whether to post to Twitter, defaulting to Anonymous. This seems like an edge case, so I'm not positive whether it'll be addressed in the way I'm describing, but I do think there are likely to be other issues around this.
Comment #3
chriszz commentedThanks a lot michaek, I really appreciate it! I also like the way you want to implement it.
Edge Case? Just think in groups, where you easily mix public with private content...
Comment #4
chriszz commentedI think, that an option to either use opt-in or opt-out would be very useful!
Comment #5
13rac1 commentedThe exact functionality will need to be fleshed out, but URLs should (optionally?) only be tweeted for content accessible to Anonymous users.
Comment #6
xurizaemonWould need to be configurable (can envisage a PPV site not wanting to require anonymous access to promote new content).
Comment #7
damienmckenna