Good question, maybe he has chosen a completely different template type that leads to this. I can only speculateā¦ but Iām pretty sure that the template type and therefore the conditions are not correct.
Thanks for coming back, I didnāt realise the functionality didnāt exist so that would explain why. It just seemed quite odd that itās clearly able to pull in the posts when you search, but not before hand based on the post type settings, which made perfect sense to me given youāve told Bricks what that template is for.
The other comment you made I also noticed, but even with the archive settings being offered, it was the previous point I was struggling with in why it wasnāt showing the post type posts I wanted you see.
No idea on that as I definitely had the template types set correctly in Bricks for archive and single, and when viewing the pages you could see they were loading the single post content 
Did you tick the custom post type in the bricks settings?
1 Like
On another thread now dude but thanks for helping. I didnāt tick it as I only wanted to use Bricks for the main CPT template and not single pages, not allow it to edit the custom post types individually (which gets even messier when clients get involved).
It seems itās not something that is offered but Iāve raised why I think it would still be good to have, unless I use a tool like Assistant Pro from the Beaver Builder guys to fill that page management gap.
Thereās definitely something not quite right with that content population drop-down. I just ran in to the same issue where I couldnāt get any of my CPT posts to appear in the drop-down (even after searching). Came back to it later and it magically started to populate with some of the CPT posts Iād created. Initially the CPT was set to not publicly queryable and also excluded from search, but I changed both of those.
I know itās an old thread, but I just stumbled upon a similar problem. My CPT wasnāt available in the select and searching for it, even with the exact title, didnāt return it. In my case, the post type had exclude_from_search set to true. When I changed it to false, it started working. This shocked me as I donāt see any reason why posts excluded from search in the frontend shouldnāt be able to populate content when creating a template. Is this the desired behavior?
Thereās already an improvement request: WIP: Link internal page/post to cpt page with "exclude from search" - #6 by timmse
1 Like