I am using Toolset for the first time.
1. I am not sure the exact roll Archive pages will have. As new posts are made to the site, is it the archive pages that are displayed resulting from viewers search?
2. From the Edit View screen > Loop Wizard > "How do you want to display the loop?", what would be the best option selection when using a Divi template?
Hello, let's focus each ticket on one question. I will answer this question here:
1. I am not sure the exact roll Archive pages will have. As new posts are made to the site, is it the archive pages that are displayed resulting from viewers search?
WordPress automatically creates various archive pages for your site. You can use Toolset WordPress Archives to control the design of these automatic archive pages. The search results page is one type of archive page, and there are also post archives like the blog page, monthly and yearly archives, author archives, and so on. There are also taxonomy term archives and custom post archives. Please review these documents for more information about Toolset's WordPress Archives feature:
https://toolset.com/documentation/user-guides/what-archives-are-and-why-they-are-so-important/
https://toolset.com/documentation/user-guides/creating-wordpress-custom-post-archives/
https://toolset.com/documentation/user-guides/create-custom-taxonomies/
Since woocommerce requires its own CPT "Products", would it be possible to establish the Archive page as the "Product" page, or would this create complications?
This is beginning to relate to an open support ticket https://toolset.com/forums/topic/product-page-as-cpt/
I definitely need the primary post Profile Pages for the CPTs that I added to Toolset (painting, ecollage, and collage) to display posts independent of the "Product" CPT in the site URL. A separate "Product" page would serve as the (painting, ecollage, and collage) CPT page summary and link to woocommerce for checkout.
Can the archive and "Product" summery be the same, or would that be problematic?
Since woocommerce requires its own CPT "Products", would it be possible to establish the Archive page as the "Product" page, or would this create complications?
I'm not sure I understand this question, sorry. The Product archive in WooCommerce is usually shown at http://yoursite.com/shop. Each Product usually has a single post page like http://yoursite.com/product/product-title. Can you explain more about what you want to accomplish, using URLs to describe what you want to achieve on each site page?
Can the archive and "Product" summery be the same, or would that be problematic?
Sorry, I don't understand. Can you provide more details?
I need a Landing page, a Profile Page for each CTP page posted and searched, a few static content pages.
Aside from the woocommerce "Product" CPT page, based on what I described for my project, it might help if you could provide an idea or suggestion of how I might use the Archive as a practical example?
Aside from the woocommerce "Product" CPT page, based on what I described for my project, it might help if you could provide an idea or suggestion of how I might use the Archive as a practical example?
Any custom post type can have an archive that shows a list of all the posts in that custom post type. If you have a post type called "Paintings" then each painting will have its own page. There will also be an archive page created automatically by WordPress that contains a paginated list of all painting posts.
Thank you. Now I believe I'm beginning to understand. The Archive posts for the "paintings" CPT can be searched and the results displayed in a certain way and each post links back to the source CPT page?
The Archive Template will display the source CPT page and link?
I need to create a ticket regarding Field, Views, and Taxonomy that may seem very simple but the answer would help explain a great deal to me. Considering that you are already aware of my development objectives, can I create the ticket under How to build a site with Toolset and somehow link the ticket for you to answer?
The Archive posts for the "paintings" CPT can be searched and the results displayed in a certain way and each post links back to the source CPT page?
Yes, that's correct. To add a custom search form to an archive page, you must go to Toolset > WordPress Archives and create an archive to assign to this post type. Then you will be able to design the list of results and add a custom search filter if you'd like. Each result can include a link to the post, the post excerpt, just about anything you would like to add using Types or Views shortcodes.
can I create the ticket under How to build a site with Toolset and somehow link the ticket for you to answer?
Please type only your new question in the next reply and I will be glad to split that question into a new ticket linked to this one and assigned to me.
Regarding the Archive page, currently every static artwork "Detail Page", has a thumbnail image display and link on a static Portfolio Page as can be seen in the attached screenshot.
In the new site development with Divi and Toolset can the Archive posts serve as the thumbnail image link in a portfolio of search results, similar to the way the old static portfolio and thumbnail links?
I'd like to start a new ticket with you on the subject of how to identify project taxonomy. I have read the Toolset documents on Taxonomy but I'm having difficulty identifying the unique Taxonomy that is needed for this project. Is the Taxonomy the title of the page Fields description and behavior, such as Title and Featured Image? Isn't the Taxonomy the nature of the page Fields?
In the new site development with Divi and Toolset can the Archive posts serve as the thumbnail image link in a portfolio of search results, similar to the way the old static portfolio and thumbnail links?
Yes, you can design the loop in a WordPress Archive to include an image and link for each post if you'd like. Views shortcodes can be used to insert the post's featured image, or you can use Types field shortcodes to insert a custom field image.
Hi,
This would be a great solution for the Archive posts to serve as the thumbnail links for the search results. However, it seems to conflict with your feedback from the "Views Display Loop Options" ticket where the options were to use Bootstrap and resolve bugs with Divi or select another option that will require custom CSS for responsive behavior.
Would I need the application of "Views Display Loop Options" to achieve the results in your previous reply?
The two options I mentioned earlier still apply - either you can activate Bootstrap on your site to support a Bootstrap-grid loop, or you can disable Bootstrap, build your own loop, and apply your own custom responsive CSS. In either case, you can insert an image link and title link in each iteration of the loop.
I'm confused because of the following document: https://toolset.com/documentation/recommended-themes/toolset-divi-integration/displaying-fields-inside-any-divi-module/, where Bootstrap is clearly a part of the Toolset, recommended workflow.
After spending a considerable amount of time learning how to use Toolset with Divi, I discovered in a support ticket that in fact Bootstrap is not recommended for use with Divi
Not knowing what now to do, I feel as if I am at a fatal conclusion with Toolset that may have been avoided it the Toolset instructional document had been updated to state that using Divi with Toolset and Bootstrap is problematic and in fact NOT recommended.
After resetting the loop display to Bootstrap grid, to recreate the search portfolio page display results similar to that of the 4 column grid shown in the previous screenshot, if I set the number of columns to 4 in Bootstrap grid options, would this be the correct path towards a responsive display?
if I set the number of columns to 4 in Bootstrap grid options, would this be the correct path towards a responsive display?
I recommend you start by reading the documentation to understand what's happening in a View, and how Bootstrap defines responsive grids:
https://getbootstrap.com/docs/3.3/css/#grid
https://toolset.com/documentation/user-guides/digging-into-view-outputs/
https://toolset.com/documentation/user-guides/view-layouts-101/#bootstrap
