Chakrapani Gautam

Update: I found this solution here on github issues: https://github.com/WordPress/gutenberg/issues/10169#issuecomment-488052952 and it has been working quite well for me. Although it was suggested back in 2019 and the issue is still open, I’m not sure if there are any downsides, but for now, everything looks good to me with this one.

Turns out, I just had to use a different filter, instead of the one I mentioned earlier.

Oops, sorry. I didn’t specify where exactly in the UI I’m referring to. Hope this helps: https://ibb.co/grSNY43

Yes, the screen options per page limit is something I’ve played around with in the past, it wasn’t that much of a problem. The issue is with this new gutenberg taxonomy sidebar. This loads the terms in the batches of 100.

Hey, thanks Alex for the insights. This explains a lot about why things are the way they are. Thanks for the ticket, I haven’t read entirely but judging based on the first few responses of the tickets, I think it could’ve been solved with a simple checkbox asking users if they want to split the term if they choose to create the same term in some other taxonomy than the existing one. Or in case of core WP API, a flag in the arguments should’ve done the trick, instead of doing it automatically, no? Smells like over-engineering but I maybe wrong.

And yeah, thanks for the hierarchical approach, that seems interesting. I’ll explore that too and how well it fits with our use case.

• This reply was modified 1 year, 10 months ago by Chakrapani Gautam.

Wow, that is actually clever. Why didn’t it occur to me? Just mentioning it here for anyone stumbling here, fiddle around the pseudo selector for label as suggested. The class that wraps the label is edit-post-post-author

Okay, one way I can think of is this. I was able to remove the entire Summary Panel using the following line from my console.

wp.data.dispatch('core/edit-post').removeEditorPanel( 'post-status' );

So right now, I’m thinking of re-implementing the Summary Panel as is from here: https://github.com/WordPress/gutenberg/blob/d899945816f0af03eae7d94bb43a18bc2b877e93/packages/edit-post/src/components/sidebar/post-status/index.js#L26

Except, the part of <PostAuthor/> is replaced with <PostOwner/>, a custom implementation from my end.

Not sure if that’s the way to do it but that’s one solution I can think of.