I love the addition of the site-wide account. When a site-wide account is specified, though, UI inconsistencies arise.

  • Say there's already a site-wide account, and a user adds her own account. When she publishes a new node and announces it on Twitter, there's no way to tell which account it will post to. (When there are several per-user accounts, there's a handy drop-down. This doesn't exist when there's one site-wide and one per-user account.) [Screenshot]
  • The site-wide account appears on each user's profile in the "Twitter accounts" subtab. There's no indication this is a site-wide account, and the "import" and "delete" checkboxes serve no purpose here. [Screenshot]
  • The password field for the site-wide user account is somewhat confusing. Instead of filling in the password field with obfuscated characters (usually bullets or asterisks), it appears blank after the account is specified. Not only is it unclear if there's data in that field, it's confusing to anyone who wants to change other values on the Twitter settings form: Does leaving the password field blank when changing other options erase the password? Do they have to enter in the password each time they submit the form? [Screenshot]
CommentFileSizeAuthor
twitter_settings_form_password_field.png57.25 KBtodd nienkerk
twitter_accounts_subtab.png62.24 KBtodd nienkerk
post_to_twitter_form.png24.91 KBtodd nienkerk

Comments

wickwood’s picture

wickwood commented

I too am trying to figure these things out.

One thing I do know, regarding point 3, you do need to add your password every time you fill out the form. If you don't the connection to Twitter will not be made.

liza’s picture

liza commented

DITTO! same problems with a new D6 site.

steinmb’s picture

steinmb commented
Status: Active » Fixed

Fixed in latest 6.x and 7.x

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.