Ruby on Rails - Paperclip Error
For reference I have been following this tutorial: https://devcenter.heroku.com/articles/paperclip-s3 Except I am in localhost testing right now, so I installed the Figaro gem and placed my S3 info in application.yml.
Using Rails v4, Cocaine v0.5.3, and Paperclip v4.1.0 (unsure if any other gem version numbers need to be mentioned).
I have a model called SubmissionDetails, where in its new.html.erb I am trying to upload a jpg to a column called attachment. Here is the relevant model code:
has_attached_file :attachment, styles: {
thumb: '200x200>',
large: '800x800>'
}
validates_attachment_content_type :attachment, content_type: /Aimage/.*Z/
When I try to upload a jpg, it returns back to the form with the following error message:
1 error prohibited this submission_detail from being saved:
Attachment translation missing:
en.activerecord.errors.models.submission_detail.attributes.attachment.spoofed_media_type
I understand some of the error, that text to display this error message is missing from my en.yml file, but what about that spoofed media type part?
This shows up in my server console, not sure if this is relevant:
[paperclip] Content Type Spoof: Filename header.jpg (["image/jpeg"]), content type discovered from file command: . See documentation to allow this combination.
(0.0ms) rollback transaction
ruby-on-rails paperclip
add a comment |
For reference I have been following this tutorial: https://devcenter.heroku.com/articles/paperclip-s3 Except I am in localhost testing right now, so I installed the Figaro gem and placed my S3 info in application.yml.
Using Rails v4, Cocaine v0.5.3, and Paperclip v4.1.0 (unsure if any other gem version numbers need to be mentioned).
I have a model called SubmissionDetails, where in its new.html.erb I am trying to upload a jpg to a column called attachment. Here is the relevant model code:
has_attached_file :attachment, styles: {
thumb: '200x200>',
large: '800x800>'
}
validates_attachment_content_type :attachment, content_type: /Aimage/.*Z/
When I try to upload a jpg, it returns back to the form with the following error message:
1 error prohibited this submission_detail from being saved:
Attachment translation missing:
en.activerecord.errors.models.submission_detail.attributes.attachment.spoofed_media_type
I understand some of the error, that text to display this error message is missing from my en.yml file, but what about that spoofed media type part?
This shows up in my server console, not sure if this is relevant:
[paperclip] Content Type Spoof: Filename header.jpg (["image/jpeg"]), content type discovered from file command: . See documentation to allow this combination.
(0.0ms) rollback transaction
ruby-on-rails paperclip
Apparently, PaperClip thinks that this is not a valid jpeg file, respectively couldn't determine the real file type using thefile
command. Have you tried different file types (png, gif)?
– pduersteler
Feb 20 '14 at 15:34
Yes, I tried a png just now--same error.
– Rachel9494
Feb 20 '14 at 15:51
add a comment |
For reference I have been following this tutorial: https://devcenter.heroku.com/articles/paperclip-s3 Except I am in localhost testing right now, so I installed the Figaro gem and placed my S3 info in application.yml.
Using Rails v4, Cocaine v0.5.3, and Paperclip v4.1.0 (unsure if any other gem version numbers need to be mentioned).
I have a model called SubmissionDetails, where in its new.html.erb I am trying to upload a jpg to a column called attachment. Here is the relevant model code:
has_attached_file :attachment, styles: {
thumb: '200x200>',
large: '800x800>'
}
validates_attachment_content_type :attachment, content_type: /Aimage/.*Z/
When I try to upload a jpg, it returns back to the form with the following error message:
1 error prohibited this submission_detail from being saved:
Attachment translation missing:
en.activerecord.errors.models.submission_detail.attributes.attachment.spoofed_media_type
I understand some of the error, that text to display this error message is missing from my en.yml file, but what about that spoofed media type part?
This shows up in my server console, not sure if this is relevant:
[paperclip] Content Type Spoof: Filename header.jpg (["image/jpeg"]), content type discovered from file command: . See documentation to allow this combination.
(0.0ms) rollback transaction
ruby-on-rails paperclip
For reference I have been following this tutorial: https://devcenter.heroku.com/articles/paperclip-s3 Except I am in localhost testing right now, so I installed the Figaro gem and placed my S3 info in application.yml.
Using Rails v4, Cocaine v0.5.3, and Paperclip v4.1.0 (unsure if any other gem version numbers need to be mentioned).
I have a model called SubmissionDetails, where in its new.html.erb I am trying to upload a jpg to a column called attachment. Here is the relevant model code:
has_attached_file :attachment, styles: {
thumb: '200x200>',
large: '800x800>'
}
validates_attachment_content_type :attachment, content_type: /Aimage/.*Z/
When I try to upload a jpg, it returns back to the form with the following error message:
1 error prohibited this submission_detail from being saved:
Attachment translation missing:
en.activerecord.errors.models.submission_detail.attributes.attachment.spoofed_media_type
I understand some of the error, that text to display this error message is missing from my en.yml file, but what about that spoofed media type part?
This shows up in my server console, not sure if this is relevant:
[paperclip] Content Type Spoof: Filename header.jpg (["image/jpeg"]), content type discovered from file command: . See documentation to allow this combination.
(0.0ms) rollback transaction
ruby-on-rails paperclip
ruby-on-rails paperclip
edited Apr 27 '15 at 3:42


jvnill
25.9k26374
25.9k26374
asked Feb 20 '14 at 15:32
Rachel9494Rachel9494
6241621
6241621
Apparently, PaperClip thinks that this is not a valid jpeg file, respectively couldn't determine the real file type using thefile
command. Have you tried different file types (png, gif)?
– pduersteler
Feb 20 '14 at 15:34
Yes, I tried a png just now--same error.
– Rachel9494
Feb 20 '14 at 15:51
add a comment |
Apparently, PaperClip thinks that this is not a valid jpeg file, respectively couldn't determine the real file type using thefile
command. Have you tried different file types (png, gif)?
– pduersteler
Feb 20 '14 at 15:34
Yes, I tried a png just now--same error.
– Rachel9494
Feb 20 '14 at 15:51
Apparently, PaperClip thinks that this is not a valid jpeg file, respectively couldn't determine the real file type using the
file
command. Have you tried different file types (png, gif)?– pduersteler
Feb 20 '14 at 15:34
Apparently, PaperClip thinks that this is not a valid jpeg file, respectively couldn't determine the real file type using the
file
command. Have you tried different file types (png, gif)?– pduersteler
Feb 20 '14 at 15:34
Yes, I tried a png just now--same error.
– Rachel9494
Feb 20 '14 at 15:51
Yes, I tried a png just now--same error.
– Rachel9494
Feb 20 '14 at 15:51
add a comment |
3 Answers
3
active
oldest
votes
That message is raised by a validation check for content spoofing.
For Paperclip v.4 this generates a bug https://github.com/thoughtbot/paperclip/issues/1429
While for Paperclip v.3, it seems it just throws a deprecation warning, https://github.com/thoughtbot/paperclip/issues/1423
So I'd wait for Paperclip team to solve this bug before using version 4. At the moment I'd rather keep using version 3.
gem "paperclip", "~> 3.5.3"
Or add this to an initializer to disable spoofing protection:
config/initializers/paperclip_media_type_spoof_detector_override.rb
require 'paperclip/media_type_spoof_detector'
module Paperclip
class MediaTypeSpoofDetector
def spoofed?
false
end
end
end
see Can't upload image using Paperclip 4.0 Rails 3
Thank you! Hope they solve the bug soon.
– Rachel9494
Feb 20 '14 at 16:00
This bug is a real stinger! Thanks for this workaround.
– RickyD
Mar 25 '14 at 19:00
1
Confirmed to still be an issue on4.1.1
.spoofed?
override fixes it for now.
– Joshua Pinter
Nov 5 '14 at 18:18
2
Still an issue on4.2.0
. Thanks for thespoofed?
fix.
– pabo
Jan 24 '15 at 23:15
add a comment |
As explained recently in the comments of the issue (https://github.com/thoughtbot/paperclip/issues/1429#issuecomment-49821032), adding :
Paperclip.options[:command_path] = '/usr/bin'
to config/initializers/paperclip.rb solved the problem.
1
I don't think the accepted answer is the better way to deal with that. One year after and using paperclip v4.3 the issue was solved setting the command_path.
– gcstr
Oct 18 '15 at 22:03
That didn't do the trick for me.
– Steve Beer
Mar 2 '17 at 15:50
Have you checked where the "identify" command is installed on your system ? ($ whereis identify)
– ZeDalaye
Mar 2 '17 at 19:45
Worked for us, thank you.
– Richard Peck
Jun 12 '17 at 7:03
add a comment |
On the same issue, I found another workaround that can be applied at model level, without edit any initializer:
class PaperclipModel < ActiveRecord::Base
has_attached_file :attachment, { validate_media_type: false }
validates_attachment :attachment, {
# tweak as desired
content_type: { content_type: ["text/csv", "text/plain", Paperclip::ContentTypeDetector::SENSIBLE_DEFAULT] }
}
end
Basically, this skip media_type
and content_type
validations to avoid spoofed error on PaperclipModel
attachment. For more details see here.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f21912322%2fruby-on-rails-paperclip-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
That message is raised by a validation check for content spoofing.
For Paperclip v.4 this generates a bug https://github.com/thoughtbot/paperclip/issues/1429
While for Paperclip v.3, it seems it just throws a deprecation warning, https://github.com/thoughtbot/paperclip/issues/1423
So I'd wait for Paperclip team to solve this bug before using version 4. At the moment I'd rather keep using version 3.
gem "paperclip", "~> 3.5.3"
Or add this to an initializer to disable spoofing protection:
config/initializers/paperclip_media_type_spoof_detector_override.rb
require 'paperclip/media_type_spoof_detector'
module Paperclip
class MediaTypeSpoofDetector
def spoofed?
false
end
end
end
see Can't upload image using Paperclip 4.0 Rails 3
Thank you! Hope they solve the bug soon.
– Rachel9494
Feb 20 '14 at 16:00
This bug is a real stinger! Thanks for this workaround.
– RickyD
Mar 25 '14 at 19:00
1
Confirmed to still be an issue on4.1.1
.spoofed?
override fixes it for now.
– Joshua Pinter
Nov 5 '14 at 18:18
2
Still an issue on4.2.0
. Thanks for thespoofed?
fix.
– pabo
Jan 24 '15 at 23:15
add a comment |
That message is raised by a validation check for content spoofing.
For Paperclip v.4 this generates a bug https://github.com/thoughtbot/paperclip/issues/1429
While for Paperclip v.3, it seems it just throws a deprecation warning, https://github.com/thoughtbot/paperclip/issues/1423
So I'd wait for Paperclip team to solve this bug before using version 4. At the moment I'd rather keep using version 3.
gem "paperclip", "~> 3.5.3"
Or add this to an initializer to disable spoofing protection:
config/initializers/paperclip_media_type_spoof_detector_override.rb
require 'paperclip/media_type_spoof_detector'
module Paperclip
class MediaTypeSpoofDetector
def spoofed?
false
end
end
end
see Can't upload image using Paperclip 4.0 Rails 3
Thank you! Hope they solve the bug soon.
– Rachel9494
Feb 20 '14 at 16:00
This bug is a real stinger! Thanks for this workaround.
– RickyD
Mar 25 '14 at 19:00
1
Confirmed to still be an issue on4.1.1
.spoofed?
override fixes it for now.
– Joshua Pinter
Nov 5 '14 at 18:18
2
Still an issue on4.2.0
. Thanks for thespoofed?
fix.
– pabo
Jan 24 '15 at 23:15
add a comment |
That message is raised by a validation check for content spoofing.
For Paperclip v.4 this generates a bug https://github.com/thoughtbot/paperclip/issues/1429
While for Paperclip v.3, it seems it just throws a deprecation warning, https://github.com/thoughtbot/paperclip/issues/1423
So I'd wait for Paperclip team to solve this bug before using version 4. At the moment I'd rather keep using version 3.
gem "paperclip", "~> 3.5.3"
Or add this to an initializer to disable spoofing protection:
config/initializers/paperclip_media_type_spoof_detector_override.rb
require 'paperclip/media_type_spoof_detector'
module Paperclip
class MediaTypeSpoofDetector
def spoofed?
false
end
end
end
see Can't upload image using Paperclip 4.0 Rails 3
That message is raised by a validation check for content spoofing.
For Paperclip v.4 this generates a bug https://github.com/thoughtbot/paperclip/issues/1429
While for Paperclip v.3, it seems it just throws a deprecation warning, https://github.com/thoughtbot/paperclip/issues/1423
So I'd wait for Paperclip team to solve this bug before using version 4. At the moment I'd rather keep using version 3.
gem "paperclip", "~> 3.5.3"
Or add this to an initializer to disable spoofing protection:
config/initializers/paperclip_media_type_spoof_detector_override.rb
require 'paperclip/media_type_spoof_detector'
module Paperclip
class MediaTypeSpoofDetector
def spoofed?
false
end
end
end
see Can't upload image using Paperclip 4.0 Rails 3
edited May 23 '17 at 12:18
Community♦
11
11
answered Feb 20 '14 at 15:40


Mini JohnMini John
5,20354488
5,20354488
Thank you! Hope they solve the bug soon.
– Rachel9494
Feb 20 '14 at 16:00
This bug is a real stinger! Thanks for this workaround.
– RickyD
Mar 25 '14 at 19:00
1
Confirmed to still be an issue on4.1.1
.spoofed?
override fixes it for now.
– Joshua Pinter
Nov 5 '14 at 18:18
2
Still an issue on4.2.0
. Thanks for thespoofed?
fix.
– pabo
Jan 24 '15 at 23:15
add a comment |
Thank you! Hope they solve the bug soon.
– Rachel9494
Feb 20 '14 at 16:00
This bug is a real stinger! Thanks for this workaround.
– RickyD
Mar 25 '14 at 19:00
1
Confirmed to still be an issue on4.1.1
.spoofed?
override fixes it for now.
– Joshua Pinter
Nov 5 '14 at 18:18
2
Still an issue on4.2.0
. Thanks for thespoofed?
fix.
– pabo
Jan 24 '15 at 23:15
Thank you! Hope they solve the bug soon.
– Rachel9494
Feb 20 '14 at 16:00
Thank you! Hope they solve the bug soon.
– Rachel9494
Feb 20 '14 at 16:00
This bug is a real stinger! Thanks for this workaround.
– RickyD
Mar 25 '14 at 19:00
This bug is a real stinger! Thanks for this workaround.
– RickyD
Mar 25 '14 at 19:00
1
1
Confirmed to still be an issue on
4.1.1
. spoofed?
override fixes it for now.– Joshua Pinter
Nov 5 '14 at 18:18
Confirmed to still be an issue on
4.1.1
. spoofed?
override fixes it for now.– Joshua Pinter
Nov 5 '14 at 18:18
2
2
Still an issue on
4.2.0
. Thanks for the spoofed?
fix.– pabo
Jan 24 '15 at 23:15
Still an issue on
4.2.0
. Thanks for the spoofed?
fix.– pabo
Jan 24 '15 at 23:15
add a comment |
As explained recently in the comments of the issue (https://github.com/thoughtbot/paperclip/issues/1429#issuecomment-49821032), adding :
Paperclip.options[:command_path] = '/usr/bin'
to config/initializers/paperclip.rb solved the problem.
1
I don't think the accepted answer is the better way to deal with that. One year after and using paperclip v4.3 the issue was solved setting the command_path.
– gcstr
Oct 18 '15 at 22:03
That didn't do the trick for me.
– Steve Beer
Mar 2 '17 at 15:50
Have you checked where the "identify" command is installed on your system ? ($ whereis identify)
– ZeDalaye
Mar 2 '17 at 19:45
Worked for us, thank you.
– Richard Peck
Jun 12 '17 at 7:03
add a comment |
As explained recently in the comments of the issue (https://github.com/thoughtbot/paperclip/issues/1429#issuecomment-49821032), adding :
Paperclip.options[:command_path] = '/usr/bin'
to config/initializers/paperclip.rb solved the problem.
1
I don't think the accepted answer is the better way to deal with that. One year after and using paperclip v4.3 the issue was solved setting the command_path.
– gcstr
Oct 18 '15 at 22:03
That didn't do the trick for me.
– Steve Beer
Mar 2 '17 at 15:50
Have you checked where the "identify" command is installed on your system ? ($ whereis identify)
– ZeDalaye
Mar 2 '17 at 19:45
Worked for us, thank you.
– Richard Peck
Jun 12 '17 at 7:03
add a comment |
As explained recently in the comments of the issue (https://github.com/thoughtbot/paperclip/issues/1429#issuecomment-49821032), adding :
Paperclip.options[:command_path] = '/usr/bin'
to config/initializers/paperclip.rb solved the problem.
As explained recently in the comments of the issue (https://github.com/thoughtbot/paperclip/issues/1429#issuecomment-49821032), adding :
Paperclip.options[:command_path] = '/usr/bin'
to config/initializers/paperclip.rb solved the problem.
answered Aug 3 '14 at 8:56
ZeDalayeZeDalaye
449515
449515
1
I don't think the accepted answer is the better way to deal with that. One year after and using paperclip v4.3 the issue was solved setting the command_path.
– gcstr
Oct 18 '15 at 22:03
That didn't do the trick for me.
– Steve Beer
Mar 2 '17 at 15:50
Have you checked where the "identify" command is installed on your system ? ($ whereis identify)
– ZeDalaye
Mar 2 '17 at 19:45
Worked for us, thank you.
– Richard Peck
Jun 12 '17 at 7:03
add a comment |
1
I don't think the accepted answer is the better way to deal with that. One year after and using paperclip v4.3 the issue was solved setting the command_path.
– gcstr
Oct 18 '15 at 22:03
That didn't do the trick for me.
– Steve Beer
Mar 2 '17 at 15:50
Have you checked where the "identify" command is installed on your system ? ($ whereis identify)
– ZeDalaye
Mar 2 '17 at 19:45
Worked for us, thank you.
– Richard Peck
Jun 12 '17 at 7:03
1
1
I don't think the accepted answer is the better way to deal with that. One year after and using paperclip v4.3 the issue was solved setting the command_path.
– gcstr
Oct 18 '15 at 22:03
I don't think the accepted answer is the better way to deal with that. One year after and using paperclip v4.3 the issue was solved setting the command_path.
– gcstr
Oct 18 '15 at 22:03
That didn't do the trick for me.
– Steve Beer
Mar 2 '17 at 15:50
That didn't do the trick for me.
– Steve Beer
Mar 2 '17 at 15:50
Have you checked where the "identify" command is installed on your system ? ($ whereis identify)
– ZeDalaye
Mar 2 '17 at 19:45
Have you checked where the "identify" command is installed on your system ? ($ whereis identify)
– ZeDalaye
Mar 2 '17 at 19:45
Worked for us, thank you.
– Richard Peck
Jun 12 '17 at 7:03
Worked for us, thank you.
– Richard Peck
Jun 12 '17 at 7:03
add a comment |
On the same issue, I found another workaround that can be applied at model level, without edit any initializer:
class PaperclipModel < ActiveRecord::Base
has_attached_file :attachment, { validate_media_type: false }
validates_attachment :attachment, {
# tweak as desired
content_type: { content_type: ["text/csv", "text/plain", Paperclip::ContentTypeDetector::SENSIBLE_DEFAULT] }
}
end
Basically, this skip media_type
and content_type
validations to avoid spoofed error on PaperclipModel
attachment. For more details see here.
add a comment |
On the same issue, I found another workaround that can be applied at model level, without edit any initializer:
class PaperclipModel < ActiveRecord::Base
has_attached_file :attachment, { validate_media_type: false }
validates_attachment :attachment, {
# tweak as desired
content_type: { content_type: ["text/csv", "text/plain", Paperclip::ContentTypeDetector::SENSIBLE_DEFAULT] }
}
end
Basically, this skip media_type
and content_type
validations to avoid spoofed error on PaperclipModel
attachment. For more details see here.
add a comment |
On the same issue, I found another workaround that can be applied at model level, without edit any initializer:
class PaperclipModel < ActiveRecord::Base
has_attached_file :attachment, { validate_media_type: false }
validates_attachment :attachment, {
# tweak as desired
content_type: { content_type: ["text/csv", "text/plain", Paperclip::ContentTypeDetector::SENSIBLE_DEFAULT] }
}
end
Basically, this skip media_type
and content_type
validations to avoid spoofed error on PaperclipModel
attachment. For more details see here.
On the same issue, I found another workaround that can be applied at model level, without edit any initializer:
class PaperclipModel < ActiveRecord::Base
has_attached_file :attachment, { validate_media_type: false }
validates_attachment :attachment, {
# tweak as desired
content_type: { content_type: ["text/csv", "text/plain", Paperclip::ContentTypeDetector::SENSIBLE_DEFAULT] }
}
end
Basically, this skip media_type
and content_type
validations to avoid spoofed error on PaperclipModel
attachment. For more details see here.
answered Nov 21 '18 at 17:52


Daniel BatallaDaniel Batalla
62511022
62511022
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f21912322%2fruby-on-rails-paperclip-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Apparently, PaperClip thinks that this is not a valid jpeg file, respectively couldn't determine the real file type using the
file
command. Have you tried different file types (png, gif)?– pduersteler
Feb 20 '14 at 15:34
Yes, I tried a png just now--same error.
– Rachel9494
Feb 20 '14 at 15:51