Hey there!
It’s not currently possible with the plugin, but we could update the plugin to embed HTTPS forms by default if selected. If you’re interested in that, please let me know!
The main issue with inline forms in that they won’t track the prospect appropriately without some additional intervention. As it sits, you’ve got two options:
- Use the embed code from Pardot, and make the URL HTTPS.
- Utilize Gravity Forms (easiest) or your own form code and use form handlers to keep the visitor context.
That help?
Hey Cliff, I think that allowing to embed HTTPS forms would be a great start at least. I’d love to use this plugin and not have to write my own code to integrate the pardot API. How long would that take?
Is inline form embeds in the works? It looks like the code for this plugin was set up for it but the option isn’t exposed. I guess that’s the reason you already mentioned that they need additional intervention in order to track properly. I’d be willing to investigate this and see if we can find a solution together if you think it’s possible. Let me know.
We should be able to add HTTPS support fairly quickly (next week or two).
Inline forms are not currently being worked on, because it creates the need to replicate existing Pardot functionality. The work you see on that option was a bit of a bonus from one of the original developers. 🙂
That would be great, are you going to expose an option to let users pick secure or unsecure forms when they embed? I’d be happy to beta test for you. Let me know.
Seems like it would be more helpful as a global setting, no?
Yea, probably better as a site wide setting. Good thinking!
I wanted to circle back here—haven’t been able to grab the time to make this update. I’m allotting some development time in November. Thanks for you patience.
Thanks for the update Cliff, I’ll be watching for the update. Let me know if you guys want any help beta testing.
Howdy! If you still want help testing, I’ve got a branch that is tentatively working in allowing HTTPS: https://github.com/Pardot/pardot-for-wordpress/archive/1.4.zip
It simply replaces whatever URL is returned with https://go.pardot.com if the “Use HTTPS?” setting is checked. I’ll be testing it more soon, but let me know if you come across any big issues in the meantime. As well, if you fancy GitHub, it’d be great to see an issue created there during development: https://github.com/pardot/pardot-for-wordpress
Oh, and remember to click “Clear Cache” on the settings page after you change it to HTTPS or back to HTTP.
Version 1.4 is live and includes the feature mentioned above.
Thanks for the update! I’ve tested (a little slow), and the 1.4 release fixes the issue.
