I've updated to Forms 2.1 and am really disappointed to find we no longer have access to a lot of useful fields.
IMAGE 1 shows to form content toolbar as it used to be (with the Fields & Views button) and IMAGE 2 shows it as it is now (no Fields & Views button).
So, pre 2.1, if I wanted to add the required shortcode to display the post title of the parent post, for example, I would select 'Fields & Views', then pick Post Title from the items listed and I'd get the options displayed in IMAGE 3 where I'd make a selection. We can't do that now. If I select the new 'Add Fields' button instead, I can still select the Post Tile (although having i renamed to post title Title is really confusing) but none of the old options are available (see IMAGE 4).
I really don't understand why you would remove access to the Standard WordPress Fields at all as it removes access to all data relating to the post author.
I noticed the same when updating to Forms 2.1 and mentioned the absence of the Fields and Views button to the Forms developer.
He had removed it because of a perceived ambiguity in which post the fields referred to (i.e. the post where the form is inserted or the post the form is creating) in an effort to simplify the UI.
I agreed we could wait for any client feedback before making any decisions—and now we have some.
I'll go back to them and suggest discussing reverting the changes.
I also don't see any progress on the question of adding back the conditional output button on the notifications body editor, I'll ask about that at the same time at the meeting in the morning.
I'm escalating this thread, the developer agrees to restore the Fields and Views button and an internal ticket has been created for this.
In the meantime, you should note there is a "Toolset shortcodes" button in the toolbar you can use to generate shortcodes and then paste where required.
Regarding the conditional output button issue, I'll just comment here that this is also with the developers. The technical issues that necessitated its removal were resolved with Forms 2.1. They want to thoroughly test that the conditional shortcode works correctly in various scenarios, and if so will go ahead and restore as well.
