After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 689994 - Upload extension problem
Upload extension problem
Status: RESOLVED FIXED
Product: website
Classification: Infrastructure
Component: extensions.gnome.org
current
Other Linux
: Normal normal
: ---
Assigned To: Shell extensions maintainer(s)
Shell extensions maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-12-10 17:39 UTC by stefano
Modified: 2017-01-21 20:58 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
extension pack that I was unable to upload (18.64 KB, application/zip)
2012-12-11 09:36 UTC, stefano 		Details

Description stefano 2012-12-10 17:39:04 UTC 
"500 - Internal Server Error" after extensions submit.

Step to reproduce:
1. Click on "Add yours" link
2. Choose zip to submit, click on checkbox and click on "Upload extension"

webserver shows a "500 - Internal Server Error

The server had an error when you wanted to access this page. This site is beta, so it may happen sometimes. Please let us know what you did so we can fix it!"

The user appears not logged.
Comment 1 stefano 2012-12-11 09:36:58 UTC 
Created attachment 231246 [details]
extension pack that I was unable to upload
Comment 2 Jasper St. Pierre (not reading bugmail) 2012-12-11 09:42:38 UTC 
It's probably choking on the "version" field, as versions are usually integers.
Comment 3 stefano 2012-12-11 09:50:08 UTC 
I have changed metadata.json file:

"version": "0.8",
in
"version": "22",

with the same effect. Previously I have always used names like 0.x version without problems in the "version" field.
Comment 4 stefano 2012-12-12 18:24:52 UTC 
Any news about this problem?
Comment 5 Jasper St. Pierre (not reading bugmail) 2013-04-14 20:59:59 UTC 
Have you tried again recently? I fixed an issue related to this recently.
Comment 6 stefano 2013-04-14 23:45:23 UTC 
Yes, I have always the same result. If you want to check yourself, you can try with the extension pack attached to this thread.
Comment 7 stefano 2013-06-24 13:37:24 UTC 
I am trying to update this extension to Gnome 3.8, but wthout success.
Any news about the resolution of this bug?
Comment 8 Yuri Konotopov 2017-01-21 20:58:37 UTC 
This should be fixed now.
The problem was laid in version 16 of your extension - zip archive of this version was broken. I remove it.