Hi again Waqar,
>Thank you for sharing these details and we have very pleasant weather here 🙂
I'm pleased for you, here the spring is finally coming.
>I see that your website has a post-relationship between the same post type "Product". This is something that is not supported in Toolset and a relationship can be created only between two different post types.
>I'm not sure exactly how you managed that and it must have something to do with the manual import, but, I'll not recommend using this unsupported approach, since it can result in unexpected results, going forward.
Well... I'll knew you said that. At the time I did the import (by a custom code), I was not aware it was not allowed, so I did it 🙂 And it 's working really well. I can add product, add related products, delete then, no worries.
>An alternative of grouping related products together can be to add a new custom post type "Product Collections" and create a 1-to-many relationship between "Product Collections" and "Products" post types, so that one collection can have multiple products.
I should has done this way.
>This will allow you to show all products, which are related to the same product collection, through a post view.
I believe you are telling me that there is no solution? 🙂 Is there a way to simply display what I /see/ in the posts products pages ? I can see the related product.
I admit I really don't understand Toolset views (I know programming languages and SQL but the view interface is really unclear to me. It's something for non programmer users. I don't understand the 'logic'). I don't want to 'loop' into products, just display the related products as its already done at the bottom of the posts products page...
I don't know how to do something which is definitly not a loop but simply a SQL extract for specific output which I need.
2. Post View and content template:
>An important point to remember is that generally, it is not recommended to mix the content generated through different page editors/builders, as it eventually leads to compatibility issues, in the long run.
I agree. But Elementor is the best WP production tool the WP community ever seen. Anyone who has discovered Elementor is not affected by Gutemberg.
>a). Our recommended approach is to attach the Toolset content template (and not Elementor's template) to single post pages. And
This is impossible given the above elements.
>b). If you'd prefer to keep working with Elementor's template attached to single post pages, as they are now, then you should be using the classic or legacy views, which use shortcodes instead of the blocks.
I've tried, without success. So my message.
>( you don't have to install Toolset Views for this as the same features are also available from within Toolset Blocks too )
>You can go to WP Admin > Toolset > Settings > General and select the option "Show both the legacy and Blocks interface and let me choose which to use for each item I build" for the editing experience.
>After that, you'll see the option to add classic views from WP Admin > Toolset > Views.
Done, really good trick.
>You'll find the guides on using the classic views here:
>https://toolset.com/documentation/legacy-features/views-plugin/
>https://toolset.com/documentation/user-guides/views/
I've seen theses docs but can't understand how to display a choosen image from a text field content. So my previous message (again).
Waiting for your ideas, I'll read again trying to understand the Toolset philosophy 🙂
All the best from Oleron Island - France (and sorry for my english)
Stef
