Steps:
- Navigate to a doc’s page
- click the edit this page icon
- Click for and edit and logon
- A 405 Method not allowed or after that a 400 Badrequest is reported
1 Like
Which doc are you talk about?
Can you please give a link?
I saw that the Server manual already moved to the new location. Might be tat some links are not changed yet.
p.s.
Did you do a “Edit in your fork”? It will fork the docs into your space on pagure and you can edit then and send a pull request.
However, I imagine that there is an issue if you are a newer user and not have logged in before.
What do you get when accessing pagure.io directly?
I made a ticket on pagure, to check if you need a group membership to use the infrastructure:
I can at least partly replicate this:
- Navigate to that page
- Click “Fork and edit”
- Enter credentials at login screen, then I get an error message like yours.
But then, if I go back to the original page, I’m logged in and I can see an “Edit in your fork” button.
However, I already had an existing fork of that repo, so this isn’t a perfect replication.
What happens if you open the docs page again after the (apparently) failed login attempt?
I believe you don’t. I’ve contributed to this repo (fedora-docs/quick-docs) before without being a member of a group.
1 Like
You do not need any groups to login to pagure.io. Just an account.
The login issues above are something else. 
We had a large network outage yesterday, it might be related to that? Are you able to login ok now, or do you get the same error? Can you try a private window and/or another browser? You are able to login to https://accounts.fedoraproject.org right? Anything else on the error page(s) aside the error code?
1 Like
Ah ok, i hope @theking2 will try again today and give us feedback here.
I could not recreate the error. From my site it worked. So that is why believed they need to be a member of an additional group.
I forgot to check here Fedora Infrastructure Status
Thx Kevin.
@theking2, ignoring an outage, [1] you might be experiencing pagure.io/fedora-infrastructure/issue/12294#comment-977820, because it can occur when already authenticated. I frequently see it (when authenticating, albeit). [2]
Yes, i think it is a session cooky which is cached. Might be good from time to time to remove the cookies in the browser.
If it is on pagure just to try to remove the domain pagure.io in the browser settings (Firefox=manage cookies and site data, searching for the domain, mark it and remove) then try again, it will write a new session cookie for this specific domain.
If it not works, with the specific domain, then also delete the cookies for accounts.fedoraproject.org.
See my post. the link is inth
See the link in my post.
@theking2, the iconless <button class="btn btn-sm btn-secondary fork_project_btn"> correctly directs me to https://pagure.io/fork/rokejulianlockhart/fedora-docs/quick-docs/edit/main/f/modules/ROOT/pages/screenrecorder-apps-comparison.adoc, [1] if that’s what you’re referring to: