[Résolu] Help with setting up page with link to child page
This support ticket is created Il y a 7 années et 8 mois. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
HI here is a basic rundown of what I am trying to achieve.
I have a CPT "advertiser". There are various custom fields in this ctp of which one is business-card (slug) this is an image field.
My objective is to create a view with a parametric search that will show the Business card images on a page that is being filtered by the taxonomy advertiser-category (slug) being a taxonomy on the advertisers. (achieved)
This is the results i have achieved. There are currently only two advertiser loaded on the system hidden link
here is the code for filter editor this view "business-card-search-form":
(I might add div tags to start the formatting process but that should not impact this query.
The idea is then that the business card image must then open the Company profile when clicked on. The id for this page is "315". This page is working correct it just needs to be filtered by the above output.
hidden link
I just need assistance with the correct steps to achieve this.
I am attaching a screen print of both the view under discussion .
Regards
Your parametric search is returning advertisers and in the loop output (via the linked content template) you are displaying the matching advertisers, except you are not displaying the whole advertiser post, just the business card custom field and the 'company' custom field.
But for each of those the matching advertiser is the current post in the loop.
Does this mean it is alway advisable to keep you relationships as flat as possible? Does that then mean if you can keep it to one Post type with more field to will be easier to develop future functions than more than one Post type with a relationship between them?
It keeps things simpler if you can achieve something using custom fields on a post rather than establishing relationships between post types, and anywhere you have access to a post you can access its post meta data (the custom fields).