Opened 2 years ago
Closed 2 years ago
#59569 closed defect (bug) (fixed)
wp_pattern_category is set public to true, when it should have been false.
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 6.4 | Priority: | normal |
| Severity: | normal | Version: | 6.4 |
| Component: | Taxonomy | Keywords: | has-patch commit dev-reviewed |
| Focuses: | Cc: |
Description (last modified by )
The pattern categories taxonomy is registered in wp-includes/taxonomy.php at lines 226-245, added by ticket #59379. Not sure why e.g. public is set to true, when it should have been false.
Wordpress version 6.4beta
Change History (18)
This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.
2 years ago
#4
follow-up:
↓ 5
@
2 years ago
It was initially set to false as the initial PR was just intended to get the infrastructure in place and not make anything available to users.
With 53835 it was set to public, because this taxonomy is intended for use by users either via the admin interface at /wp-admin/edit-tags.php?taxonomy=wp_pattern_category or via the UI added to the editor, so setting public to true seemed like the correct option. We may have misunderstood the meaning of public in this context though because /wp-admin/edit-tags.php?taxonomy=wp_pattern_category is still accessible even if it is set to false as you note.
Should we put up a patch to switch this back to false?
#5
in reply to:
↑ 4
@
2 years ago
- Keywords needs-patch added
Thank you @glendaviesnz for explaining :) I get it.
Replying to glendaviesnz:
With 53835 it was set to
public, because this taxonomy is intended for use by users either via the admin interface at/wp-admin/edit-tags.php?taxonomy=wp_pattern_categoryor via the UI added to the editor, so setting public to true seemed like the correct option. We may have misunderstood the meaning of public in this context though because /wp-admin/edit-tags.php?taxonomy=wp_pattern_categoryis still accessible even if it is set tofalseas you note.
As long as it's intended for use within the admin only, it should work with the public set to false. In my testing, the pattern categories are still accessible within:
- Pattern Categories
wp-admin/edit-tags.php?taxonomy=wp_pattern_category - Site editor
- Post/Page editors
Should we put up a patch to switch this back to false?
As long as it is working in all admin UIs, then yes, please.
This ticket was mentioned in PR #5604 on WordPress/wordpress-develop by @glendaviesnz.
2 years ago
#6
- Keywords has-patch added; needs-patch removed
## What?
Sets the pattern categories taxonomy public param to false instead of true
## Why?
It was suggested here that this would be a better setting for this taxonomy as it only needs to be accessed in admin, not the frontend.
Trac ticket: https://core.trac.wordpress.org/ticket/59569
#7
@
2 years ago
Gutenberg plugin PR is here - https://github.com/WordPress/wordpress-develop/pull/5604
#8
@
2 years ago
@hellofromTonya ignore the notification you may have got asking for an explanation of the reasoning for this, after rereading the docs I see it is just a matter of limiting the permissions to the minimum needed, and there is no need for access to this taxonomy from the front-end.
@ramonopoly commented on PR #5604:
2 years ago
#9
I think the REST API fixtures need to be regenerated.
Running the unit test WP_Test_REST_Schema_Initialization should do it I think.
npm run test:php -- --filter WP_Test_REST_Schema_Initialization
@hellofromTonya commented on PR #5604:
2 years ago
#10
Hmm, the tests are failing. Pulling it down locally to have a peek.
#12
@
2 years ago
- Keywords commit added
- Owner set to hellofromTonya
- Status changed from new to reviewing
Patch: https://github.com/WordPress/wordpress-develop/pull/5604
This patch is ready for commit.
#14
@
2 years ago
- Keywords dev-feedback added
- Resolution fixed deleted
- Status changed from closed to reopened
Reopening for 2nd committer review to backport [57044] to the 6.4 branch.
@hellofromTonya commented on PR #5604:
2 years ago
#16
Committed via https://core.trac.wordpress.org/changeset/57044
#17
@
2 years ago
- Keywords dev-reviewed added; dev-feedback removed
Marking as dev-reviewed with @azaozz and @mikeschroder reviewing it. Also see discussion in Make/Core slack.
Hello @vrajadas,
Welcome to WordPress Core's Trac :) Sorry for the delay in responding to your ticket.
The change: #59379 / [56642].
It was originally set to
false, but then changed in Gutenberg PR 53835, which added the UI and ability to assign categories to the user created patterns.Hmm I also wonder why the
publicarg is set totrue. Tested with it set tofalseand am able to add, see, and update pattern categories.Pinging the contributors for discover the reasoning @glendaviesnz @isabel_brison @mamaduka.
Pulling into 6.4 for awareness and discussion.