Hey Darren, this seems like an awesome package! However, somehow it's not working for me.
Hope you can help me out. I've changed the document_type alias from BlogPostComment to blogpostcomment because of the lowercasing in the log, did not make any difference though. Other than that, it seems like everything is configured correctly.
The /umbraco/plugins/DocumentPublishTweet/tweet.config (with the username and password censored obviously, they are correct though):
<config> <accounts> <account key="mainaccount"> <login>username</login> <password>password</password> </account> </accounts> <document_types> <document_type alias="blogpostcomment"> <tweets> <tweet> <account>mainaccount</account> <message>d sebastiaan #title# - #url#</message> </tweet> </tweets> </document_type> </document_types> </config>
The umbracoLog messages:
i was never able to get this working either, but i chalked it up to user failure and had to move away from working on my site to paying gigs :P if you figure it out, let me know!
@bob - I did a complete rewrite since you had those issues before.
@Sebastiaan - Am looking into your issue now.
@Sebastiaan can you try adding a domain_filter attrib to your tweet as specified in the docs and let me know if that works for you.
I can be empty. I think I have a bug where it will throw an expection if the domain filter attrib were to be null.
Unfortunately, I am still getting the same messages in the log file, the config file now looks like this:
<config> <accounts> <account key="mainaccount"> <login>cultiv</login> <password>123barry</password> </account> </accounts> <document_types> <document_type alias="blogpostcomment"> <tweets> <tweet domain_filter="cultiv.nl"> <account>mainaccount</account> <message>d sebastiaan #title# - #url#</message> </tweet> </tweets> </document_type> </document_types> </config>
Maybe I have some uncommon set-up? Windows 2008 server (IIS 7), extensionless URL's maybe?
Does your log table extract still look the same after those config changes?
Yes sir, as stated in my previous comment.. ;-)
I'm afraid it is a bit of a mystery to me at the moment.
Could you perhaps try it with an empty domain_filter attribute?
You config and O/S shouldn't make any difference at all.
Sorry, still no dice. I tried an empty domain filter, I tried to include "www.", als I saw in the log that my index was corrupt, so I did a re-index, tried all options again to make sure that the index wasn't interfering. Still nothing.
The config should not make a difference, but might still be the fact that I'm running the .net 3.5 config and IIS is in pipeline mode?
I'm having the same issue. Do you think it could be a security issue on Windows 7?
The log file says it's been tweeted as well as the fact that I have stepped through it using a debugger and the event it fired.
I'm not sure what I should be getting back from Twitter but it doesnt seem like the correct info.