403 when trying to delete Approved extension #103

New Issue

Dalai Felinto · 2024-05-02T12:16:36+02:00

Dalai Felinto commented

2024-05-02 12:16:36 +02:00

If you login as dfelinto on the staging site you get:

Good: https://staging.extensions.blender.org/add-ons/border-buddy/delete/
403: https://staging.extensions.blender.org/themes/nice-name/delete/

If you login as dfelinto on the staging site you get: Good: https://staging.extensions.blender.org/add-ons/border-buddy/delete/ 403: https://staging.extensions.blender.org/themes/nice-name/delete/

Dalai Felinto commented

2024-05-02 12:42:24 +02:00

For the web-team:

I found a sentry entry which is likely related to when I was trying/deleting the other extensions:

https://blender-org.sentry.io/issues/5291955701/

For the records I first deleted all the files I owned. And then noticed that that didn't delete the versions/extensions themselves. And because there is no way to list them on the admin UI by user, I tried to delete them from the site itself.

**For the web-team:** I found a sentry entry which is likely related to when I was trying/deleting the other extensions: https://blender-org.sentry.io/issues/5291955701/ For the records I first deleted all the files I owned. And then noticed that that didn't delete the versions/extensions themselves. And because there is no way to list them on the admin UI by user, I tried to delete them from the site itself.

Oleg-Komarov commented

2024-05-02 13:35:46 +02:00

What was the intention? Fully delete a listed extension as an admin?
I think, in most cases we would expect to use "disabled by staff". We can also decide if we want to support deletion of extensions that were disabled/unlisted.

What was the intention? Fully delete a listed extension as an admin? I think, in most cases we would expect to use "disabled by staff". We can also decide if we want to support deletion of extensions that were disabled/unlisted.

Dalai Felinto commented

2024-05-02 14:02:34 +02:00

In this particular case I was just trying to delete so I could re-upload extensions without creating new packages.

Either way getting a 403 in some cases seems strange no?

But also the real bug may simply be that deleting files is not deleting the associated Extensions.

In this particular case I was just trying to delete so I could re-upload extensions without creating new packages. Either way getting a 403 in some cases seems strange no? But also the real bug may simply be that deleting files is not deleting the associated Extensions.

Anna Sirota referenced this issue from a commit

2024-05-09 18:11:41 +02:00

Close #103: don't show Delete btn when deletion impossible

Anna Sirota closed this issue

2024-05-09 18:11:41 +02:00

Sign in to join this conversation.