WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#32647 closed defect (bug) (maybelater)

Multisite UX - Move Save Changes button to be next to the Primary Site select field

Reported by: kdamken Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Networks and Sites Keywords: close
Focuses: ui, multisite Cc:

Description

On the My Sites page, there is a select field that lets you choose your primary site. Below that is a table that lists out your sites, then below that there is the button to Save Changes for when you select a new primary site. Since the Save Changes button is related to the select dropdown and not the table, it might be better to have the button to the right of the select field rather than underneath the table.

Attachments (2)

32647.diff (964 bytes) - added by amcreative 5 years ago.
32647.diff
Screen_Shot_2015-06-15_at_1_18_23_PM.png (44.1 KB) - added by amcreative 5 years ago.
screenshot of changes

Download all attachments as: .zip

Change History (13)

#1 @earnjam
5 years ago

  • Component changed from General to Networks and Sites
  • Keywords ui-feedback added
  • Version set to 3.0

Could be done in coordination with #32645

@amcreative
5 years ago

32647.diff

@amcreative
5 years ago

screenshot of changes

#2 @amcreative
5 years ago

@earnjam

I've attached a diff that moves the button from the current location to the right of the select box. I've also attached a screenshot showing the change.

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


5 years ago

#4 @jeremyfelt
5 years ago

  • Milestone changed from Awaiting Review to 4.3

Thanks for the ticket @kdamken! This makes a lot of sense, the placement of the Save Changes button on this screen has confused me plenty of times. :)

#5 @kdamken
5 years ago

Thanks @jeremyfelt! Though I can't take too much credit, it was @earnjam who had the idea and showed me how to add a ticket to Trac at the Philly Wordcamp.

#6 follow-up: @earnjam
5 years ago

In today's example of "nothing is ever simple in multisite", upon digging on this a bit more, I discovered that the Save Changes button is at the bottom because the sites list has the myblogs_options filter, which in theory would allow plugins to add additional fields for submitting/processing. It defaults to an empty string, but could be used to insert extra inputs into this form.

My original thought on this ticket was to simply shorten the <form> to only include the Primary Site select, but that would break any usage of this filter that adds inputs.

The other option is to do as @amcreative did and simply move the save button to the top. That would not break usage of the filter, but it would make it less ideal if you had a long list of sites and made a change at the bottom and had to scroll back up.

I'm not sure how much that filter is actually used in the wild, but I'm hesitant to change it without some understanding.

#7 @amcreative
5 years ago

@earnjam Would it make sense to have the button at both the top and bottom as we see in other instances throughout WordPress such as "Bulk Actions" in the post editor? This would provide some context to the drop down at the top of the "My Sites" screen but would also not lose the option if the list is long.

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


5 years ago

#9 in reply to: ↑ 6 @obenland
5 years ago

  • Keywords close added; ui-feedback removed

Replying to earnjam:

In today's example of "nothing is ever simple in multisite", upon digging on this a bit more, I discovered that the Save Changes button is at the bottom because the sites list has the myblogs_options filter, which in theory would allow plugins to add additional fields for submitting/processing. It defaults to an empty string, but could be used to insert extra inputs into this form.

Yes, we should probably leave the button where it is now.

#10 @jeremyfelt
5 years ago

  • Milestone 4.3 deleted
  • Resolution set to maybelater
  • Status changed from new to closed

Agreed, our hands are pretty tied here at the moment.

I'll echo Boone from #31685:

The more I look at My Sites, the sadder I get - it could probably use a significant rethink to make it something much more beautiful and useful.

It's going to take an overhaul (replacement?) of this screen to make changes like the one in this ticket. Going to close this and the related #32645 as maybelater, because maybe later. :)

#11 @jeremyfelt
5 years ago

Actually, #32645 still has a chance due to craftiness.

Note: See TracTickets for help on using tickets.