WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 4 months ago

#20983 closed defect (bug) (wontfix)

Change phrasing for 'Network Activate' newly installed plugins

Reported by: Ipstenu Owned by:
Milestone: Priority: normal
Severity: minor Version: 3.0
Component: Plugins Keywords: has-patch
Focuses: multisite Cc:

Description

Not everyone is clear what 'Network Activate' means and after installing a plugin, a lot of people just assume that activate will turn it on for one site only. Then they complain that the plugin turned it self on automagically!

While it would make the link longer, I think changing it to the same wording we have in the title might actually catch their eye: Activate this plugin for all sites in this network

(The other thought was to put 'Return to Plugins Page' in front of Network install, but that would annoy single site people, of whom there are a majority)

Attachments (3)

20983.diff (1.3 KB) - added by Ipstenu 2 years ago.
20983.1.diff (2.3 KB) - added by Ipstenu 11 months ago.
De/Activate for all sites
20983.patch (4.8 KB) - added by ocean90 10 months ago.

Download all attachments as: .zip

Change History (23)

Ipstenu2 years ago

comment:1 follow-up: scribu2 years ago

How about 'Activate for all sites' ? The few people running multiple networks can figure it out.

comment:2 jeremyfelt11 months ago

  • Keywords ux-feedback added
  • Milestone changed from Awaiting Review to 3.7

Need some UX feedback, moving to 3.7 for discussion or close.

+1 for the shorter string via @scribu

comment:3 in reply to: ↑ 1 hotchkissconsulting11 months ago

  • Cc hotchkissconsulting added

Replying to scribu:

How about 'Activate for all sites' ? The few people running multiple networks can figure it out.

+1 -- This still provides clarification while being succinct

comment:4 SergeyBiryukov11 months ago

"Activate for all sites" sounds good to me.

Note that the string also needs to be changed in the Bulk Actions dropdown.

Ipstenu11 months ago

De/Activate for all sites

comment:5 Ipstenu11 months ago

Uploaded new diff and I think I got everything. wp-admin/includes/class-wp-plugins-list-table.php and wp-admin/includes/class-wp-upgrader.php

comment:6 Hanni11 months ago

  • Cc h@… added

ocean9010 months ago

comment:7 ocean9010 months ago

If the text is changed in the Bulk Actions dropdown, shouldn't it be changed for the action links too? See 20983.patch

http://f.cl.ly/items/0O043j3u2z1b0o37062j/Bildschirmfoto%202013-09-21%20um%2020.26.48.png

Also: The links already have a title saying "Activate this plugin for all sites in this network". Isn't that enough?

comment:8 helen10 months ago

Hiding important information in a title is a terrible idea, and it shouldn't have a title anyway. I thought the idea was to change everything, action links and bulk dropdown.

comment:9 Ipstenu10 months ago

The title is not good enough.

But yes, the idea WAS to change everything and neglecting the bulk dropdown was an omission :)

comment:10 ocean9010 months ago

Okay, I agree. So should we change the title too? Current:

Deactivate for all sites => Deactivate this plugin
Activate for all sites => Activate this plugin for all sites in this network

And what about themes? There we have "Network Enable".

comment:11 Ipstenu10 months ago

Themes is a separate mess IMO. The activation/deactivation process is entirely different.

We may as well change the titles to match (or maybe remove as Helen indicated? Does this break accessibility?)

comment:12 knutsp10 months ago

Network activate is not the same as activate for all sites. If the plugin was just activated for all sites, then it could be deactivated for some, afterwards. Network activate means to force the plugin to be active on all sites, even invisibly to the site admins, and this should be reflected in the text. "Mandatory across network".

comment:13 follow-up: Ipstenu10 months ago

It's not 'mandatory' though, it is 'active' on all sites.

Further details would be something for the help screen, but issue we're facing today is a glut of people confusing 'network activate' on plugins with what it means on themes.

I will note that 15 months ago, this ticket was aimed because we were 'network activating' from the primary site on Multisite. This is no longer the case, and while I think using 'Network Activate' for BOTH plugins and themes is inconsistent (they don't mean the same thing), perhaps this should be chucked, and we should have 'Network Enable' for themes and 'Network Activate' for plugins.

Then use the help screen to go further.

comment:14 in reply to: ↑ 13 knutsp10 months ago

Replying to Ipstenu:

It's not 'mandatory' though, it is 'active' on all sites.

Mandatory, from "TheFreeDictionary": "Required or commanded by authority; obligatory"

Since site admins cannot deactivate such plugins, and since site admins can't even see that such plugins is active, I call them mandatory. If they were just activated, site admins would be able to see them in the list of (active) plugins and deactivate them.

In theory, the "Network activate" action could loop through all sites in the network and make the plugin active, but that is not what's happening, of course. Hence, the plugin becomes mandatory active for all sites in a network, not just happening to be active, in the usual way, on all sites.

And this distinction is exactly what causes confusion. "Network activate" does not provide the superadmin specific information about the effect of this action.

comment:15 helen10 months ago

Three things:

  1. Redundant title attributes hurt accessibility. See #24766.
  2. Problems with network enable theme messaging should be addressed separately.
  3. We are not going to be able to teach somebody how to be a multisite admin through the wording of a single action link.

comment:16 follow-up: Ipstenu10 months ago

  • Keywords close added

Re #1 - So ... we shouldn't have titles at all? I honestly don't know!

I actually feel today we should drop this ticket. The initial need was that when one network activated, one did it from the Plugins page of Site #1. This is no longer the case, the confusion is no longer the case, and 'Network Activate' is a correct term for use here.

So yeah, marking we close my own ticket :)

comment:17 jeremyfelt10 months ago

I'm working on something right now to globally activate plugins across multiple networks and have 'Activate Globally' as the text at the moment.

I wonder if something like Activate on Network or Activate across Network would work as more of an action statement.

Also good with closing otherwise. :)

comment:18 nacin9 months ago

  • Milestone changed from 3.7 to Future Release

comment:19 jeremyfelt6 months ago

  • Component changed from Multisite to Plugins
  • Focuses multisite added

comment:20 in reply to: ↑ 16 jeremyfelt4 months ago

  • Keywords ux-feedback close removed
  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Replying to Ipstenu:

The initial need was that when one network activated, one did it from the Plugins page of Site #1. This is no longer the case, the confusion is no longer the case, and 'Network Activate' is a correct term for use here.

+1 for this reasoning (and @helen's third point).

Note: See TracTickets for help on using tickets.