Problem:
The user is able to preview a page with a view inside of it, but once he publishes the page, he gets a different design.
Solution:
The user was creating the page with the same slug as the custom post type, which is used in the archive URL. Once he changed the slug of the page, everything works as expected.
Problem:
The user would like to make some optional custom fields required in a Toolset form.
Solution:
Currently, the required-ness of a field in a Toolset Form comes from its field's settings in Toolset->Custom Fields. Our developers are aware of this limitation and there is a feature request to allow implementing it independently of the fields settings. I am adding this ticket as a vote to the developers' board.
In the meantime, you can implement one of the following solutions:
Hiding the submit button until all fields have content. You can wrap the submit button inside a conditional group that will check that all the fields have values.
Problem:
The user has created a content template but it is not being used in the frontend.
Solution:
It turns out that the user's theme does not have a proper template to display single posts(single.php or single-{cpt-slug}.php).
The default template index.php does make any calls to the_content() function from WordPress.
After creating a single.php file that contains the_content() call, the content template was correctly used in the frontend.
