WordPress.org

Make WordPress Core

Opened 8 years ago

Last modified 12 months ago

#17164 new enhancement

More elegant handling of site 'archive' options for MultiSite

Reported by: Ipstenu Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.1
Component: Networks and Sites Keywords: has-ux-feedback needs-patch has-ui-feedback
Focuses: administration, multisite Cc:

Description

Right now you have a few options with MultiSite blogs

1) Spam
2) Deactivate
3) Archive
4) Delete

Spam is easy to understand, and should be marking the admin and site as spam. Delete ditto, hi.

Deactivate and Archive are weird though and almost seem backwards. Deactivate means to turn OFF (like deactivating a plugin). Archive implies that you're making a site read-only.

Right now, if you change a site to 'deactivated' it actually shows up as DELETED and the front end has the message "This user has elected to delete their account and the content is no longer available." Clearly the verbage on the network/sites.php page needs to be updated (and perhaps the front end to 'This site has been deactivated.' to be consistant).

If you 'Archive' a site it kicks it to a paler pink in the sites.php page (though the 'Archived' text is white and nigh impossible for me to read) and the front end says "This site has been archived or suspended."

It's rather illogical there. Archive SOUNDS like it should be making things read-only (and turning off commenting and posting if possible). Otherwise it should just be 'Suspend', and at that point, why have two options that pretty much do the same thing from the front-end perspective?

Attachments (3)

status column WP admin multisite.png (136.2 KB) - added by boemedia 12 months ago.
Separate status column in multisite dashboard
are you sure to change state multisite.png (96.3 KB) - added by boemedia 12 months ago.
Extra info could be added to the screen that shows before final confirmation
guidance before changing status multisite.png (170.5 KB) - added by boemedia 12 months ago.
More guidance before changing status multisite would give a better UX

Download all attachments as: .zip

Change History (27)

#1 @duck_
8 years ago

Related #15801.

Basically a dupe on delete/deactivate trouble, but not archive.

#2 @scribu
8 years ago

+1 on merging Deactivate and Archive.

#3 @toscho
8 years ago

  • Cc info@… added

#4 @Ipstenu
8 years ago

Either merge or make distinctly separate functionally.

Having a way to flag a site as 'archived' where it's there, but read only, is probably plugin territory, but I can see as useful. Deactivate/mark as spam/archive is just all overkill for the same effect right now.

#5 @SergeyBiryukov
8 years ago

  • Keywords ux-feedback added
  • Version set to 3.1

#6 @archonic
8 years ago

  • Cc archonic added

Hope this gets approved! Would ultimately like "public" in the sites context to be renamed to something more descriptive like "crawl-able". Agree on archiving keeping the site visible by the public but lock the backend to all but the super-admin.

#7 @DrewAPicture
8 years ago

  • Summary changed from More elegant handling of site 'archive' optinos for MultiSite to More elegant handling of site 'archive' options for MultiSite

#8 @hansluk
8 years ago

  • Cc hansluk added

#9 @jazbek
7 years ago

+1 for ipstenu's suggestion for Archive functionality. Would be awesome to be able to make an old/inactive site read-only. Statically caching it somehow would be amazing, though not sure that is core territory, so an archive hook would be useful (there may be one already, didn't check).

#10 @jazbek
7 years ago

  • Cc j.yzbek@… added

#11 @jeremyfelt
5 years ago

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

#12 @Kent Brockman
5 years ago

  • Keywords dev-feedback needs-refresh needs-docs added

Will this ticket bring attention of some dev? any possibility to upgrade version number to 3.8? or is 3.1 the version when request was first noticed?

#13 @Ipstenu
5 years ago

Version number is for when the problem first arose, not for what version we fix it in :) Milestone will be set to a version if we get there.

#14 @Ipstenu
5 years ago

  • Keywords needs-patch added; needs-refresh needs-docs removed

#15 @wonderboymusic
5 years ago

  • Milestone changed from Awaiting Review to Future Release

#16 @leedman
5 years ago

  • Keywords ui-feedback added

Additions to Site Management

Bulk Actions - Add Activate and other options so multiple blogs can be selected and qeued and processed.

Filters - Allow the user to view only the Active sites, Inactive Sites, etc., via Filter box option.

Sort - During an overview, Sorting on Blog Status would also be useful.

#17 @chriscct7
4 years ago

  • Focuses administration added
  • Keywords dev-feedback removed

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


2 years ago

#19 @melchoyce
2 years ago

@jeremyfelt @flixos90 @johnjamesjacoby @spacedmonkey Curious what your thoughts are as component maintainers. I don't have a lot of multisite experience, but @Ipstenu's suggestions make sense to me.

#20 @flixos90
2 years ago

I agree that at least the verbiage should be changed. Related ticket is #39158 (though it is more about a bug in the functionality).

Adjusting the behavior of what archiving vs deactivating does, I'm not sure that can be changed due to previous expectations that might exist. But we should certainly consider it and investigate possibilities.

#21 @johnjamesjacoby
2 years ago

In my opinion, also related are #36492, #12706.


For this ticket specifically, should be update the verbiage? Probably, yes. Though it'll be difficult to change their functionalities because of how deeply these are integrated into WordPress.com, Jetpack, and other open multisite networks.


For WordPress in general, deeper scrutiny should be considered. See my comment here: https://core.trac.wordpress.org/ticket/12706#comment:211

These links currently map to several unique columns in the wp_blogs global database table:

public, archived, mature, spam, deleted

My preference would be to consolidate these columns down to 1 status column, with an API to help define what those statuses are and what they mean within the system.

Then these row-action links can be driven by their defined statuses rather than the literal database schema. The added cardinality of an indexed, string-based status column should improve query performance over the multiple numerical columns, too.

Last edited 2 years ago by johnjamesjacoby (previous) (diff)

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


2 years ago

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


12 months ago

#24 @boemedia
12 months ago

  • Keywords has-ux-feedback has-ui-feedback added; ux-feedback ui-feedback removed

We discussed this ticket in today's design triage. We agree with @johnjamesjacoby that a separate status column would work. This way it's possible to filter and for instance, only see active sites or sites that are archived.

Besides that, the colour status seems a bit much, maybe we can work with icons in the status column instead?

We also think the different statuses could benefit from more clarification. What's the difference between deactivating and archiving a site? We think of clarifying on 2 levels: possible an info button next to the status column and extra info after changing a status. See attached screenshots as well.

@boemedia
12 months ago

Separate status column in multisite dashboard

@boemedia
12 months ago

Extra info could be added to the screen that shows before final confirmation

@boemedia
12 months ago

More guidance before changing status multisite would give a better UX

Note: See TracTickets for help on using tickets.