Is there any way I can modify the below code (currently used to filter View results by post type), so the View only shows post types as defined by either a shortcode, or where it is placed?
Solution:
The client have found another workaround with custom codes:
Problem: are there known limitations for importing from CSV?
Solution: It is possible to import post relationships and relationship field values with CSV imports. Some general CSV import limitations:
- Data in serialized formats is not importable. This includes certain field types like checkbox groups, skype fields, and fields that store multiple values.
- Date custom fields must be converted into Unix timestamp format to be usable by Toolset.
- Very large imports can put a heavy strain on your server.
Each CSV import plugin has its own feature set, more or less configurable with a built-in GUI.
The issue here is that the user wanted to Link posts of the same CPT in a relationship.
Solution:
This is possible if you enable the hierarchical relationship on your CPT. If you go to Toolset->Custom Post Types and edit your cpt, under the options tab you should see the Hierarchical option to allow for your CPT have parent/child relationship amongst itself using the default wordpress relationship.
It functions the same as if you were to go to Pages and set another page as its parent.
The issue here is that the user wanted to disable the wrapper div around their view.
Solution:
You can completely removing this div by enabling this setting "Disable the wrapping DIV around the View".
However it should be noted that you can disable this DIV, but you will not be able to use some of the functionality that Views offer such as AJAX updates and Pagination.
In the GUI available on the backend such as Toolset Shortcodes > Fields and Views > Post/Taxonomy View or the Fields and Views button in the Views loop editor.
Views appear to be shown in the order they are created. Is there any way to change this to alphabetically order for example?
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
