NextScripts 4.0.4 : Unable to Post to Twitter (Bad Image) or artifacts

  • Hi,

    The problem with “bad image” is still present in version 4.0.4.

    When the upload of the image is activated:
    – either the tweet and the image are sent but the image contains artifacts
    – Either the tweet is not sent, there is. The error “BAD IMAGE”

    Example of tweet with artifacts :

    I have the problem on my 2 sites

    • This topic was modified 7 years, 1 month ago by Djib's.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author NextScripts

    (@nextscripts)

    Well, your server is changing the uploaded files. Twitter used to tolerate that. It looks like it is not ok with that anymore (since the depreciation of the “update_with_media” endpoind). All altered images cause “bad image” error.
    New enpoint allows base64 encoding for images, but it looks like encoded images are still getting alerted by your server, Instead of “bad image” error, encoding is causing artifacts.

    What can be done?
    Best solution will be to fix your server. You need to find a VERY good server admin who will be able to determine why your server is doing that and how to fix that.

    We are still investigating the problem and trying to find out if anything can be done from our code.

    Thread Starter Djib's

    (@djibs13)

    I found why some images are uploaded (with artifacts) and why for others there is an error and the tweet is not sent.

    If the image contains the EXIF data, the image is uploaded. If it does not contain one, there is the error. I did the test on 10 images.

    You can apply a patch?

    (I often use software to optimize the size of images, the software removes EXIF data to save space)

    • This reply was modified 7 years, 1 month ago by Djib's.
    Plugin Author NextScripts

    (@nextscripts)

    Do you have any EXIF extensions installed on your PHP or server in general? Something like https://php.net/manual/en/book.exif.php ?

    Thread Starter Djib's

    (@djibs13)

    Yes I have EXIF extension (and PHP Version 5.6.31)

    View post on imgur.com

    @nextscripts – there’s no way Twitter is requiring EXIF data to be able to upload, because I have no issues using Hootsuite or Buffer with the exact same images.

    Would really love a fix for this – removing EXIF data really saves space and helps with optimization.

    Thread Starter Djib's

    (@djibs13)

    I confirm, no probleme with twitter clients like hootsuite, tweetbot, buffer, twitterrific …

    Plugin Author NextScripts

    (@nextscripts)

    @elrebrin, @djibs13 please read my post above. It starts with the words:

    Well, your server is changing the uploaded files.

    and ends with

    Best solution will be to fix your server.

    The keyword there is “Your server”. It’s not a general issue. Almost nobody else is affected by this.

    hootsuite, tweetbot, buffer, twitterrific and all others get your content and post it from THEIR OWN server. Their server has no issues. Your server has issues.

    It’s the main difference between SNAP and all those other services. We do not act as middleman between your content and your networks. Your server posts directly to Twitter.

    We are unable to replicate your issue in our environment. We tried to install exif on php 5.6, but still images are coming without any artifacts. We even tried to post your images:

    Still no issues.

    • This reply was modified 7 years, 1 month ago by NextScripts.
    • This reply was modified 7 years, 1 month ago by NextScripts.
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘NextScripts 4.0.4 : Unable to Post to Twitter (Bad Image) or artifacts’ is closed to new replies.

Tags