The upload of category images gets stuck at 0%. The same image uploaded inside a topic works fine. I uploaded some category images last week. The only thing I changed since then was updating to 2.8.0.beta11 (cbf99f48d8) this morning.
3 Likes
I think this might be related to the data center outage described here:
(I’ve had the same problem)
1 Like
I thought about that, but I imagined the image processing for categories to be local.
My guess is that the outage is causing backend processes that do talk to the discourse servers (such as the avatar service and the version check) to take much longer than normal before timing out. This causes other tasks that are local-only to be delayed.
2 Likes
The same thing happens to me, the only error that I have the console is this:
application-e3e2b65734231ede09b9034749bc29d929feb55a4b1dd4f0e9cab9440c643ac4.js:sourcemap:1 Uncaught TypeError: e._perFileData is not a function
at application-e3e2b65734231ede09b9034749bc29d929feb55a4b1dd4f0e9cab9440c643ac4.js:sourcemap:1:622332
at Array.forEach (<anonymous>)
at Object.onBeforeUpload (application-e3e2b65734231ede09b9034749bc29d929feb55a4b1dd4f0e9cab9440c643ac4.js:sourcemap:1:622286)
at H.upload (vendor-96a5eaa8d436066b954c21ae5afb7f504310945c679465a2f1ba46b429a95edf.js:sourcemap:77:151420)
at vendor-96a5eaa8d436066b954c21ae5afb7f504310945c679465a2f1ba46b429a95edf.js:sourcemap:77:154902
I rebuilt several times and even tried in Safe mode thinking it might be a plugin or theme
2 Likes
Oddly I am getting a very similar error on attempting to upload a Backup file of around 50MB. This is on a totally clean, new Digital Ocean-based image that I just finished setting up, running 2.8.0.beta11 (232f840b60). I increased all file size limits within the admin settings. Error log shows:
TypeError: e._perFileData is not a function
at https://xxxx.xxxx.com/assets/application-e3e2b65734231ede09b9034749bc29d929feb55a4b1dd4f0e9cab9440c643ac4.js:1:622332
at Array.forEach (<anonymous>)
at Object.onBeforeUpload (https://xxxx.xxxx.com/assets/application-e3e2b65734231ede09b9034749bc29d929feb55a4b1dd4f0e9cab9440c643ac4.js:1:622286)
at H.upload (https://xxxx.xxxx.com/assets/vendor-96a5eaa8d436066b954c21ae5afb7f504310945c679465a2f1ba46b429a95edf.js:77:151420)
at https://xxxx.xxxx.com/assets/vendor-96a5eaa8d436066b954c21ae5afb7f504310945c679465a2f1ba46b429a95edf.js:77:154902
Then a few minutes later, after following these instructions to change max attachment size (because I don’t know what else it could be), I get:
onBeforeUpload/<@https://xxxx.xxxx.com/assets/application-e3e2b65734231ede09b9034749bc29d929feb55a4b1dd4f0e9cab9440c643ac4.js:1:622332
onBeforeUpload@https://xxxx.xxxx.com/assets/application-e3e2b65734231ede09b9034749bc29d929feb55a4b1dd4f0e9cab9440c643ac4.js:1:622286
upload@https://xxxx.xxxx.com/assets/vendor-96a5eaa8d436066b954c21ae5afb7f504310945c679465a2f1ba46b429a95edf.js:77:151420
Q/this.scheduledAutoProceed<@https://xxxx.xxxx.com/assets/vendor-96a5eaa8d436066b954c21ae5afb7f504310945c679465a2f1ba46b429a95edf.js:77:154902
Tried in 3 separate browsers. I’ve redacted the specific subdomain, but I wouldn’t think that should matter.
I’m only posting here because it’s literally the only other mention I can find of these errors, and it’s recent so I thought it might be related. Apologies if it’s OT.
2 Likes
I am getting the same error on my site and it is really messing with profile images. Looking for a quick resolution to this since we have a huge exodus of users coming over from a just announced shutdown of a decades-old forum.
2 Likes
Oh dang. I presume it’s happening in uploads, but where?
Seems like maybe a bug crept into the latest beta?
Perhaps. Uploads to threads and posts seem to work, just not profiles or categories. The Discourse team is very good about closing bugs that are very experience halting like this so I strongly expect it will get fixed in the day or two.
2 Likes
I just updated to a commit they did a half hour or so ago, and it seems fixed 
4 Likes
Same here… upgraded and everything works fine now.
2 Likes
Dang, but these changes aren’t in the latest beta it seems, since it’s saying I’m up to date. So I guess I have to switch to nightly? Is there any precedent for major bugs justifying a hot fix release to main channel(s)? If so, does this not qualify?
Edit: I rebuilt the container anyway (git pull said no update before that) and hey, it works now! 
1 Like
Worked for me just now for Backup upload, at least. 
1 Like
Help plz. How can i apply this code for production ?
1 Like
Visit /admin/upgrade on your site and update to the latest from there
4 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.