[Resuelto] Editor with permission can't delete CPT-posts
This support ticket is created hace 4 meses, 3 semanas. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.
Sun
Mon
Tue
Wed
Thu
Fri
Sat
-
9:00 – 12:00
9:00 – 12:00
9:00 – 12:00
9:00 – 12:00
9:00 – 12:00
-
-
13:00 – 18:00
13:00 – 18:00
13:00 – 18:00
13:00 – 18:00
13:00 – 18:00
-
Supporter timezone: America/Sao_Paulo (GMT-03:00)
Este tema contiene 8 respuestas, tiene 2 mensajes.
Since a while, the user with the Editor role can't delete posts from a certain post type he is responsable for. I can't find why this occurs. He get's a message that he has no permission to see the page after clicking on delete.
Hello, can you tell me if this CPT in question is in a post relationship with any other posts? If so, what are the permissions for the editor role in the related post types? For example, if this CPT1 is in a post relationship with another post type like CPT2 then what are the custom role permissions for CPT2?
Also, can you please review the editor roles in Toolset Access and make sure it has the permission "Delete own posts using Toolset Forms" enabled?
Do you remember if there was a specific action before the issue started happening, like a plugin update, an edition of the CPT or user role or something along these lines?
Can you please let me know what CPT is having this issue in order for me to investigate it?
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: enlace oculto
Please, let me know if you need any additional details. Have a nice day.
After that, I tested it and I'm able to delete the messages logged in aseither an administrator or editor. As soon as the message is deleted, the page refreshes without errors and the message is not showed anymore.
I tested without being logged in and with other roles and the delete button won't work in those cases.
Can you please review it to make sure it is working as expected now?
If I misunderstood your inquiry, please let me know and I'll reassess.
I checked it and the issue seems related to the plugin Fusion Builder from Avada, if it is temporarily disabled, then there's no permission issue.
I believe that it might be necessary to add some custom Avada capabilities to the role Editor in order for it to be able to delete and/or edit messages from the backend.
It is possible to add custom permissions in Toolset Access > Custom Roles > Advanced mode > Editor > Change permissions > Custom capabilities
Would you kindly be able to reach out to Avada support and check if there might be some custom capabilities that we could add to the role Editor in order to fix this issue?