I enabled the setting:
tvs_below_content to move the TVs below the content input field in the Document Tab.
The problem that I'm seeing is as follows:
I have a resource with a template that has multiple TVs of different Type, organized in a couple of categories. Now when I use any other TV input type before using the tinyMCE input type, the content in the rich text field is not saved.
If I use the rich text field first and save after editing, it works ok.
This is definitely not a major bug, but it's somewhat inconvenient for my clients to adhere to this restriction.
I am using:
I enabled the setting: tvs_below_content to move the TVs below the content input field in the Document Tab.
The problem that I'm seeing is as follows: I have a resource with a template that has multiple TVs of different Type, organized in a couple of categories. Now when I use any other TV input type before using the tinyMCE input type, the content in the rich text field is not saved.
If I use the rich text field first and save after editing, it works ok.
This is definitely not a major bug, but it's somewhat inconvenient for my clients to adhere to this restriction.