Block TAG creation in Gutenberg

Hi @alessandroemerich

Thanks for using PublishPress Capabilities. You may require PublishPress Permissions in this case. Please check this documentation: https://publishpress.com/blog/permissions/stop-users-creating-new-tags/

Thanks for the help. I’ll test it here, but in short, do I have to install another plugin? If I buy it, do I have to buy both plugins?

Hi @rizaardiyanto

Following the instructions you provided in the link, I was able to restrict it. However, there are Groups or Roles for which I need the “Tags” item to be displayed, but even after assigning all permissions, this item does not appear.

Here are the Capability settings:

https://sandbox.infomoney.com.br/wp-content/uploads/2024/09/demo_01_teste_01.jpg

Here are the Permission settings:

https://sandbox.infomoney.com.br/wp-content/uploads/2024/09/demo_01_teste_02.jpg

Here is the user with the Role assigned:

https://sandbox.infomoney.com.br/wp-content/uploads/2024/09/demo_01_teste_03.jpg

Finally, the WordPress administration screen showing that the “TAG” item is not displayed:

https://sandbox.infomoney.com.br/wp-content/uploads/2024/09/demo_01_teste_04.jpg

We are doing a proof of concept. If we can achieve some goals, we will purchase the complete plugin package, if you confirm that we will need 2 plugins (previous question).

Thanks again for your help.

@alessandroemerich From your screenshot, the configuration should have been correct. I will not be able to pinpoint the exact issue why the Tag is not showing without proper troubleshooting.

You could purchase our plugin, then open a support ticket and share your temporary login details to your site so we could investigate this further.

And yes, for your need, you will require 2 plugins (Capabilities & Permissions).

Thanks,

Hi @rizaardiyanto ,

I understand the issue, but how can I justify to the company buying something that already has an error? Something that I will have to buy and open a ticket to make it work (and that should work in the free version)? It’s a complicated issue. The idea is to see if the product is good enough to buy it. Would anyone buy MS Office if they later needed to contact technical support to make it work perfectly? A proof of concept works for that.

In addition, the permissions plugin also shows an error when clicking on a group. The “Set Specific Permission” and “Clone” tabs also don’t work. See below a print with the error:

https://sandbox.infomoney.com.br/wp-content/uploads/2024/09/demo_01_teste_05.jpg

Would it be possible to help us at least with the TAGs issue? With that, I can complete the proof of concept and justify the purchase. In addition, everyone who is trying out the tool would have a better impression of it.

Just for reference, here are some details about WordPress and the environment we are running on:

• Hosting: WPVIP
• WordPress version: 6.6.1
• Chrome: 128.0.6613.115

If you would like any further information, please let me know.

Thanks again.

@alessandroemerich @rizaardiyanto The suppression of Tag management access by the Permissions plugin is intentional. When you enable a Post Type or Taxonomy in Permissions > Settings, that means taxonomy-specific capabilities will now be required for editing or management access. Roles which previously had access based on more generic capabilities like edit_posts or manage_categories will now need to have the corresponding type-specific capability. In this case, you will need to add the manage_post_tags capability to the role in question.

This situation is confused by the current behavior of our PublishPress Capabilities plugin. Its capability assignment UI indicates that the manage_categories capability always governs access to Tag management. That is not correct if the Permissions plugin is active with the Tags taxonomy enabled for filtering. The UI error will be corrected in a future release of PublishPress Capabilities. Until then, you can use the “Add Capability” sidebar input box to manually add the manage_post_tags capability to your role.

Hi @kevinb ,

Thank you very much for your help. With the configuration you mentioned, we were able to create the proof of concept. We will continue internally to validate the product. I would just like to point out another Javascript error that is shown above in the screenshots, but that will not hinder our proof of concept.

Thanks.