I am trying to create a custom taxonomy archive page but it seems that a recent update introduced a conflict between the Elementor Pro and Toolset Blocks plugins. Neither plugin is able to output a view for the category archives unless the other plugin is disabled.
Link to a page where the issue can be seen:
hidden link
(You'll need these credentials as the site has privacy mode enabled currently: u/n rodlimb p/w communicating-love )
I expected to see:
The view output from either plugin. (Ideally I'd like to build the archive using Elementor Pro.)
Instead, I got:
No output. Only the header/footer are displayed with no content area between them.
Hello,
I have tried the URL you mentioned above, but I see only a blank page, since it is a compatibility problem, please follow our document to provide a copy of your website in below private message box, you can put the files in your own google drive disk, and share the link.
https://toolset.com/faq/provide-supporters-copy-site/
Thanks for the details, I am downloading the files, will update here if there is any found.
Here are what I found:
1) According to our document:
https://toolset.com/documentation/user-guides/using-toolset-with-elementor-page-builder/design-archive-pages-for-custom-post-types/
The workflow for designing archive pages with Toolset is different than the one for creating templates with Elementor.
So it will produce conficts if you use Toolset and Elementor pluins to design the taxonomy archive page.
2) For example, if you want to design the category archive page using Toolset, you can try these:
1) Dashboard-> Templates-> Saved Templates,
2) Find and trush both template:
- Category Archive
- Main Blog Archive
Or change them to other archive page, exlude the category archive page
Hi Luo! Thanks so much for taking the time to look into this. I didn't realize that there was a content template assigned to my Reviews CPT archive from the toolset side. I didn't mean to create that association, which is what was causing the conflict. Thanks for helping me to know where to look to resolve the problem.
I've unassociated all content templates from the reviews archive, and that solved the problem for me.
