Hi, I just updated to 6.0.5. (from 6.0.4.) and noticed that while everything else seems to be working fine, file uploads seem to be broken (they worked fine in 6.0.4.). If I go to Files and upload a file (test 20k JPG named testfile.jpg), instead of getting that file uploaded to public/files and having the thumb (public/files/thumb_testfile.jpg) generated, I get a 48-byte file named testfile.jpg which contains the following *text*: #<ActionDispatch::Http::UploadedFile:0xb55a2124> In other words, instead of saving the binary data, Typo is saving a text identifier of some sort into the file (and thumb generation of course fails). I can see nothing about any sort of error in the log. Does anyone else have the same problem, or is it something with my setup? I'm using ruby 1.8.7 (ruby 1.8.7 (2010-04-19 patchlevel 253) [i686-linux], MBARI 0x8770, Ruby Enterprise Edition 2010.02) on Gentoo Linux, in case it matters. -Petri
on 2011-06-28 14:22
on 2011-06-28 15:14
Agh, realized that I should have made a ticket about this on Lighthouse instead of bothering the mailing list about it :}. Done. -Petri
on 2011-06-28 15:19
Le 28 juin 2011 13:44, Petri Wessman a crit : > -Petri Hi Petri, Thank you for reporting and filling a bug. This one will start with the current "can't reproduce yet". So I'll have to dig through this a little bit more. Best regards, Fred -- Frdric de Villamil "What's mine is mine. What's yours is still unsetteled" Go player proverb frederic@de-villamil.com tel: +33 (0)6 62 19 1337 http://t37.net Typo : http://typosphere.org
on 2011-06-28 15:26
On 06/28/2011 04:16 PM, Frederic de Villamil wrote: > Hi Petri, > > Thank you for reporting and filling a bug. This one will start with the current "can't reproduce yet". So I'll have to dig through this a little bit more. > > Best regards, > Fred Ok, thanks. Please let me know if I can help in any way in tracing this... I'll try to look at the Typo internals and insert some debugging stuff of my own, but I'm not familiar at all with how the file upload works there. It could of course be something specific to my system, but as noted it worked fine in 6.0.4. and I've ran "bundle update" and "RAILS_ENV=production rake db:migrate" without any errors coming to light. -Petri
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.