Help talk:How can I update my previously uploaded edition?: Difference between revisions

From ChoralWiki
Jump to navigation Jump to search
(problem making a picture display)
 
(Reply to Bob, complaining about a bug)
Line 1: Line 1:
I seem to be having a problem getting an image to display on this page. I want to use it to make it easier for users to follow the written instructions but I don't seem to be able to get it to appear - just a link appears. The image file has been uploaded and exists here: [[Image:Properties box.JPG]]. [[User:Bobnotts|Bobnotts]] 05:27, 10 January 2007 (PST)
I seem to be having a problem getting an image to display on this page. I want to use it to make it easier for users to follow the written instructions but I don't seem to be able to get it to appear - just a link appears. The image file has been uploaded and exists here: [[Image:Properties box.jpg]]. [[User:Bobnotts|Bobnotts]] 05:27, 10 January 2007 (PST)
 
:The problem is exactly the same as has been mentioned several times over the last weeks: for some reason, uploaded files are systematically tagged with the MIME type "text/plain", which is incorrect most of the cases (for instance, it should be "application/pdf" for PDF files, "application/zip" for zipped archives, and, in your case, "image/jpeg"). So the system doesn't want to display your image because it relies on the MIME type, not the file extension, to determine what file it is, and in this case it just puts a link to it (using an <a> HTML tag, not <img> as it should). In addition, when you follow the link, there is apparently some template telling that plain text files are nasty and can contain “malicious code” (which is rather stupid, I think: plain text files are only what their name tells they are, plain text, and do not contain any more “malicious code” than PDF or image files -- probably even less, nowadays, since it's probably possible to embed plugins or code snippets inside PDF files, that would be executed when the PDF file is displayed; I have no special knowledge about it though, only guessing, but it seems to be Adobe's  CEtrend in the latest PDF developments to enable all sort of things inside a PDF).
 
:I don't think this has anything to do with the way users upload files, and the fault must lie with the Wiki software on the server side. I believe only admins can do anything about it, since some settings have to be changed (I know nothing of Wiki software, though, but this seems the most probable since it is connected in some sense with security issues).
 
:Incidentally, the file name is "Image:Properties_box.jpg" with a lowercase 'jpg', not uppercase like you wrote; I took the liberty of changing it above because else it makes the problem even harder to understand (since "Image:Properties_box.JPG" doesn't actually exist, in spite of your claim ;-). -- [[User:R|Arthur]] 2007-02-21 19:14 CET (18:14 UTC)

Revision as of 20:00, 21 February 2007

I seem to be having a problem getting an image to display on this page. I want to use it to make it easier for users to follow the written instructions but I don't seem to be able to get it to appear - just a link appears. The image file has been uploaded and exists here: Properties box.jpg. Bobnotts 05:27, 10 January 2007 (PST)

The problem is exactly the same as has been mentioned several times over the last weeks: for some reason, uploaded files are systematically tagged with the MIME type "text/plain", which is incorrect most of the cases (for instance, it should be "application/pdf" for PDF files, "application/zip" for zipped archives, and, in your case, "image/jpeg"). So the system doesn't want to display your image because it relies on the MIME type, not the file extension, to determine what file it is, and in this case it just puts a link to it (using an <a> HTML tag, not <img> as it should). In addition, when you follow the link, there is apparently some template telling that plain text files are nasty and can contain “malicious code” (which is rather stupid, I think: plain text files are only what their name tells they are, plain text, and do not contain any more “malicious code” than PDF or image files -- probably even less, nowadays, since it's probably possible to embed plugins or code snippets inside PDF files, that would be executed when the PDF file is displayed; I have no special knowledge about it though, only guessing, but it seems to be Adobe's CEtrend in the latest PDF developments to enable all sort of things inside a PDF).
I don't think this has anything to do with the way users upload files, and the fault must lie with the Wiki software on the server side. I believe only admins can do anything about it, since some settings have to be changed (I know nothing of Wiki software, though, but this seems the most probable since it is connected in some sense with security issues).
Incidentally, the file name is "Image:Properties_box.jpg" with a lowercase 'jpg', not uppercase like you wrote; I took the liberty of changing it above because else it makes the problem even harder to understand (since "Image:Properties_box.JPG" doesn't actually exist, in spite of your claim ;-). -- Arthur 2007-02-21 19:14 CET (18:14 UTC)