AMO view source not allowed Fx 52esr (Resolved)

[LewS]

Trying to use the view source option in the version information section
of any add-on's AMO home page now returns:

"Oops! Not allowed.
You tried to do something that you weren't allowed to."

Is this part of the ongoing removal of all features or just a temporary
glitch?

Edited title 4/25 to show resolved.

[Mo_D]

It's not just you.

https://github.com/mozilla/addons-server/issues/5135

[RobertJ]

.
I never used that but your observation is correct. I even tried it logged in as a dev and nothing.

Did it ever work?

.

[nohamelin]

As a dev, I can inspect the source code of my add-ons but not others.

[RobertJ]

As a dev, I can inspect the source code of my add-ons but not others.

You are correct. I was able to inspect the source code of one of my add-ons; that is something I never used.

.

[LewS]

It did work in the past. I used it a lot on 45esr checking for
e10s multiprocess flag on many different addons; can't think
of any reason it would be there if it didn't work for everyone.

[RobertJ]

It did work in the past. I used it a lot on 45esr checking for
e10s multiprocess flag on many different addons; can't think
of any reason it would be there if it didn't work for everyone.

No clue but I can view my add-ons but no others.

.

[Mo_D]

If you click on the link I posted above, you'll see the server is temporarily disabled to the public, and will be restored, but there is no date set yet for restoration.

[RobertJ]

If you click on the link I posted above, you'll see the server is temporarily disabled to the public, and will be restored, but there is no date set yet for restoration.

Right you are! I missed that

.

[Aris]

Anyone tried to view source code being logged into AMO, but not being an AMO editor or developer?

Although I can see and correctly access only source code links of my add-ons, accessing works for me for other add-ons too, if I switch to their file number/id.
e.g. TabMixPlus https://addons.mozilla.org/en-us/firefo ... se/566309/
Not sure, if this is possible because I'm an AMO editor or only because I'm logged into AMO.

[LewS]

@ Mo_D, I did look at the link you posted (thanks, it explained the
problem) but my response was more about the way it was blocked.

The "Oops" message was not only mysterious, it was misleading:
there was no "Oops"!