"too old" error using default Twitter plugin for DA
Aaron Kulbe
via web
The exact text of the error is: "since date or since_id is too old"
It will work if you manually modify the EngineUrl key date value to be recent enough it's still covered in Twitter's history.
I'm wondering if there is a way to make it work so that the date calculated is "30 days before today" (or 60 or 90, however many days Twitter keeps history for)?
Just a cursory look says it keeps history for the search for approximately 1.5 weeks.
That would make the modification of the plist file unnecessary.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Mark Grimes on 16 Sep, 2009 07:59 AM
Where does this error message appear? I cannot repeat the problem. Screenshot: Twitter plug-in debug
3 Posted by Aaron Kulbe on 16 Sep, 2009 08:15 AM
Just to make sure I set up the plugins correctly... I copied the plist files I got from your GitHub repo to ~/Library/Application Support/DEVONagent/Plugins/
Then I opened DA and dropped down the menu to select Twitter for search, I put in "github" as my search term.
I didn't get any results, so I looked at pages and log, and saw the error message on the log tab.
Once I opened the Twitter.plist and modified the date to something more recent, it worked.
Support Staff 4 Posted by Mark Grimes on 16 Sep, 2009 08:27 AM
The plug-in is installed correctly.
I removed all the cookies from DA on quit, tried it again against "github" and it worked. But what's probably more intriguing is that I tried entering that same search term in Twitter Search via Safari and it worked just fine.
Update: Tried it on my Leopard PPC machine -- never visited Twitter Search on it before, confirmed same results, the query "github since:2008-01-01" returns same results as a realtime search. I'm going to close this issue due to this query working outside the context of DA and the plug-in.
Support Staff 5 Posted by Mark Grimes on 16 Sep, 2009 08:39 AM
Please open an issue if you can isolate the problem to the plug-in more specifically. Thanks!
Mark Grimes closed this discussion on 16 Sep, 2009 08:39 AM.