Home › Forums › Support › Help with Block – Content Template Scenario: Passing 3rd-Party Form Through
- This topic has 9 replies, 3 voices, and was last updated 3 years, 4 months ago by
David.
-
AuthorPosts
-
December 13, 2022 at 1:24 pm #2460910
Tom
- I have a Custom Post Type for Company Management.
- The CPT contains Custom Fields.
- And is governed by a GP Elements>Content Template.
One of the fields – in the CPT is an oEmbed which pulls in a JotForm Contact form (per employee CPT). I use oEmbed purely because that choice made the form appear in my CPT.
The Form appears, as it should, in the CPT.
But I can’t figure out HOW to get the forms to appear through the Content Template (as it should).
Or do I need to approach it differently?
That’s it! Thanks!
December 13, 2022 at 6:23 pm #2461063Fernando Customer Support
Hi Tom,
How are you grabbing the oEmbed field value in your Content Template currently?
We may need to try a different approach.
December 14, 2022 at 10:13 am #2461921Tom
Really Fernando, I have just been grasping at straws hoping one GP element might work.
- In ACF – it is assigned to an oEmbed field.
- In the Custom Post Type (the team members) – it appears properly in the back-end.
- Apologies if this is redundant to this point. :^)
- In my Content Template – I have tried a few things and then erased them as they did not work.
- I started with a Heading element – just to see if it cared what proxy was there – knowing it was going to resolve the form in the code.
- Then tried other things (the Dynamic Data link in a separate container in the Content Template). Currently – I have an empty container just pointing to the meta data – in hopes that worked. But it did not.
Looking for suggestions. Thanks!
December 14, 2022 at 5:21 pm #2462241Fernando Customer Support
I see. Can you share admin login credentials? I’ll check your structure and assess how to address this?
Please use the Private Information field for this.
December 15, 2022 at 10:06 am #2463173Tom
Thanks for taking a look! Really appreciate it.
December 15, 2022 at 5:17 pm #2463511Fernando Customer Support
Hi Tom,
Have you tried retrieving it through a Dynamic GB Headline Block to see if that will work?
If not, can you try that first?
If it doesn’t work, you’ll likely need to retrieve it manually.
December 16, 2022 at 8:43 am #2464381Tom
I tried that once and it did not work (I tried everything before writing). Tried it now – and it works (obviously – go figure).
- BUT – is renders as collapsed (probably a mobile view?). See link to image below.
- In dev tools – nothing I check, or uncheck, seems to be making a difference.
IMAGE LINK:
Embed Form Width not container width.December 18, 2022 at 4:35 am #2465827David
StaffCustomer SupportHi there,
select the Headline Block that you used to display the oEmbed.
In its Spacing settings you have it set toInline Widthcan you de-activate that.
That will ensure the headline does not restrict the width of the iframe.Final piece is to give the
iframea width as it it currently has none.
This CSS will do that:iframe { width: 100%; }December 19, 2022 at 7:00 am #2466947Tom
David – I worked through it yesterday – then forgot to reply to this thread.
- In the Custom Fields – I switched to the WYSIWYG editor as the field to receive the Jotform form.
- In the Content Template – I used the Dynamic Headline & Post Meta.
- In the CPT – I used the iFrame code within the WYSIWYG editor.
It all worked without having to add any CSS.
IF there is something inherently wrong with my approach – let me know and I will revisit it.
Thanks for the help!December 19, 2022 at 7:03 am #2466951David
StaffCustomer SupportCan’t see anything wrong with that approach. Glad to hear its working and thanks for sharing that!
-
AuthorPosts
- You must be logged in to reply to this topic.