Closed
Bug 276255
Opened 20 years ago
Closed 20 years ago
Developers page does not work anymore
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
FIXED
1.1
People
(Reporter: jaap, Unassigned)
References
()
Details
If I go to the developers page https://addons.update.mozilla.org/developers/ I get a 403 Forbidden page
Comment 1•20 years ago
|
||
Sounds right, this is intentional.
Assignee: psychoticwolf → nobody
OS: Linux → All
Hardware: PC → All
Comment 2•20 years ago
|
||
*** Bug 276349 has been marked as a duplicate of this bug. ***
| Reporter | ||
Comment 3•20 years ago
|
||
would be good to add a page at that location that the developer feature is taken offline and is expected to be online again at .....
Comment 4•20 years ago
|
||
(In reply to comment #1) > Sounds right, this is intentional. what's happened? too many submissions? Maybe instead of a 403 error some kind of short update or explanation might be nice :)
Comment 5•20 years ago
|
||
(In reply to comment #1) > Sounds right, this is intentional. I would like to know more about that : the update-beta.m.o worked nice. Where can one find an explanation, or a plan for the future ? I like the idea to administrate my extensions' pages and to update versions (otherwise I dunno how it is done : waiting for a long time since I send the bug of a new version for EditCSS... still waiting). Does someone know something ? thx :o)
Comment 6•20 years ago
|
||
(In reply to comment #5) > I would like to know more about that : the update-beta.m.o worked nice. > Where can one find an explanation, or a plan for the future ? I'm not part of the staff, but my understanding is that when the update.m.o site was upgraded to the new software version, some things were discovered that still need work. When those features are finished, the developer section will be enabled - hopefully in the next few weeks (personal guess).
*** Bug 276862 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: 1.0 → 1.1
| Reporter | ||
Comment 8•20 years ago
|
||
Does changing the target milestone to 1.1 mean that this one does not get solved before march? (I.e. when FF 1.1 gets released). That would be a pity, because I'd like to update my extensions and themes. Also the fact that with assigned to it says "Nobody's working on this, feel free to take it" suprises me.
Developer Control Panel now online again! [However, no email was sent to registered authors to inform them of this }:-/ It's not like they don't have our details, after all---I received an email (the day *after* the release of Fx1.0.3) informing me that changes in the app may break my extension.] Anyway, it all seems to work well, except for one thing. When viewing the overview of an extension (the page where you can change the Developer's Comments) there's a link to edit the main description of the extension. Unfortunately, access is denied! Is this deliberate behaviour? What is the rationale? How do we go about getting this description changed---do we still have to file a bug like we used to?
Comment 10•20 years ago
|
||
That's bug 290633.
Comment 11•20 years ago
|
||
The developers section is now back live... any other issues relating to this should probably be filed in a new bug.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•