Opened 7 years ago
Last modified 4 days ago
#40683 accepted enhancement
Add a Plugins link to admin bar menu
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.5 | Priority: | normal |
Severity: | normal | Version: | 4.7.4 |
Component: | Toolbar | Keywords: | has-patch needs-testing |
Focuses: | ui | Cc: |
Attachments (7)
Change History (24)
#1
@
7 years ago
- Focuses ui removed
- Keywords has-patch added
@colomet The "Plugin" menu is not required to everyone as a shortcut menu on admin bar but if everybody agrees to add plugin shortcut then i have added patch for same.
I have added "Plugin" shortcut menu option after the "Menus" which shows if current user has capability to install plugins like current_user_can( 'install_plugins' )
. Please see the below attached snapshot.
http://www.awesomescreenshot.com/image/2466653/47c2324998660de213aea6396c0d610b
This ticket was mentioned in Slack in #accessibility by afercia. View the logs.
7 years ago
#3
@
7 years ago
- Component changed from Administration to Toolbar
- Focuses ui added; accessibility administration removed
Removing the accessibility focus, as per today's accessibility bug scrub. More related to UI.
#5
@
6 years ago
- Keywords needs-testing added
Refreshed the patch with a couple of changes.
- Add plugins after the themes link but before any other potential extra links.
- Capability for link is activate_plugins.
#6
@
6 years ago
- Summary changed from plugin direct acces from admin header menu to Add a Plugins link to admin bar menu
This ticket was mentioned in Slack in #core by danieltj. View the logs.
6 years ago
This ticket was mentioned in Slack in #core by danieltj. View the logs.
6 years ago
#10
@
2 years ago
The new Plugins link would not belong between Appearance and Menus.
I prefer placing the new link before the set of Appearance links 40683.before-appearance.patch . However, that does not match the order of links in the side admin menu, so I made another option with Plugins at the end of the Appearance group 40683.end-of-appearance-group.patch .
Both patch options use the ID of 'ab-plugins' (similar to ab-icon and ab-item) to avoid any confusion with links added by plugins. A directory search found some nodes with a 'plugins' ID. Of course, this one could have a better name, too.
#11
follow-up:
↓ 13
@
7 weeks ago
- Milestone changed from Awaiting Review to 6.5
- Owner set to joedolson
- Status changed from new to accepted
Speaking personally, I have a need to go to the plugins screen *much* more frequently than I do the themes screen.
I think this would be a good change, and makes a lot of sense. It's not clear to me why plugins don't have equal relevance here; it's a very comparable use case to themes or widgets, e.g. jumping back and forth between admin and front-end comparing how a given choice works for you.
I would put Plugins before 'Themes', to match the order in the admin menu. However, it's a short enough menu that I could be convinced otherwise.
#12
@
4 weeks ago
Test Report
Patch tested: 40683.before-appearance.patch
Environment
- WordPress: 6.5-alpha-56966-src
- PHP: 7.4.33
- Server: nginx/1.25.2
- Database: mysqli (Server: 5.7.43 / Client: mysqlnd 7.4.33)
- Browser: Chrome 118.0.0.0
- OS: macOS
- Theme: Twenty Twenty-Four 1.0
- MU Plugins: None activated
- Plugins:
- Test Reports 1.0.0
Actual Results
- This patch Add Plugins link before the Appearance ✅
Screenshots
Before Apply Patch | After Apply Patch ✅ |
![]() | ![]() |
#13
in reply to:
↑ 11
@
3 weeks ago
Replying to joedolson:
I would put Plugins before 'Themes', to match the order in the admin menu.
Unless I'm missing something, Plugins comes after Themes, both in the regular admin menu and in the Network Admin menu. So placing the link after the Appearance group would be my preference here.
Placing it in the wp_admin_bar_appearance_menu()
function, as in 40683.end-of-appearance-group.patch, doesn't feel right to me though, as plugins are not in the Appearance group. After the wp_admin_bar_appearance_menu()
call in wp_admin_bar_site_menu()
seems like a better place.
Replying to sabernhardt:
Both patch options use the ID of 'ab-plugins' (similar to ab-icon and ab-item) to avoid any confusion with links added by plugins. A directory search found some nodes with a 'plugins' ID. Of course, this one could have a better name, too.
There appear to be false positives in those search results. Most of the instances are unrelated to the admin bar, and most of the related ones use it for the same purpose (linking to the Plugins screen). I think we can just use 'plugins'
here, for consistency with the existing naming scheme: 'themes'
, 'widgets'
, 'menus'
, etc. Plugins that are still supported should adapt to the change.
40683.3.diff is a refresh with the above in mind.
#14
@
3 weeks ago
Test Report
Patch Tested: https://core.trac.wordpress.org/attachment/ticket/40683/40683.3.diff
Environment:
WordPress - 6.5-alpha-56966-src
OS - Windows
Browser - Chrome
Theme: Twenty Twenty One
PHP - 8.0.18
Active Plugin - None
Actual Results:
- This patch Adds Plugins link in admin bar✅
Screenshots:
Before Patch: https://prnt.sc/KTHZYZowOEvx
After Patch : https://prnt.sc/ZSkPAIbkot2i
#15
@
3 weeks ago
Test Report
Description
This report validates whether the indicated patch works as expected.
Patch tested: https://core.trac.wordpress.org/attachment/ticket/40683/40683.3.diff
Environment
- WordPress: 6.5-alpha-56966-src
- PHP: 8.2.12
- Server: nginx/1.25.3
- Database: mysqli (Server: 5.7.44 / Client: mysqlnd 8.2.12)
- Browser: Chrome 119.0.0.0
- OS: Windows 10/11
- Theme: Twenty Twenty-Four 1.0
- MU Plugins: None activated
- Plugins:
- Test Reports 1.0.0
Actual Results
- ✅ Plugins Link shows up in the admin bar.
Supplemental Artifacts
#16
@
2 weeks ago
Test Report
Description
Patch working fine. ✅
Patch tested: https://core.trac.wordpress.org/attachment/ticket/40683/40683.3.diff
Environment
- WordPress: 6.5-alpha-56966-src
- PHP: 7.4.33
- Server: nginx/1.25.2
- Database: mysqli (Server: 5.7.43 / Client: mysqlnd 7.4.33)
- Browser: Chrome 119.0.0.0
- OS: Windows 10/11
- Theme: Twenty Twenty-Three 1.3
- MU Plugins: None activated
- Plugins:
- Test Reports 1.0.0
- WP System Info 1.5
Actual Results
- ✅ Issue resolved with patch.
Supplemental Artifacts
Before applying patch:
After applying patch:
#17
@
4 days ago
Test Report ✅
Patch tested: https://core.trac.wordpress.org/attachment/ticket/40683/40683.3.diff
Environment
- WordPress: 6.5-alpha-56966-src
- PHP: 7.4.33
- Server: nginx/1.25.2
- Browser: 119.0.6045.199 (Official Build) (x86_64)
- OS: macOS Ventura 13.3
- Theme: Twenty Eleven 4.5
Screenshot
https://prnt.sc/52DItsBn6tdS
Test status:
The patch is working fine. ✅
sreenshot of the place where the plugin direct acces is missing