Hello,

After updating to Admin Columns Pro 7 we have a list screen where the configured columns are no longer registered for users with a custom role, while another list screen on the same site works correctly for the same users. I have already ruled out the usual suspects, so I am sending the isolated facts rather than a generic report.

I have seen the forum topic “Issues with Toolset fields & other plugins after updating”, where Stefan suggested handling these cases by email. What I describe below may or may not be related to those reports.

ENVIRONMENT
– WordPress 7.0.2
– Admin Columns Pro 7.1.1 (updated from [previous version])
– PHP 8.3.32
– Toolset Types for CPTs and custom fields
– Custom role “funzionario” (author-like capabilities). This role cannot be changed: it is what limits each agent to their own records.

SYMPTOM
On the list screen for CPT “cliente”, users with the funzionario role see only the native WordPress columns. None of the columns configured in Admin Columns appear. In Screen Options, the column checkboxes are not present at all, so the user cannot even toggle them. An administrator sees the full configured set on the same screen.

NOT AFFECTED
On the list screen for CPT “immobile”, the same users do see Admin Columns columns, including Toolset custom field columns. So the behaviour is not uniform across screens.

ALREADY RULED OUT
– Column set assignment: every column set is explicitly assigned to every role on the site.
– Plugin state: uninstalled, reinstalled, deleted the configuration and rebuilt it. No change.
– Stale user preferences: created a brand new user with the funzionario role and no prior user meta. Same behaviour, so this is not a leftover preference pointing at an old set ID.
– Deleting and re-adding the individual columns on the affected screen: [outcome to be filled in].

QUESTIONS
1. In version 7, what determines whether a column is registered for a given user on a given list screen? Is there a capability check involved beyond manage_admin_columns, which as far as I understand only governs access to the settings screen?
2. Can a difference in the capabilities a CPT is registered with (capability_type, map_meta_cap) cause Admin Columns to skip column registration entirely for non-administrators on that screen?
3. Is there anything in the v7 refactor of column registration that could produce this asymmetry between two CPT screens on the same site?

I can provide screenshots, the CPT registration arguments and a staging copy if useful.

Thanks,
Stefano Thiella