Opened 5 months ago
Last modified 6 days ago
#61921 new enhancement
Require plugin name should be taken from plugin header instead of readme name
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 6.6.1 |
| Component: | Plugins | Keywords: | needs-patch |
| Focuses: | ui | Cc: |
Description
Hello team,
It looks too congested if the readme plugin name is picked in the plugins table. Using the plugin header name will be more convenient and consistent.
Current: https://prnt.sc/PZkYXa-Z3vWn
Proposed: https://prnt.sc/u-VLaKs4aFpY
Thank you
Note: See
TracTickets for help on using
tickets.
Hi @wpwax, I was unable to reproduce the issue you mentioned. Based on your screenshot, it seems the example includes some paid plugins.
To test this, I installed WooCommerce-related plugins that depend on WooCommerce as a dependency. When I modified the WooCommerce Plugin Header Name and the WooCommerce readme name, the required plugin name displayed was the updated WooCommerce Plugin Header Name, as expected.
[Screenshot(https://prnt.sc/BBs3oaTnnzYQ)]
Could you please share another example with me?