-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CAS users unable to change email address #6
Comments
Someone on our team pointed out that this is actually a fairly important issue for us because setting one's email address allows for communication via user talk pages and watched pages. If you don't have the time to fix this issue, then any clues for this issue would be very much appreciated. : ) Thanks. |
Hi @sudoman, Yes, I see this on our wiki. This is a feature I've never attempted to use before, but when I try it now I encountered an error: "The page isn’t redirecting properly". I'm afraid that I neither have time to work on this now nor any suggestions for where to start. Please let us know if you find something. Jeff |
This patch to mediawiki is a workaround that essentially acts like $wgRequirePasswordforEmailChange = false;, which is an option that was removed in 1.27.
|
I hope someone can make a proper fix. I might try someday. The area of code that patch is on seems like a good area to look at. Here's a dump of my notes when investigating this issue
|
Hello,
Thanks for maintaining this extension. I appreciate the work you've put into this.
I have noticed an issue when using this extension with MW 1.27 on both of our wikis that make use of CASAuth. Users are unable to change their email address, due to a redirect loop. On other sites that we manage this is sometimes due to a failure to authenticate or lack of user permissions on the client side. The infinite redirect loop is such:
Do you see this on your own wiki?
This isn't a super important issue for us, so no pressure. Thanks again for your work on this extension.
Thanks,
Andrew
The text was updated successfully, but these errors were encountered: