Roundcube Community Forum
SVN Releases => Issues & Bugs => Pending => Topic started by: MDC888 on June 21, 2010, 05:59:35 AM
-
Hi there,
I encounter a little problem with the last stable version of Roundcube:
It seems to be impossible to display received images, especially JPEG ones.
Opening the mail under another webmail or Outlook give a good result: the image is well displayed.
So here is a description of the problem:
Clicking on an attached JPG will give this message:
h-t-t-p://domainname.com/?_task=mail&_action=get&_mbox=INBOX&_uid=45&_part=2
Downloading the image won't help, because Windows (for example) can't read it: the preview system seems to be corrupted.
Opening the image in Photoshop will work, as it's not opening the preview only...
Could you help me?
Thanks ;)
-
Its working for me in the SVN, is there anything in your error log?
-
Nothing relative to this.
Are received images stocked in the upload temp dir?
-
Shouldn't be, I recommend upgrading the SVN to see if you stlll have the problem.
-
I have the last version...
Don't know what to do.
I want to verify files directly on the server. So could kyou give the default path for received temp files? Or is it the same than the uploaded temp files?
Thanks
-
You said that you where using the latest stable version witch would be 0.3.1 witch is nearly 6 month old. The files are stored on the mail server so I can give you a path to where there are stored.
-
Right!
I didn't know it was 6 month old. I will update at the end of the week and tell you what happens
cheers
-
I have the same problem...using .4 whats the fix?
-
Hey guys, still have issue with JPG in version 0.4.2. Anybody found solution? Other formats seem to be fine. I tried to play with files encoding, but no succes.
-
attach a message with this problem, maybe then you will get answer...
-
There is no error message, the image simply doesn't appear. Chrome (and other browsers) just show an unknown image icon and when I download it, multiple programs say the file's corrupted (but the filesize is appropriate). Seems like an encoding problem to me.
-
have you checked that you dont have any UTF8-BOMs at the start or blank lines at the end of any of your localisation or config files, including any in plugins?
-
have you checked that you dont have any UTF8-BOMs at the start or blank lines at the end of any of your localisation or config files, including any in plugins?
Thanks for tip, I tried to disable plugins one by one and found out it's caused by plugin "accounts". I changed encoding of config.inc.php and cs_CZ.inc files (of the plugin) from UTF8 to CP1250 and it works fine.