![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 6 weeks ago
Closed 5 weeks ago
#8282 closed defect (bug) (worksforme)
User profile fields not saving correctly on update
| Reported by: | modi2918 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Profiles | Keywords: | |
| Cc: |
Description
Steps to Reproduce
Go to WordPress.org → Profile → Edit Profile → Contributions tab.
Update a field (for example, Contributor Teams).
Click Update Profile.
Expected Behavior
The updated field is saved successfully and persists after reloading the page.
Actual Behavior
The field reverts to its previous value after the page reloads, or an error is displayed during the update process.
Environment
Browser: Brave
Attachments (2)
Change History (10)
#2
@
6 weeks ago
This may be the result of Akismet doing its alchemy stuff. If that's the case, then @otto42 or @dd32 may be able to shine more light.
#3
@
6 weeks ago
I can't duplicate. I don't think this is akismet.
I do get a "Warning: Leave Site? Changes you made might not be saved" type alert upon clicking update though.
#4
@
6 weeks ago
Environment
Browser: Brave
Browser: Chrome
Steps to Reproduce
Go to the Contributor Teams selection screen.
Select one or more Contributor Teams.
Click Save.
Actual Result
After clicking Save, a browser warning appears:
Warning: Leave Site? Changes you made might not be saved.
#5
@
6 weeks ago
@modi2918 Are you reporting the Unchanged edits may be lost warning, or that the fields don't save?
#6
@
6 weeks ago
When I click the Save button, a browser warning appears:
"Warning: Leave Site? Changes you made might not be saved."
Thanks for the report. I haven't been able to reproduce this - on the current site, updating Contributor Teams (and Sponsored/Hours) on the Contributions tab saves and persists correctly, with no error. Could you share: (1) the exact error text or a screenshot of it, (2) whether it still happens in another browser or with Brave Shields down, (3) the exact field and steps, and (4) any errors in the browser console (F12) when you click Update Profile? That'll help pin down whether it's environment-specific.