Sauter la navigation

[Résolu] Can’t edit field permissions

Ce fil est résolu. Voici une description du problème et la solution proposée.

Problem:
In Toolset Access settings, some of the checkboxes cannot be manipulated.

Solution:
https://toolset.com/errata/checkboxes-in-toolset-access-forms-settings-are-not-working/

This support ticket is created Il y a 5 années et 1 mois. 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.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Ce sujet contient 2 réponses, a 2 voix.

Dernière mise à jour par Beda Il y a 5 années et 1 mois.

Assisté par: Beda.

Auteur
Publications
#1384351
Screen Shot 2019-11-15 at 10.08.00 AM.png

Hi,

In the page "Access Control" > "Types Fields", I am unable to check the checkboxes for the Post Meta Field Access.

Looking at the page source, I can see that all the Fields with the checkboxes are located inside a table with the classes `wpcf-access-table table table-condensed table-striped js-access-table widefat fixed striped sticky-enabled`

but right on top of that table there is another invisible table with the classes `sticky-col wpcf-access-table table table-condensed table-striped js-access-table widefat fixed striped` which prevents any interaction with the checkboxes. I have to go in and remove that table every time via chrome developer tools.

Can someone please fix this UI bug.

Thank you,

Adrian

#1384791

This is an error that was reported already, it can be fixed with this erratum:
https://toolset.com/errata/checkboxes-in-toolset-access-forms-settings-are-not-working/

Once the issue is resolved we will update that erratum accordingly.

Thanks!

#1393147

This issue is now resolved in Access 2.8.2 release