pardot | Pardot API library for building custom CRM connectors | REST library

Something like this oughta do the trick.

I could get jsonp working with this one, it isn't as old as the one you are using. I would test it first with a working example (like the url I am using).

Try this : //li[@id='ember943']

If you're not entirely sure if the form is an iframe element, you could try targeting the form's fields using CSS and using dynamic width and height values such as width: 100%; instead of something like width: 250px;, which will automatically resize your elements to fit the available width. This will take care of the horizontal scrollbar.

For the vertical scrollbar, you could try targeting the scrollbar with psuedo properties to manipulate it's style or hide it altogether. You can read more about it here:

https://css-tricks.com/almanac/properties/s/scrollbar/

It's worth noting though, that this approach isn't highly recommended, due to it's limited support across different browsers and platforms.

However, in the case of this specific vertical scrollbar, it appears to be a height or padding issue on the form's container, so you could target that with @media queries to make it more responsive across devices.

I hope this helps!

What Pardot is suggesting is to create 2 static URLs on your own server that return a simple JSON response.

So for example:

1. mysite.com/pardot-success

Returns: {"result":"success"}

1. mysite.com/pardot-error

Returns: {"result":"error"}

You'll then use those two URLs as your success and error redirect URLs for your Pardot form handler settings.

An AJAX request can then be made to your Pardot form handler using JSONP, which will wrap and return the JSON response from one of those URLs (depending on the result).

Your AJAX response data would include your JSON result (success or error).

I managed to get a response from Pardot support, and they have confirmed that such response filtering is not available on the Visits API. I asked for a feature request, but hardly any chance to get enough up-votes to be considered :(

The problem you're hitting with MimeKit giving you an error about failing to parse the headers is due to the fact that your string is missing the message headers.

What you're effectively doing is asking a MIME parser to parse a message starting half way into the message. You're giving it an impossible task.

You need to combine the original message headers with the above string to produce the original (complete) message source before you can parse it.

Either that or you have to fake the original message headers so that things parse correctly.

Presumably you have the original message headers somewhere in your database?

Does the QuotedPrintableDecoder method need to come into play? I've reviewed http://www.mimekit.net/docs/html/Working-With-Messages.htm, but I'm hoping I don't have to manually traverse each part and there's still a way to grab just the message body.

There's generally no need to use any of the low-level decoders (or encoders) yourself.

There are multiple ways to get the message body:

1. Traversing the MIME tree manually (but in general I wouldn't recommend it), but to do this you really need to understand how MIME is structured and how common mail clients will structure their messages. It's not something I would generally recommend unless you are well-read on MIME. (Difficulty: Extreme)
2. Using a MimeIterator. For the most part, I wouldn't bother with this approach unless you want to manually traverse the MIME tree structure without using any sort of recursion. Where this class really comes in handy is if you are implementing something more akin to an IMAP server. Again, you need to understand how MIME works to really make use of this. See the documentation for a simple example on how to use this. (Difficulty: Extreme)
3. Using a MimeVisitor subclass to traverse the MIME tree structure. For a good example on how to do this, I would recommend taking a look at the HtmlPreviewVisitor class in the example in the documentation. This is probably the best way to do things if you want to "render" the message like a mail client might. (Difficulty: Moderate)
4. If all you want is the quick & dirty way of getting a message body and you don't care about trying to render the message the same way Outlook or GMail do, then you can use the MimeMessage.TextBody and/or MimeMessage.HtmlBody properties. (Difficulty: Easy Mode)

If I were you, I'd probably choose between the TextBody/HtmlBody properties and using something similar to the HtmlPreviewVisitor class in the example docs. They will be the simplest way to accomplish what you want to do.

Okay so this seems to work:

You can pass the default as a parameter to the function, and return that in your conditional operator instead of "":