Bug #92

Media thumbnail creation not working under Windows Vista

Added by Bernard Chhun about 3 years ago. Updated about 2 years ago.

Status:Invalid Start date:2009-02-01
Priority:Undecided Due date:
Assignee:Alex Cartwright % Done:

0%

Category:TangoCMS::Modules
Target version:-
PHP Version:

Description

Server

Apache 2.2.8, PHP 5.2.5 (XAMPP under Windows Vista)

Expected behavior

When I upload an image file using the media module it should create a thumbnail correctly.

Actual behavior

Thumbnail creation for an image file is not working and says the following: "You must upload a thumbnail image for Video and Audio files". The file extension I used until now was *.JPG & *.gif.
The thumbnail creation process ain't working. It always says: "Thumbnail could not be created." until I specify one.

Alex recommended that I install the fileinfo extension. Which I did. and here's the error log:

    [2009-01-27T22:03:58-05:00] [127.0.0.1 | uid 2] [warning] -- (common.php:344) File mime type could not be got. Unable to create resource for file "C:\xampp\tmp\php16A1.tmp" 
    [2009-01-27T22:03:58-05:00] [127.0.0.1 | uid 2] [warning] -- (common.php:344) File mime type could not be got. Unable to create resource for file "C:\xampp\tmp\php16B2.tmp" 
    [2009-01-27T22:03:58-05:00] [127.0.0.1 | uid 2] [warning] -- (common.php:344) File mime type could not be got. Unable to create resource for file "./html/uploads/media/3//vne4GgFkh1/2nmWJgcQzN.JPG" 

Forum's discussion about this bug: http://forums.tangocms.org/viewtopic.php?f=4&t=39


Related issues

related to TangoCMS - Bug #214: Media upload not work under Windows Closed 2009-12-16

History

Updated by Alex Cartwright almost 3 years ago

  • Category set to TangoCMS::Modules
  • Status changed from New to Confirmed
  • Assignee set to Alex Cartwright

Confirmed, will fix for 2.3.0

Updated by Alex Cartwright about 2 years ago

  • Status changed from Confirmed to Invalid

See bug #214 and changeset commit:"892ef5104f3a88a172103787c7b16de158a0984f" for details. I believe this fixes the bug, however with such an old report and slightly different error messages I can't be 100% sure. Closing for now, please re-open if this has not fixed it.

Also available in: Atom PDF