1. I recently started using the Gutenberg editor, and can no longer see my wordpress revisions which normally show up in the RH settings bar between Trash and Permalink. I disabled plugins and discovered that the revisions only disappear when Toolset Forms is activated. Please advise. Thank you!
2. I attempted to create a new user to grant you access, but as I have some toolset User fields that are "required" (associated with each user) the normal WordPress route to create a new user won't work - I get error messages above each required toolset field saying the field is required, and I am unable to create the new user. Please help on this too as I can't grant access otherwise!
Starting with the second question, when you define fields as required then they are required. If you don't intend for them to be required for all users then you can specify which roles the field group the fields belong to should be assigned to.
In this case, for example, you would not want the field group containing these required fields to apply to administrators.
About the second question, I'm trying this out on my own test site, and at first it looked like I could reproduce the problem. Without any plugins active I made some changes to the Hello world! post so that I could see there were revisions. Then I activated some Toolset plugins in turn, including Forms, and found that the post revisions link had disappeared. So then I tried to do the same again being careful to note the exact steps for reproduction, and then it worked regardless of what plugin I had activated. (Right now I have just Forms active, and I can see the revisions no problem.)
It looks to be something temperamental, possibly with Gutenberg itself, but I will keep trying to find steps to consistently reproduce and I'll get back to you.
1. I'm going to have a lot of non-administrative users that I will be creating - but I don't want them to have to fill out the required field until they get to the page where the form appears. Sounds like I won't be able to manually create users with this in mind. Is this correct? If so, then requiring fields would never be a good idea... which means a user can skip the field on the page which I don't want. A dilemma...
2. I look forward to any additional insight you can discover about the disabled Revisions. I will also continue troubleshooting and post back if anything new emerges.
If you want to be able to create users in the backend and not be subject to completing required fields, but you do want them to be required when submitting front-end forms, then you'll need to have them not marked as required (because when they are required they are required both on the backend and frontend).
FYI I received another report about post revisions, and after investigating further I determined it happens specifically with post types registered with Types.
