th3br41n

I’m using an Apache 2 server with PHP 5.6 64-bit on a production server (Linux), while I’m using an Apache 2 server with PHP 5.6 32-bit on a local server (Windows). I have experienced the bug on my local server.

• This reply was modified 7 years, 11 months ago by th3br41n.
• This reply was modified 7 years, 11 months ago by th3br41n.

Ok, thanks…

Ok…
Do you have any suggestion to discover the cause the next time I have the problem?

No error messages is shown, just silently fails with no notice.

However, on a new post with the same text, the Tweet is sent.

If it were the truncation routine it should be reproducible, since at the same text should correspond the same truncation. Am I wrong?

The Twitter interface part is objectively complex, but it reflects Twitter security needs…
Then you can understand other options step by step… and, since it is a free plugin, you can also think to write a small starting guide.

from time to time there is a post like this…
The difficult part of the configuration is the interface with Twitter, and it is not due to the plugin but to Twitter security policies that guarantee users.
Other settings are really intuitive and immediate…

So I have to disagree with you.

With the option OFF, I can see that the function jd_doTwitterAPIPost is called for every post I update with a “bluk operation”, for example by adding a new tag or recovering posts from trash. In both cases $_POST['_inline_edit'] is not set, thus the value of wpt_inline_edits is not important. In jd_doTwitterAPIPost, the plugin only checks for duplicates of the last tweet.

(WordPress 3.5.1)

However as I can see, the plugin can send multiple posts when I bulk edit posts (e.g., adding a tag to posts) or when I recover posts from trash. Am I wrong?

Just to give my personal contribution to this problem…

The plugin can post multiple tweets if the “Allow status updates from Quick Edit” option is selected. This behaviour is controlled by the option wpt_inline_edits. Is it possible that this option is changed by some other plugin?

I would suggest to use a value more complex than 1 to identify that the user has checked this sensitive option and to change the logic of lines 664-668 of wp-to-twitter.php to:

if ( get_option('wpt_inline_edits') == 'this_is_a_complex_value' ) {
  if ( isset($_POST['_inline_edit']) ) { $is_inline_edit = true; }
} else {
  if ( isset($_POST['_inline_edit']) ) { return; }
}

this could reduce the probability of unwanted behaviours.

It seems you implemented this in the new version… ??

You cannot blame the plugin if you are not able to keep your API keys secret or if you do not update your WordPress thus allowing everyone to exploit its vulnerabilities…

The most hilarious part, is that everyone can analyze the source code of the plugin and discover that it doesn’t do anything dangerous… ??

It could be a good idea to let users to add their own shortener, actually you need only a URL for the API method (that incorporate API keys) with a {url} parameter. Almost all shortener support the plain/text (return) format. A button TEST near the configuration could help people to configure the shortener.

es. https://my.shortener.api/shorten?url={url}&apikey=my_api_key