Make WordPress Core

Opened 15 months ago

Last modified 14 months ago

#57951 new defect (bug)

Multisite filters not filtering

Reported by: richardkrone's profile richardkrone Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 6.1.1
Component: General Keywords: has-screenshots
Focuses: ui, administration, multisite Cc:

Description

I have a multisite with over 200 folder based sub-sites.

When I am on the /wp-admin/network/sites.php page, the public filter at the top of the page do not filter as expected.

This is my current list: All (258) | Public (226) | Archived (11) | Deleted (9)

When I click on Public filter, I still see both Archived and Deleted in the list of filtered sites. I suppose that I expected to only see those that were not archived or deleted, as they have their own filters.

I may be misunderstanding the point of a "Public" filter.

Thank you.

Attachments (1)

site-attributes.png (419.2 KB) - added by juhise 14 months ago.
site attributes

Download all attachments as: .zip

Change History (6)

This ticket was mentioned in Slack in #core-test by juhise. View the logs.


14 months ago

#2 @juhise
14 months ago

  • Keywords has-screenshots added

Hi @richardkrone,

Thanks for reporting this. It seems public attribute is used to make the site available for search engines and hence it can be used with other attributes. I can see that multiple attributes can be assigned to one site and hence it shows in multiple filters, though it doesn't make much sense to me. Attaching the screenshot site-attributes.png

There are a few open issues for blog status for example #17164.

@juhise
14 months ago

site attributes

#3 @richardkrone
14 months ago

Hello @juhise

Thank you for your response.

This makes sense now that you said it.

In the case that the filters at the top can be representative of more than one attribute at a time, should there not be a Spam and Mature filter at the top at all times as well, even if there are (0) in the list? This would have allowed me to make a more logical leap to what you are saying.

Thanks again.

Richard

#4 @juhise
14 months ago

Hey @richardkrone

I agree, it doesn't seem to be mature functionality. I think it needs some modification, that's what they are discussing in #17164 I believe.

#5 @richardkrone
14 months ago

I think that the tickets are linked.

I had another ticket https://core.trac.wordpress.org/ticket/56076 where I discussed the same issues.

The semantics and UI need a good review.

Thanks for your help with this. Much appreciated.

Note: See TracTickets for help on using tickets.