summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJuuso Lapinlampi <wub@partyvan.eu>2015-10-27 15:57:13 +0100
committerJuuso Lapinlampi <wub@partyvan.eu>2015-10-27 15:57:13 +0100
commitb8259ef32c861e483d6c6beef4d5f8f2dc475bdf (patch)
tree916ff6bbb83b89567adfeb7ad4df920da6db287e
parent377a3e53bdb71df0ccb8a1288eb2088d508adee1 (diff)
Revert default max-file-size from 120MiB to 10MiB
ewhal@ didn't understand how changing the maximum file size works, so he edited the JavaScript code directly to set the default to his desired 120MiB. For all clones, this may not be viable and it's not a sane default in my opinion. This doesn't change the fact that the maximum file size remains to be what it's configured in the configuration (Gruntfile.js). This bug was introduced in commit ec0154b, and potentially others. Vague OK from ewhal@ many weeks ago.
-rw-r--r--js/pomf.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/js/pomf.js b/js/pomf.js
index 0d71dbf..baaac46 100644
--- a/js/pomf.js
+++ b/js/pomf.js
@@ -59,7 +59,7 @@ $(function() {
});
var MAX_SIZE = (function(node) {
- var max = node.attr('data-max-size') || '120MiB';
+ var max = node.attr('data-max-size') || '10MiB';
var num = parseInt(/([0-9,]+).*/.exec(max)[1].replace(',', ''), 10);
var unit = /(?:([KMGTPEZY])(i)?B|([BKMGTPEZY]))/.exec(max) || ['B', '', ''];