Deleting tweet at Twitter doesn't remove it in the tweets View
So... other than removing from the database directly, how would you get rid of a tweet that has been imported?
Deleting tweet at Twitter doesn't remove it in the tweets View
So... other than removing from the database directly, how would you get rid of a tweet that has been imported?
Comments
Comment #1
pribeh commentedBump. Really want this. I believe it's a feature request though. Revert it if I'm wrong.
Comment #2
jrefano commentedbumping as well, there needs to be an easy way to do this
Comment #3
sheena_d commentedAlso, it seems like when you delete a Twitter account from the site, it should automatically delete that account's tweets from the site (or at least give you that option).
Comment #4
grp commentedsubscribing
Comment #5
j0k3z commentedAlso, when you turn off "import tweets" it still shows all previously imported tweets. Would be nice if it also hide those or deleted them or something
Comment #6
geerlingguy commented+1 - the module's awesome already, hope to see it continue to develop/flourish :-)
Comment #7
pztrick commentedbump =p
it isn't too hard to manually delete from sql database, so for my one-tweeter implementation it's not a big problem... but if you have multiple users and they delete their accounts, it makes sense that you would delete any previously imported tweets.
Comment #8
rootdownmedia commentedSubscribe
Comment #9
pbz1912 commentedI really want this too
Comment #10
Kane commentedSubscribe.
It'll look very strange if on someone else's twitter account won't be posts which exists on some site.
Comment #11
Dutchman commentedSubscribe
Comment #12
Anthony Pero commentedI'm changing the version on this, because if this gets done, it should get done on the dev version first and backported if necessary. I do not have the skills to implement this, but I do have an idea for a simple workflow of how this might be accomplished that I'd like to put up here for discussion.
To me, it would be great to have a link in the Twitter Config section that rebuilds the database information, the way we do for links, or anything else. Basically, this module is caching information from Twitter in the site's database. It would be nice if we had a link to click that would wipe the data in that table, and rebuild the information with current info from Twitter.
Downside: Obviously this is a heavy handed way to get rid of one or two deleted tweets in your database. But it works, and for some sites, it's PROBABLY a good idea to be able to empty those table of old tweets periodically, anyway. Also, if you ARE archiving two years worth of tweets for some reason... Twitter only keeps them for 7 days, so when you performed this function, you'd lose all tweets older than 7 days.
Still, I think site admins should have an easy way to purge their database of old tweets without having to edit the database directly, and this would also fix the issue in this thread.
Comment #13
jjma commentedWill the delete option add to the overall load of the front end as well as the administration section?
Jon
Comment #14
javier1968 commentedBump this
Comment #15
webflo commentedi have started a sandbox with vbo integration. http://drupal.org/sandbox/webflo/1698568
Comment #16
xurizaemonWould prefer if this could come forward to 7.x-3.x and then get backported, but as you're already working on it for 6.x I'll leave version as it is. Thanks for engaging @webflo!
Comment #17
Homotechsual commentedIf this is implemented it should be configurable. I for one don't wish all the politician's "slip up" tweets I've archived to be removed when the user deletes them from twitter or when one of my contributors looses their account...
Comment #18
dddave commentedComment #19
janis_lv commentedyep, this I'd love
Comment #20
xurizaemonMoving to 7.x, new features can be backported to 6.x. No progress updates in 12mo but webflo please update us with your progress if you got somewhere?
@Anthony Pero, I imagine we'd do this by deleting individual tweets - anyone who wants to start from scratch can wipe the DB table, so I think the VBO / individual item approach is preferable.
Comment #21
Anthony Pero commentedI totally agree, I was just proposing a simple solution.
Comment #22
loren.swendsen commented+1 subscribing
Comment #23
damienmckennaComment #24
hkirsman commentedA real life scenario. Our clients twitter account was hijacked. While the account is now ok again there's a tweet on the site that is not supposed to be there.
Maby there's should be Delete link next to "Reply", "Retweet" and "Favorite" in the tweets list? If you have the permission ofcourse.
+1
Comment #25
hkirsman commentedOr if you delete tweet on your twitter account, it should be detected by twitter module.
Comment #26
xurizaemon@hkirsman, IMO this really has to be a per-site decision, because:
Patches I think would be welcome to provide both (1) delete functionality for specific tweets via an additional callback / entity support (2) some means to bulk-scan existing tweets and detect / remove those which have been deleted. (#17 would probably find the ability to identify "slip up tweets" en masse and NOT delete them a feature!)
Comment #27
aharown07 commentedAlong the lines of #25 but to reduce resource demand, what if it just checks for deleted tweet over the last user-configurable # of hours... with a max of, say 24?
So the option would be a check box to "automatically remove tweets deleted in Twitter" with a parameter box for the max delete age or something along those lines.