I first posted this message earlier in the Pro section by mistake. My apologies for any inconvenience it may have caused.
I am a Newbie and I am just getting the feel of the software. I am very pleased with it so far. Your setup instructions for FaceBook and Twitter are crystal clear and the set up went smoothly. All the tweets have gone out flawlessly from the very beginning, except under one circumstance.
(I am using Joomla 2.5.8. Rochen is my host (The Joomla.org host) so PHP etc are the latest.) AutoTweetNG version is 6.3.5.
If I have an article set for front-end editor access instead of public access, and then, just before publication time, I switch it to public access, no tweet goes out on or after the publication time. But this doesn't always happen. Sometimes it does and sometimes it doesn't!
There should have been five articles queued for publication. But there were only two.
At the time one of the three unqueued articles was loaded into the JCE editor, it was saved as "published" and "front-end editor." The publication date was back-dated so that it could be accessed in the front end. It never appeared in the queue.
(I have a Joomla problem since I moved from 1.5 to 2.5: I can't see not-yet-published articles in the front end even when logged in as superuser. Haven't figured out why. Use of "front-end editor is a work-around.)
The other two articles that did not appear in the queue were created in a peculiar way. I uploaded a 9000 word article into the JCE editor and saved it as "parts 1,2,3" and then corrected all the HTML problems. I then copied the article into two more editor windows and saved them as part 1 and part 2. Then I renamed the original whole article as part 3. (stripping the unwanted 2/3rds from the respective three parts.) This was supposed to save me a lot of HTML work. It did. But part 3 never appeared in the queue. Even though it was always published/public.
My solution was to copy the non-appearing articles into blank editing screens, save them, delete the originals, and clean up the SH404sef. The articles immediately appeared in the queue.
So, I recognize that I have created a unique hell for my exclusive enjoyment. Unlikely to be a problem for anyone else.
I also went into the DB as an experiment and renumbered one of the articles that did not appear from its original 1039 to a as-yet-unused 1052. Didn't work. Don't recommend it. I had some problems getting back into my backend, which may or may not have been related to the DB change, but was more likely due to the increasingly unpredictable FireFox browser.
So, I have thought about saying "yes" to the "On Modification" setting in the Content Plugin Posting Filter but have hesitated to do so because when an article runs to several thousand words, there is always a mistake or two that is caught after publication. I don't want to bother people with a repeat Tweet when it is the same article. On the other hand, I am told people don't notice or pay much attention to repeat tweets because they come and go so quickly. Of course facebook is a bit different since the results remain.
I would appreciate any suggestions in this area of allowing repeated tweets for merely correcting typos in a long article. Or anything else that I should be thinking about!
I can confirm that if when you first save an article in your editor you make sure that it is published and public, you are OK. The article appears in the queue and stays there until you actually publish and the tweet goes out.
I have done this with two articles. They both appeared in the queue. I then went back and changed them to front-end editor so others could work on them. They remained in the queue. When they were switched back from front-end editor to public the tweets went out normally at the publication time.