Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Unfortunately there's not that capability, but might be a cool thing for me to add. =) It would be hard to get it precise though because it's strictly dependent on when your drupal cron runs. For example if you wanted your tweets posted at 8:00pm, and your cron only ran at 6:00pm and 11:00pm. then there's no real way I can make it happen precisely at 8 ....
well ... actually I -might- be able to post something with a specific date and time and even though it would show up at 11pm, the post itself would say 8. would that suffice? (clearly if you actually adjusted your cron to run every hour or something it would work out just fine, but i'm thinking of cases where it's not set up that way)
Not "trivially" =) What triggers it is "the first time it ran + 24 hour increments" In other words, a timestamp was taken the first time it ran and from then on, it won't update until it's been 24 (actually more like 23.5 hours) since the last update, at which point it re-updates the timestamp. There is a table in your database that houses "properties" stored for the plugin (amongst other things) that will contact said timestamp that you could actually manually update. I don't know what it is off the top of my head right now but hopefully it's not too hard to locate. (should be obvious from the code too if you want to look over the plugin code)
Currently the plugin, for any given account, checks twitter, records the timestamp when it checked, and then won't contact twitter again for another 24 hours from that same account. (slightly less than 24 hours due to some weirdness I was seeing) Now it is certainly possible that something has broken along the way, but that's the way things worked when I first released it and is how things are working on my own install. I run cron every 5 minutes and it only bothers twitter after 24 hours.
i really, really, really like this module and my readers were oohing and aaahing about it, so am really interested in helping in any way i can to help debug. alas, am not a module coder.
that said ... when i installed it, i had poormans cron running. since i have now regular cron running, i took it out and that's when it stopped working.
is there anything i should look in my logs for that would help you crack this puzzle?
Hrm. I wonder how other modules run via poormans cron. Maybe they check to see who they are running as -- like perhaps if it's run as admin, process all users, if it's run as a specific user, it only runs for that one user. Ok, let me back up and make dailytwitter work properly to begin with -- it's quite broken right now as i'm sure you are aware.
Note to self -- simply pass "date" option when creating entry. However, I do not want to implement this until I've implemented functionality where dailytwitter checks for "days it's missed" so to speak. Otherwise I fear that this may cause some missed posts if folk don't run cron often enough.
Comments
Comment #1
jadestorm commentedUnfortunately there's not that capability, but might be a cool thing for me to add. =) It would be hard to get it precise though because it's strictly dependent on when your drupal cron runs. For example if you wanted your tweets posted at 8:00pm, and your cron only ran at 6:00pm and 11:00pm. then there's no real way I can make it happen precisely at 8 ....
well ... actually I -might- be able to post something with a specific date and time and even though it would show up at 11pm, the post itself would say 8. would that suffice? (clearly if you actually adjusted your cron to run every hour or something it would work out just fine, but i'm thinking of cases where it's not set up that way)
Comment #2
ThePrince commentedMy cron runs every 15 mins so that's not a problem.
Right now, what triggers the time of the posting? Can I just change that?
Comment #3
jadestorm commentedNot "trivially" =) What triggers it is "the first time it ran + 24 hour increments" In other words, a timestamp was taken the first time it ran and from then on, it won't update until it's been 24 (actually more like 23.5 hours) since the last update, at which point it re-updates the timestamp. There is a table in your database that houses "properties" stored for the plugin (amongst other things) that will contact said timestamp that you could actually manually update. I don't know what it is off the top of my head right now but hopefully it's not too hard to locate. (should be obvious from the code too if you want to look over the plugin code)
Comment #4
liza commentedplease review this comment:
http://drupal.org/node/484782#comment-1891084
i am pretty sure this "feature request' is actually necessary fix the bug in question
Comment #5
jadestorm commentedAlso review my response.
Comment #6
jadestorm commentedCurrently the plugin, for any given account, checks twitter, records the timestamp when it checked, and then won't contact twitter again for another 24 hours from that same account. (slightly less than 24 hours due to some weirdness I was seeing) Now it is certainly possible that something has broken along the way, but that's the way things worked when I first released it and is how things are working on my own install. I run cron every 5 minutes and it only bothers twitter after 24 hours.
Comment #7
jadestorm commentedComment #8
jadestorm commentedComment #9
liza commentedi really, really, really like this module and my readers were oohing and aaahing about it, so am really interested in helping in any way i can to help debug. alas, am not a module coder.
that said ... when i installed it, i had poormans cron running. since i have now regular cron running, i took it out and that's when it stopped working.
is there anything i should look in my logs for that would help you crack this puzzle?
Comment #10
jadestorm commentedHrm. I wonder how other modules run via poormans cron. Maybe they check to see who they are running as -- like perhaps if it's run as admin, process all users, if it's run as a specific user, it only runs for that one user. Ok, let me back up and make dailytwitter work properly to begin with -- it's quite broken right now as i'm sure you are aware.
Comment #11
jadestorm commentedDo any of y'all know how to revoke a release? I can't find it in the drupal docs but I've definitely seen it done before!
Comment #12
jadestorm commentedNote to self -- simply pass "date" option when creating entry. However, I do not want to implement this until I've implemented functionality where dailytwitter checks for "days it's missed" so to speak. Otherwise I fear that this may cause some missed posts if folk don't run cron often enough.
Comment #13
jadestorm commented