Before answering your questions, let me describe some WordPress and Toolset concepts that are important for understanding and fixing this issue.
- WordPress: Posts are the basic data model in WordPress. And they can be from different types. Pages, posts, attachements, views, content templates, archive templates, RFGs are all posts from different custom post types. They are stored in the wp_posts table, and their custom fields(or metadata) are stored in the wp_postmeta table.
- Toolset: An RFG is a hidden custom post, with a one-to-many relationship to its parent post type.
- Toolset: A content template is meant to display only ONE post, whereas a view is meant to display a list of posts.
- Toolset: We can use views inside a content template, and we can use content templates inside views. We can use views(or content templates) inside other views (or content templates).
This being said, I'll try to answer each of the questions below:
when you say "the current view is corrupt" do you mean that the "Content Template" is corrupt?
I meant the view inside the content template. The view that will query the posts of the RFG that are linked/related to the parent post. Check this screenshot hidden link
Because RFGs are a custom post type, we must use a view to display them, instead of a shortcode or a regular block(single field block). For that reason, we create a new view or we reused an existing view with a View block, to display the values of the RFG.
what is happening when a toolset user puts an RFG into a "content Template that they are building. Are they "putting" a sub Content Template into a parent Content template?
The only way to display RFG inside a content template is using a view. We need a view inside the content template. Inside the view's loop, we can insert a content template(meant to display each post from the RFG)
Now, about the Database. I have access. and i have found the entry with the key 'usage' for post_id=3312. see screenshot attached. Do i just hit Delete?
Yes, you can delete it. Or change the meta_key "usage" to something else like "__usage". It is equivalent to deleting it from the view's perspective.
If this fixes the problem will I still have the option of using Toolset Blocks or Toolset Views?
Toolset Blocks and Toolset Views are basically the same. They are two editing experiences, and you can use either of them or both. Currently, the legacy editing experience(Toolset Views) has more features than the new editing experience(Gutenberg and Toolset Blocks). For example, Toolset Blocks do not support user views and taxonomy views yet.
I hope this answers your questions and gives more insights about Toolset. Let me know if you have any questions.