Archived topic
Beta feedback for GP Premium 2.0
12 replies · Started by Antoinette on April 6, 2021
Hello!
I've been testing this with Pods and custom post types.... and while it is entirely possible that I am being very dim, is integration with custom post types created through Pods missing? I feel like I might be missing something really obvious, but I can't see a way to use the custom fields as dynamic sources for custom post layout templates.
Hi there,
I'm not sure I fully grasp what you mean.
If you're trying to display the custom field from a post you should be able to set something like this.
https://share.getcloudapp.com/kpuKYAPe
acf1 is a custom field slug from ACF but the same works for custom field slugs from PODs or any plugins.
Just make sure your display rules are correct for where you're trying to display it.
No I mean, when creating custom post types [https://pods.io/docs/learn/what-are-custom-post-types/] with Pods and setting some additional input fields for those.
That's actually what I was going to point to.
I actually made a demo. Check this page:
https://dev-generate-press.pantheonsite.io/news/
On this page is a post list with is layout modified by a Block Element Template.
The post "CPT Bird from Pod #1" is a custom post type created with PoDs. The text Pods custom field 1 for Pod bird #1 below the title is actually taken from a PODs custom field.
Now perhaps I still misunderstood what you meant. If that's the case, I'd like to ask for more details on this. (purpose, functionality, layout, etc)
Whew, yes, that's how I expected it to work.... but.... it turns out............I was missing something REALLY obvious...it might just be me being foolish, but in case it is useful feedback...what I was missing here was the following:
1. Dynamic calls only work with Generate Blocks (I know that's super obvious, I actually worked that out before but it's worth mentioning again :-)
2. If the input type in Pods is set to paragraph - then it must be changed on the GenerateBlocks Headline Element to be a paragraph too (again, very obvious to me now).
Thanks for your patience :-)
1. Dynamic calls only work with Generate Blocks (I know that’s super obvious, I actually worked that out before but it’s worth mentioning again 🙂
Ah right yes. I should've mentioned that. That's on me. My bad. :)
2. If the input type in Pods is set to paragraph – then it must be changed on the GenerateBlocks Headline Element to be a paragraph too (again, very obvious to me now).
Yes, that's how it's done.
No problem. Glad to be of any help. :D
The second one is actually the more confusing part from a UX POV - because the Element is called Headline - I never thought to look there. Might also just be me :-)
Can't wait for it to be released 'properly'.
The second one is actually the more confusing part from a UX POV – because the Element is called Headline – I never thought to look there. Might also just be me 🙂
Can’t wait for it to be released ‘properly’.
I kinda agree but its quite difficult to gauge if its worth doing a label change for "Headline Block" as some people are already used to it. It may cause confusion. (and bugs on the technical side.)
We'll see what can be done with it. Please look forward to it. :D
The second one is actually the more confusing part from a UX POV – because the Element is called Headline – I never thought to look there. Might also just be me 🙂
Can’t wait for it to be released ‘properly’.
I kinda agree but its quite difficult to gauge if its worth doing a label change for "Headline Block" as some people are already used to it. It may cause confusion. (and bugs on the technical side.)
We'll see what can be done with it. Please look forward to it. :D
Oh last one - I've been getting an "updating failed" lag a few times while creating a content template. This is on a fresh install, with only four plugins running. Are the diagnostic reports in these instances of any use?
Oh last one – I’ve been getting an “updating failed” lag a few times while creating a content template. This is on a fresh install, with only four plugins running. Are the diagnostic reports in these instances of any use?
It's best to post a new topic about it so this topic doesn't get convoluted. :)
On posting a new one, try to include the error log (or maybe a screenshot) and perhaps try to provide what steps were done as well so we could attempt to replicate the cause of the error and observe things. :D
Perfect! It still works after the error, so will keep an export handy for a more comprehensive feedback report.
Perfect! It still works after the error, so will keep an export handy for a more comprehensive feedback report.
Thanks. Let us know. :)
