Make WordPress Core

Opened 15 years ago

Closed 8 months ago

#15801 closed defect (bug) (fixed)

Network Admin: Deactivated / Deleted inconsistency

Reported by: kawauso's profile kawauso Owned by: johnbillion's profile johnbillion
Milestone: 6.9 Priority: normal
Severity: normal Version: 3.1
Component: Networks and Sites Keywords: has-patch needs-user-docs
Focuses: multisite Cc:

Description

Under the Sites screen, there are distinct inline links for Deactivate and Delete. However, when a site is deactivated, it is referred to as deleted in:

  • Sites screen inline status
  • Edit Site screen attributes section
  • Error page for non-admins visiting the site

Attachments (1)

deactivated.diff (629 bytes) - added by wonderboymusic 13 years ago.

Download all attachments as: .zip

Change History (46)

#1 @kawauso
15 years ago

  • Severity changed from minor to normal

Leaving severity alone

#2 @nacin
15 years ago

  • Component changed from UI to Network Admin
  • Milestone changed from Awaiting Review to 3.1

#3 @PeteMall
15 years ago

  • Owner set to PeteMall
  • Status changed from new to assigned

#4 @ryan_b
15 years ago

  • Cc ryan_b added

#5 @ryan_b
15 years ago

From what I can tell, the delete link removes the site from the db, deactivate leaves it in the db and sets a flag called "deleted", so my question is if the flag is called deleted is the status being listed as "Deleted" the desired effect?

#6 @ryan_b
15 years ago

  • Keywords dev-feedback added

#7 @ryan
15 years ago

  • Milestone changed from 3.1 to Future Release

#8 @scribu
15 years ago

Related: #17164

#9 @novasource
15 years ago

  • Cc aren@… added

#10 @wonderboymusic
13 years ago

  • Keywords has-patch added; dev-feedback removed
  • Milestone changed from Future Release to 3.5

Deactivated is the status for the Delete flag, Delete is an action that removes the site. Patched.

#11 @nacin
13 years ago

  • Milestone changed from 3.5 to Future Release

There's a lot of inconsistency here. Moving out of 3.5 for further review.

#12 @knutsp
13 years ago

  • Cc knut@… added

#13 @wonderboymusic
13 years ago

  • Milestone changed from Future Release to 3.6

#14 @DrewAPicture
13 years ago

  • Component changed from Network Admin to Text Changes

deactivated.diff looks good to me. It's a shame the flag is called 'deleted' but I'd assume changing it isn't an option.

#15 @wonderboymusic
13 years ago

  • Milestone changed from 3.6 to Future Release

#16 @wonderboymusic
13 years ago

  • Keywords easy-fix added
  • Milestone changed from Future Release to 3.7

#17 @martythornley
13 years ago

It seems there is still an inconsistency in that from a user's POV, they go through the process of saying to 'delete' their site, which is why it now shows up as 'deleted' but from the super admin POV it is really deactivated.

So... we could either change the "delete" link from the Super Admin level and rename it to "remove" or "permanently delete", then change the "deactivate" link back to "delete". This would make user and super admin "delete" functions act the same. "Delete" would mean temporary, like moving to the trash. While "Remove" or "Permanently Delete" would remove it altogether.

#18 @SergeyBiryukov
13 years ago

  • Keywords easy-fix removed

"easy-fix" is a tag for attracting new contributors to tickets that don't have a patch yet.

See the IRC discussion: part 1, part 2.

#19 @martythornley
13 years ago

I played with some of the wording in those links and some seem to work better than others.

It seems from the user level, they go through the delete site process and to them the site is gone. But really to the Super Admin it is "marked for deletion" which seems an even better label to me than "deactivated".

As a Super Admin, when we deactivate and reactivate a site, it is like trash/untrash or again, marking for possible deletion.

Once sites are "marked for deletion" or in the trash, we can use the "Delete" link to do it permanently.

Changing the wording of the links makes the super admin process make more sense, but it starts messing with the flags and would be inconsistent when looking at the code.

However, the get_blog_status and update_blog_status are only called a couple times in core and it would seem to not too difficult to run a quick update that says if the blog status is called 'deleted' update that to 'trash'. Or whatever the decided wording is. Or am I missing other areas that rely on those flags?

Another, farther reaching idea...

Could we somehow change the blog status to an array that can be whatever we want? That way a blog could be multiple things at once - A blog could be 'Mature', "Spam', and 'Trash" all at once? Or any number of custom status that a plugin might build like "Awesome", "Promoted", etc...

#20 @nacin
12 years ago

  • Component changed from Text Changes to Multisite
  • Milestone changed from 3.7 to 3.8
  • Owner changed from PeteMall to nacin

#21 @jeremyfelt
12 years ago

The behavior makes sense in that a user (not a superadmin) is flagging or marking their site for deletion, not deleting it directly. If the language to the user was updated to better convey this, that might be all that is needed.

The post delete screen of Your site will not be deleted until this link is clicked. could become Your site will not be flagged for deletion until this link is clicked.

An explanation about the network administrator having to complete the process could be added to the delete email.

The text for a non logged-in user *could* stay the same - This user has elected to delete their account and the content is no longer available. or could be changed to This site has been marked for deletion and the content is no longer available. It is the site being deleted, not necessarily the user's account.

And finally, the Deleted marker in the network admin's list table could be left alone or something else could be done to convey that further action is needed to satisfy the user's wishes.

@nacin - do you have thoughts on approach with this? Not sure if it really is something we can squeeze into 3.8.

#22 @nacin
12 years ago

  • Milestone changed from 3.8 to Future Release

@nacin - do you have thoughts on approach with this? Not sure if it really is something we can squeeze into 3.8.

Not really. Let's play a long game here. What's the best approach? Let's figure it out and do it, versus trying to squeeze things into a release over a confusing label.

#23 @jeremyfelt
12 years ago

  • Component changed from Multisite to Networks and Sites
  • Focuses multisite added

#24 @jeremyfelt
11 years ago

#29459 was marked as a duplicate.

#25 @jeremyfelt
11 years ago

  • Keywords needs-patch dev-feedback added; has-patch removed

#26 @jeremyfelt
11 years ago

  • Milestone changed from Future Release to 4.4

This ticket was mentioned in Slack in #core by sergey. View the logs.


10 years ago

#28 @SergeyBiryukov
10 years ago

  • Owner changed from nacin to jeremyfelt

#29 @jeremyfelt
10 years ago

  • Milestone changed from 4.4 to Future Release
  • Owner jeremyfelt deleted

This ticket was mentioned in Slack in #core-multisite by flixos90. View the logs.


9 years ago

#31 @SergeyBiryukov
7 years ago

#44974 was marked as a duplicate.

#32 @SergeyBiryukov
7 years ago

#47275 was marked as a duplicate.

#33 @sebastienserre
7 years ago

Hello,

This ticket seems to be abandoned... but I think there's a really problem with this "deleted label" io a "deactivated" one.

I'm quiet new in Core contribution so, I d'on't know exactly what to do to make this ticket closed :-/

This ticket was mentioned in PR #4476 on WordPress/wordpress-develop by @ideag.


3 years ago
#34

  • Keywords has-patch added; needs-patch removed

This PR changes some of the strings, to consistently refer to sites in multisite as 'Deactivated' when they are marked as such. Previously there were cases where they were being called as 'Deleted', while there is a separate action to 'Delete' a site which actually fully removes the site from the system.

EDIT: Trac ticket: https://core.trac.wordpress.org/ticket/15801

#35 @jorbin
3 years ago

#56076 was marked as a duplicate.

#36 @ideag
3 years ago

#44515 was marked as a duplicate.

#37 @jorbin
3 years ago

  • Keywords needs-patch added; has-patch removed

Looking at @jeremyfelt's comment, I think we should also fix up the other strings as a part of this so that everything is clear and we may need to add some additional code so that a site is considered flagged for deletion along with it being deactivated. That will help super admins know that a user requested the site be deleted vs that they deactivated it.

#38 @sabernhardt
22 months ago

#61142 was marked as a duplicate.

This ticket was mentioned in PR #8594 on WordPress/wordpress-develop by @sukhendu2002.


11 months ago
#39

  • Keywords has-patch added; needs-patch removed

The changes update the terminology from "Deleted" to "Flagged for Deletion" across the Network Admin interface to better communicate the actual status of deactivated sites.

Trac ticket: https://core.trac.wordpress.org/ticket/15801

#40 @johnbillion
8 months ago

  • Milestone changed from Future Release to 6.9
  • Owner set to johnbillion
  • Status changed from assigned to reviewing

@johnbillion commented on PR #8594:


8 months ago
#41

I've pushed a few commits to this PR to clarify the terminology in additional places and in particular to increase the distinction between permanent deletion. The phrase "Delete Permanently" is already used in several places in core when the deletion cannot be reversed.

It was correctly pointed out in Core-17164 that from a technical point of view there is no distinction between archiving a site and deactivating a site. There is a distinction in the administrative workflow though, and this becomes more distinct with this change in terminology.

## Screenshots

Confirmation message when flagging a site for deletion:

https://github.com/user-attachments/assets/cfd4579b-ead8-4ca4-bb30-1219a22cf97a

Confirmation message when archiving a site:

https://github.com/user-attachments/assets/f6cc7875-c571-4b26-a58d-93e656e4b2b4

#42 @johnbillion
8 months ago

I'm pretty happy with the state of https://github.com/WordPress/wordpress-develop/pull/8594 . @realloc @spacedmonkey @jorbin what do you think?

Testing steps:

  • Visit the Network Admin -> Sites menu on a Multisite installation
  • Use the "Flag for Deletion" and "Archive" options on different sites and verify the explanatory text on the confirmation screen makes sense

There are two related tickets:

  • #17164 for the distinction between archiving a site and flagging it for deletion. This is less of an issue once this change goes in but would still be beneficial to revisit.
  • #39158 for handling the fact that when a regular Administrator user requests to delete their site from Tools -> Delete Site, it's not possible to distinguish this from when a Super Admin does this from the Network Admin -> Sites menu.

#43 @realloc
8 months ago

Thanks for the ping, @johnbillion. I think the current state of the PR looks solid and is a good step forward. I also appreciate the effort to increase the distinction between deactivation and permanent deletion. It makes the overall admin workflow more transparent and easier to reason about.

The related tickets you mentioned are interesting as well. Some additional issues came up there that aren’t directly tied to this PR, but they might be worth revisiting in the future, such as accessibility concerns around colour contrast. Or the idea of unifying related actions across the user and network admin dashboards.

#44 @johnbillion
8 months ago

  • Keywords needs-user-docs added; dev-feedback removed

Documentation pages that need to be updated in time for 6.9.:

#45 @johnbillion
8 months ago

  • Resolution set to fixed
  • Status changed from reviewing to closed

In 60358:

Networks and Sites: Correct and improve terminology relating to deactivated, deleted, and archived sites on a Multisite installation.

  • Deleting a site is permanent action, so the terminology around site deletion has been updated to reflect that.
  • Site deactivation has been renamed to "Flag for Deletion", and a site with this status is no longer incorrectly shown as "Deleted".
  • Extra helper text has been added to the screen shown when changing a site's status to make the effects clearer to Super Admins.

Props kawauso, ryan_b, wonderboymusic, nacin, DrewAPicture, martythornley, SergeyBiryukov, jeremyfelt, ideag, jorbin, sukhendu2002, johnbillion, realloc.

Fixes #15801

Note: See TracTickets for help on using tickets.