Announcement

Collapse
No announcement yet.

Image upload failed because the extension of this file did not match the content.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • saiff
    replied
    Originally posted by Wayne Luke View Post
    We need to be able to recreate the issue in order to fix it. Your bug hasn't been confirmed because we can't replicate it. You need to provide as much information as possible to the bug report including character sets and collation, language settings in vBulletin, the file names you're using, the name of the post. Step by step information on what happens when you upload an image. Whether it is these images only or every image known to mankind.

    I suspect it is due to using Arabic which we do not test or provide explicit support for.

    new issue



    thank you

    Leave a comment:


  • saiff
    replied
    I tried to load through the tool inside the editor . I had this error message



    Warning: file_put_contents(/morfqart/vbattachaa9f67b99332bd88cc7eac426a22623f.gif): failed to open stream: No such file or directory in .../vb/library/content/attach.php on line 465 Warning: Cannot modify header information - headers already sent by (output started at .../vb/vb.php:1167) in /home/user/public_html/vb/includes/vb5/frontend/controller/uploader.php on line 828 Warning: Cannot modify header information - headers already sent by (output started at .../vb/vb.php:1167) in /home/user/public_html/vb/includes/vb5/frontend/controller/uploader.php on line 832

    Leave a comment:


  • Wayne Luke
    replied
    We need to be able to recreate the issue in order to fix it. Your bug hasn't been confirmed because we can't replicate it. You need to provide as much information as possible to the bug report including character sets and collation, language settings in vBulletin, the file names you're using, the name of the post. Step by step information on what happens when you upload an image. Whether it is these images only or every image known to mankind.

    I suspect it is due to using Arabic which we do not test or provide explicit support for.

    Leave a comment:


  • saiff
    replied
    Php version. 5.6.31
    vbulletin 5.3.2
    Attachements in filesystem


    Last edited by saiff; Thu 24 Aug '17, 12:12am.

    Leave a comment:


  • Mark.B
    replied
    In this post I have attached the images you added to the bug report.

    So there isn't a bug here, as it works on this site.

    What version of php are you using?
    What actual version of vBulletin are you currently running?
    Are you storing attachments in the file system, or in the database?
    Attached Files

    Leave a comment:


  • saiff
    replied
    same problem here
    vbulletin 5.3.1- 5.3.2

    Leave a comment:


  • Mark.B
    replied
    The first 5.2.5 Alpha is already available. We do not provide future release dates though, as we do not work to specific dates, the software is released when it is ready.

    Please don't use an alpha release on a production site though. If you do and anything breaks, our only support will be to advise you to restore the previous version from backup.

    Leave a comment:


  • amart79196
    replied
    Do you know of an expected estimated date in which the alpha, Rc, or stables releases will happen for 5.2.5?

    Leave a comment:


  • amart79196
    replied
    Excellent, looking forward to getting 5.2.5 installed and reporting back to you. Thanks for all of your help everyone!

    Leave a comment:


  • Wayne Luke
    replied
    We're applying a fix for this in 5.2.5. Basically, if all the other security checks pass, the image will have its metadata stripped be rewritten as a valid JPEG file. This should help workaround phones and cameras that can't follow standards.

    Leave a comment:


  • amart79196
    replied
    I just uploaded this file to the bug tracker.

    Leave a comment:


  • Trevor Hannant
    replied
    Originally posted by amart79196 View Post
    Just to report, this problem is also in the latest version, 5.2.4 as well.

    1. Is there any viable workaround to get an image posted?
    2. Can we expect this to be fixed in the next release?
    1. Not at this time
    2. Depends on whether people provide images that have been causing issues so that they can look into these and work to resolve the issue. The more sample images that have been causing issues, the more likely the developers will be able to resolve this!

    Please attach any images that are flagging up the same message to the Bug Report, NOT here:

    Leave a comment:


  • amart79196
    replied
    Just to report, this problem is also in the latest version, 5.2.4 as well.

    1. Is there any viable workaround to get an image posted?
    2. Can we expect this to be fixed in the next release?

    Leave a comment:


  • Kevin Sours
    replied
    We're still looking into this. My apologies for the delay. The core issue is that the file in question is tripping some security checks we have in place. The root issue is that it's relatively easy to create a completely valid image that will execute PHP code if you can convince the system to treat it as a PHP file. Unfortunately the image standards have a lot of essentially undefined sections that various cameras do some strange things with, so sorting out what a valid image looks like isn't as easy as it should be. So we need to tweak the checks to accept a wider variety of (legitimate) images, but I hope you understand why we're moving carefully on this. We think we've worked out a process that will greatly improve things.

    We do have a sample image, but we could use a few more to make sure that there isn't anything out there we haven't accounted for (there probably is -- I expect this to be a iterative process)
    Kevin

    Leave a comment:


  • naszeaudio
    replied
    Sorry guys for delay. We are using GD at the moment (as apple product users says it works better for them than imagemagick).

    I understand u have sample file already.

    Leave a comment:

Related Topics

Collapse

Working...
X