1. I defined a taxonomy term field group "Feldnamen Taxonomie", see upload image 1
2. In this field group, I inserted up to now 2 term fields (see image 2) They are assigned to variouos taxonomies, where I can see the input fields, everything as expected.
3. I then wanted to insert one of these term fields in a view, using the block editor. I select the block type *fields and views", and I then wanted to select in the upcoming window "Add shortcodes fields and views" the term field. But the defined term fields are not displayed in that window (see images "Toolset fields & views part1-4).
4. However, if you look at these print screens, you can see that post custom fields are displayed, but custom taxonomy term fields not.
5. Another observation: in the related blocks in the backend, I can see the taxonomy term fields.
So, as conclusion, the term fields as just missing tn the window "Shortcodes fields and views. Is this a bug, or did I make a mistake?
many thanks for your reply. I understand what you mean, but I do not understand what is a taxonomy view. I am working with BLOCK EDITOR AND NOT WITH VIEWS. Searching on Toolset site for "taxonomy view", almost all search hits are related to nested views (which is not possible with block editor?) and to the view plugin.
So I am used to build views with the block editor based on a custom post content, which may be selected / filtered programmatically or with front-end filters. Filtering may be done by categories or other methods.
see as a working example
hidden link
So can you give me an example of a taxonomy view built with BLOCK EDITOR ? Or is it demonstrated somewhere in your training lessons? I am afraid that I miss something very important in Toolset's methodology, so it would be very important to me to have a example built in BLOCK EDITOR. What is the difference of creating a "taxonomy view" compared to a "normal view" using BLOCK EDITOR??
The thing is that, You can not build Taxonomy/User using Blocks but the workaround would be to create taxonomy view in classic mode.
To create taxonomy view in classic mode, navigate to Toolset => Settings => General Tab => Editing experience Section => Select the option "Show both the legacy and Blocks interface and let me choose which to use for each item I build".
Then once you refresh the page in admin, within Toolset menu, you will be able to see the Views as submenu, from where you should try to Add a new view and create a taxonomy view for your desired taxonomy and then within Loop Editor add your taxonomy custom fields and later try to add this view using "Fields and Text" block.
many thansk for your clarifying answer. I was afraid, that I get this answer. And I am irritated a little bit about the information of Toolset. I am using this excellent plugin since 2 months only, and the recommendation from Toolset is to use the block editor, because this one would be developed further, and views as "old model" of building views would not be updated anymore. This message is in contrast with your statement, that the block editor is not able to fullfill all requirements. Mmh....., very strange.
So I will try to follow your recommendations. I already have activated the settings mentioned in your message, in order to be able to manage the different views. I just have two questions:
1. Until now, I did not acitvate the view plugin. Is the activation mandatory in order to work based on your proposal?
2. You say in your message ...and later try to add this view using "Fields and Text" block. That means, that I create a new view in block editor and I add in the loop the view created with views, right? Is it possible in this way to get a nested view? (but based on Toolset support, it seems to me that nested views have to be build entirely in view's mode),
The thing is that Toolset Blocks is in early life and currently using Toolset Blocks GUI you can create only post type views, taxonomy/user views are not supported yet but we do have plants to add taxonomy/user views to blocks in near future but there is no ETA on it yet but we are really eager to add as many new features as we can to blocks.
1. Until now, I did not acitvate the view plugin. Is the activation mandatory in order to work based on your proposal?
==>
No, Toolset Blocks and Toolset Views plugins are 1:1 copy of each other, just the name are different. So there is no difference if you are using Toolset Views or Toolset Blocks. But at a time you must either install and activate Toolset Blocks or Toolset Views.
Because both plugins offer the settings:
- Show only the legacy interface for designing with shortcodes
- Show only the Blocks interface
- Show both the legacy and Blocks interface and let me choose which to use for each item I build
So, as required we can switch the option, as we require to build view using classic views and Block view, I asked you to chose the setting "Show both the legacy and Blocks interface and let me choose which to use for each item I build" that will allow you to create Views using Blocks as well as Classic mode (from Toolset => Views).
2. You say in your message ...and later try to add this view using "Fields and Text" block. That means, that I create a new view in block editor and I add in the loop the view created with views, right? Is it possible in this way to get a nested view? (but based on Toolset support, it seems to me that nested views have to be build entirely in view's mode),
==>
To display the taxonomy view we will require to create a view in classic mode and then we can add this view at the place where you want.
If you can tell me where exactly you want to display the taxonomy term fields and share problem URL where you already created the existing view I can setup that and that will help you to understand how it works. For that I will require temporary admin access details.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Dear Minesh, thanks for your excellent support. For the moment, this case is resolved for me. I am playing around now with views methods in order to learn how it works, and I am exploring, how I can use this approach.
