It took a few gos, but I seem to have Autotweet 3.0 working on my site now. Thanks for the extension!

My setup is fairly vanilla; I'm just creating articles normally in the Joomla! backend. However, I did have these problems:

1. Initially, articles weren't getting added to the job queue. Turns out the AutoTweet NG Content-Extension wasn't enabled by default.

2. There is a delay before a new article is tweeted. Turns out Autotweet requires a visit to your home page in order to trigger tweets. There also appears to be a delay of a couple of minutes before an article from the job queue will tweet. I'd prefer it to just publish the tweet directly from the Joomla! backend as soon as the article is published.

3. I get an error when using the is.gd shortening service, saying:
AutoTweet - short url service is.gd failed, normal url used - http_code = 0, err = ()
However, bit.ly works.

Cheers,
Graham

Hi!

Initially, articles weren't getting added to the job queue. Turns out the AutoTweet NG Content-Extension wasn't enabled by default.


Yes, as described in the documentation, this is to prevent accidental posts. See the instructions for new installation: www.1st-movers.com/products/autotweet/au...ntation#installation

There is a delay before a new article is tweeted...

Yes, you will find some information in the documentation about this and why this is the only way to get this work with SEF URLs. See also this FAQ entry: www.1st-movers.com/faq/3-autotweet/15-ho...message-sending-work

I get an error when using the is.gd shortening service...

is.gd has sometimes problems when the timeout on your server is to short. OR the URL is blocked by some firewall rules or something else.


Greetings
Ulli

Thanks for the clarifications Ulli.

Initially, articles weren't getting added to the job queue. Turns out the AutoTweet NG Content-Extension wasn't enabled by default.


Yes, as described in the documentation, this is to prevent accidental posts. See the instructions for new installation: www.1st-movers.com/products/autotweet/au...ntation#installation


This came as something of a surprise to me. Personally, I'd rather the extension install into an enabled state. I don't see accidental posts as a problem, compared to having to work out why the extension didn't appear to work out-of-the box. The less documentation I need to read to get something working, the better!

Cheers,
Graham