Currently, the 'Twitter' operates as user unfriendly as it can get; if a node is announced on Twitter, it reports after saving the node: "Message was posted successfuly" (localized: "Nachricht erfolgreich gepostet"). This message appears in green on top of the node.
Under certain circumstances, on top of the green message might beanother one: "Twitter returned an error: Status is over 140 characters". As the module allows to use tokens, it is
a) impossible for users to figure out how long the twitter status update will become, and
b) it is impossible to guess from to contradictory Drupal messages, if something was posted or not (screenshot attached).
So the user has to go to the Twitter account and manually verify if the "green" or the "red" message is true. The 'Twitter' module does not relive him from going to the Twitter account which makes using the module quite obsolte as he could now directly post on Twitter as well.
Thusly, this feature requests has two components:
a) Please do evaluate proper success/error messages. Please avoid contradictory Drupal messages like in the example quoted above;
b) Please do some checking if the Twitter status at least formally can be posted to Twitter. If Twitter does not allow to post more than 140 characters, the 'Twitter' module must never try to post longer messages. The 'Twitter' module could either automatically truncate the message before posting to Twitter, or (better) notify the user that the string will be too long, and instruct what he/she can do about it.
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| twitter-status-messages.jpeg | 25.32 KB | asb |
Comments
Comment #1
xurizaemonPretty sure we fixed that. Years old issue anyway.