EDIT: this is only an issue for a particular user that's reached out to me. I've tested with random other users with the same 'Editor' role and it's not an issue for them. There is nothing unique to this particular user. I've tried re-assigning the role and it doesn't seem to make any difference. I've also cleared the cache multiple times.
Hello,
After applying various updates to WordPress and Toolset I'm having an issue with a particular CPT built with Toolset (Press Releases). (On a Multisite) only the SuperAdmin role is able to see the Toolset field group when the Block editor is selected. Other roles are not able to see the group as a Panel option at all. The only workaround being switching to the Classic editor, at which point the field group shows up in the Screen Options section.
Troubleshooting steps I've taken:
-- Disabling the Editor entirely for this particular CPT fixes the issue, but I do need the Editor, so it's not a solution
-- Changing "Post editor: Editor choice per post" fixes the issue for existing content, but new content requires switching to the Classic editor for the Toolset field group to appear, which means extra steps to first save the CPT and then switch
-- Adding an entirely new field group to the same CPT - no issue for the new filed group to show up even when using the Block editor (the old field group still not showing up though)
-- Tested other CPTs with their own field groups - no issue
Is this a known bug or potentially something getting corrupted on my end? I can re-create the field group, but I'd having to deal with exporting and importing all the custom data for the existing content.
Thanks!
Hi,
Thank you for contacting us and I'd be happy to assist.
We haven't received any other report similar to this, so this will require some troubleshooting.
Can you please share temporary admin login details, along with the name of the missing custom field group? Also, as this is apparently, happening for only a particular user, also include that user's username and password.
Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.
regards,
Waqar
Thank you for sharing these details.
As this issue is being experienced only by a particular user, it suggests that it relates to something off in this user's metadata or settings. Have you tried adding a new 'Editor' role user or recreating a new user for the one that is affected?
(i.e. you can delete this affected user and then add a new one in its place)
To investigate this further, at the database level, I'll need your permission to download a clone/snapshot of the website.
Thanks for looking into this.
I wouldn't be comfortable deleting the user, as they are a major content publisher and linked to the PublishPress Authors, so I'm doubt that I can safely re-add them and still have content properly linked to them.
Not sure downloading a snapshot would work either, as it's 45+GB Multisite, and the particular sub-site is not the default site.
Anyway, after further troubleshooting with the Filed Groups, I added a test Group, which did show up for the particular user. Adding a new field to the troublesome Group didn't make a difference either, but what FINALLY did make a difference was altering the name of the group itself! It really required a change or addition of a character to make it work. Seems like a bug to me.
Thank you for sharing these results.
I don't see this change on the development website, so you must have tried that on the production one.
Changing the name of the field group would have reset the preferences of the panel display settings for that particular user, which would explain why it starts showing. Without the database access, that's the only logical explanation I can think of.
Yes, I found the solution on the production site. I also tried renaming the group back to what it used to be, but that un-reset the permissions for the user and I was back to square one. The only solution was renaming the group for good.
My issue is resolved now. Thank you!
