Make WordPress Core

Opened 3 years ago

Last modified 3 months ago

#59025 new defect (bug)

Incorrect error message when changing the screen options after erasing personal data

Reported by: harsh175 Owned by:
Priority: normal Milestone: Awaiting Review
Component: Privacy Version:
Severity: normal Keywords: has-patch
Cc: Focuses: administration

Description

When an administrator adds a username or email for the purpose of erasing personal data and clicks on the remove request option after completing the process, the data is removed. However, at that point, if the administrator clicks the screen option, unchecks the next step, and then clicks the apply button, an error message saying that error message failed to delete.

​https://www.awesomescreenshot.com/video/19806917?key=ca89e6f131318e651ccc67b126de39ba

Attachments (2)

Screenshot from 2023-08-14 12-24-21.png​ (30.1 KB ) - added by ivanzhuck 3 years ago.
59025.diff​ (1.3 KB ) - added by ivanzhuck 3 years ago.

Download all attachments as: .zip

Change History (5)

#1 @NekoJonez
3 years ago

  • Component General → Privacy
  • Summary Error Message Issue In Screen Option In Erase Personal Data → Incorrect error message when changing the screen options after erasing personal data

I changed the title of your ticket, so it describes the issue better. I also tagged the right team to look into this.

This ticket was mentioned in ​PR #5005 on ​WordPress/wordpress-develop by ​@ivanzhuck.


3 years ago
#2

  • Keywords has-patch added; needs-patch removed

Pressing the "Apply" button reload the page with the same URL, so the delete operation calls twice. I've added a message for cases like this. The message says "request already deleted" when a request removing repeated.

Trac ticket: [](https://core.trac.wordpress.org/ticket/59025)

@ivanzhuck
3 years ago

​@masteradhoc commented on ​PR #5005:


3 months ago
#3

Hey @IvanZhuck
Sorry i know a lot of time has passed since your PR. I took over the privacy component and am checking various open tickets currently. Would you be able to update your branch and fix the merge conflicts so we can give it a fresh test?

Thanks

Note: See TracTickets for help on using tickets.