https://bugzilla.wikimedia.org/show_bug.cgi?id=72324
--- Comment #9 from Daren Welsh <[email protected]> --- I was reading this: https://www.mediawiki.org/wiki/Manual:$wgMaxImageArea Thank you for modifying it, though I think it could use some more detail. Can you provide an example of a case where you want a large (image) file uploaded where it cannot be rendered/scaled? 1. I don't agree that you should allow a user to upload an image of a size that will not be able to be scaled by whatever tool is being used because the default action of the upload page is to take you to the file page with a scaled version of that image. So that process just breaks in the case of a large image. The upload page should stop the upload and report that the image size is in excess of the $wgMaxImageArea value which will result in memory issues when the image is automatically scaled. Maybe there should be an option or separate special page for large images where you do not require scaled versions. 2. I find the following scenario interesting: I increase the value of $wgMaxImageArea (for example, to 100,000,000) but leave $wgMemoryLimit to the default value. Then I go to the upload page to upload a new version of an image that is very large but under the new limit of $wgMaxImageArea (and $wgMaxUploadSize). After selecting the file, it creates the thumbnail successfully. But when I click on the upload button, I get a blank page. Now the only way to fix that page is to increase $wgMemoryLimit in LocalSettings (at least temporarily for that one page load). It seems like there should be some mechanism to relate these two values together. Remember, the reason I posted this report and am investigating the details is that one of our users uploaded an image with no warning or push-back and was met with two broken pages: the file page itself and a page that displayed a thumbnail of that image. It seems like there should be something in place to "more-gracefully fail". -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
