bckaz

Hello –
We have been having similar issues – since the new updates . . .
I don’t know if the updates solved the issues for the others on this topic —
Unfortunately, even the newest updates are not solving the issue for us.
After Slack advice, we are still using Pods 2.7.12 (as the images all show up / work correctly in this version)

Thank you so very much.
It can be really hard to “look up” answers – when ya don’t really know how to ask the question.
Thanks for being patient!
Your help is worth more than I could pay!

Jory – THANK YOU!

It does appear that this will work!
I can’t thank you enough – as I wouldn’t have known how to write the add_filter for this.

Thanks again!
You’re awesome!

Chris

Hi Jory –
We have a single installation.

Yes, I also tried: Restrict access by Role
– same result — it does not restrict our Site Manager role

And, I tried: Restrict access by Capability –same result —
– I tried different caps that our Site Manager role does not include, (i.e. update_core and update_plugins), but I haven’t yet found one that will work. . I did not try every single one. I’m happy to try more – if that is helpful ?

The “Hide field from UI” – does hide it from Site Managers, but it also hides it from admins, so that doesn’t work.
Similarly, the “Make field ‘Read Only’ in UI” – makes it “read only” for admins too.

I also tried selecting multiple “Restrict Access” options simultaneously, but I did not find any ‘combo’ that would work (not that I’ve tried every possibility, there could be lots of combos available – so if there’s a combo that you would suggest – I’ll give it a go.)

Perhaps there is a way – to Restrict Access – via user ID ?
— if so, I would need to enter more than one userID – as we have more than one admin.

I could add a function to our child theme . . . although I’d likely need some help writing it – my PHP skills are minimal.

Let me know – if there are more ideas that I can test?

Please forgive my ‘additional question’ — I started a new topic for it instead.

Thanks for the info. I did finally manage to get it working – using Pods templates.

One thing that I found frustrating . . .
When attempting to use the “Restrict Access” for a field — it turns out that I can’t restrict access to “Admins” — (nor could I use other options) — because one of our Roles includes the capability: “delete_users” — so that role can’t be ‘restricted’.

Is that how it is designed to work?

Wow – thanks for the super quick reply!
Your answer – about it not being written to unassign makes perfect sense.
AND – your suggestion works!

I created a new group – “No Forums Access” Group . . . and set it to be assigned for the user role ‘suspended’ . . .
And it works perfectly!
THANK YOU!!!!

• This reply was modified 5 years, 1 month ago by bckaz.