Seems a great module but one thing is keeping me from using/testing it: "post to each service following the creation of a node". I think it makes more sense to post when node is published. Many sites are based on workflows. So either use the "node is published" or use trigger/action (or even better Rules). Merely a suggestion!
Comments
Comment #1
Rob_Feature commentedThis question of published vs. unpublished is a good one. Before addressing that, let me point out however that it doesn't automatically (ie. without user interaction) publish content to fb/twitter. If you install the module and take a look, the user must check a 'share' box, which then gives them the opportunity to easily share it once the node is saved. So, it's not as if it's going to share it and you can't do anything to stop it. It's up to the user to check the box, then share on social networks.
Now, that being said, I think the question is: Should the module prevent users from sharing unpublished content? Should it refuse to display share links if the content isn't published? That would be an easy addition if lots of people thought it should.
So, lets hear some feedback...if the node is unpublished should it show a "you aren't allowed to share this content until it's published" message instead of the share links?
Comment #2
vrteach commentedI think it makes sense to have the module set to "no share until it's published". To me, that would be part of the "simple" in simpleshare.
Comment #3
Rob_Feature commentedYeah, I think this all makes sense....most likely in the short term I'd just do it on the display side (we'd show a message saying "sorry, you can't share unpublished content" or something instead of the share buttons. I could do it on the form (hiding form item with .js), but I can see that frustrating people if by default their nodes are unpublished and they can't figure out why they can't check the share box.
Comment #4
Rob_Feature commentedbeta3 prevents unpublished nodes from being shared and, instead, gives a drupal message explaining why.