I am trying to create a wordpress archive in toolset. I have done this hundreds of times before in other websites but on this site I am using the Full Site Editor based on the Twenty Twenty Four theme. This theme contains an "All Archives" template.
I have created a custom taxonomy called "Listing Categories" that is related to the custom post type "Listings". So my expectation is that when a user clicks on a listing category, they will see all Listings within that category in the format specified in the Toolset WordPress Archive I created called "Listing Categories Archive" which is set to post archives "Listings"
For example: hidden link should display a loop of all Listings that fall under that category.
But for some reason it is only showing content based on the All Archives theme template. I have tried creating templates in the FSE including "archive" and "taxonomy" but they don't seem to work with the Toolset WordPress Archive I created.
From the FSE, I created "Listing Category" template and I can edit that template which DOES work, but this is not the Toolset WordPress Archive but the Theme's version of the archive. So I don't have access to the toolset features such as search, pagination, and html formatting, etc.
Is this true for CRED as well? I noticed that when I create a cred form link from within a custom post, it redirects to the page which has an editable form rather than append the page with the cred form
For example I expect to see this URL:
hidden link (which contains the editable form)
but instead I see this hidden link (with an editable form allowing me to edit any listing. Yikes)
New threads created by Minesh and linked to this one are listed below:
As per our support policy - we entertain only one question per ticket. This will help other users searching on the forum as well as help us to write ticket resolution summery for original issue reported with this ticket.
For those viewing this later, my work around was to use the FSE to edit the all archives template. From there I added my own blocks and even used types short codes in custom html block to achieve the desired look. So this ultimately works as a replacement but I would rather keeps views and archives within the Toolset areas rather than spread out between toolset and Full Site Editor.