SanfordWhiteman

Franklin, I think you're highlighting two non-issues and one real one.Non-issue: People enter identifying info into a form on a formally shared -- or illicitly borrowed -- computer. You are not responsible for the consequences of this kind of stupidity recklessness. It's like a family or company s...

You could build a webhook to return a match (stored in a 3rd field)... if that's in your wheelhouse.

Building a photo gallery display would be a separate front-end and back-end task. On the front, your developer could use any number of slideshow libraries that are out there. To load the images out of Marketo, since they are being uploaded to a protected area (i.e. they are fields on the lead, and...

OK. Consider that the referral process consists of two data storage steps. Storing the new lead (the referral) in Marketo as you would any new lead, also including the referrer's email address as a field on the referral's lead record.Augmenting the referrer's lead record with information about the...

Depending on the size (in KB) you expect for the final image, you can exploit the technique I described here. Note you will have to have (or be) a skilled front-end developer.

It's funny because I was working on exactly that task when you posted!

You absolutely do not want to add forms2.min.js twice.

That's pretty fragile code to unescape entities, IMO. How about:function unescapeEntities( str ) { var tmpEl = document.createElement('SPAN'); tmpEl.innerHTML = str; return tmpEl.innerHTML;}

Nate, the general pattern here is what we can call Post-Map-Repost. After the form's first submit (in the onSuccess handler) you remap the field values so that a different lead (the referrer) owns the form, then post it again. An example is here and I know I linked to this demo in an earlier Commu...

You said there was a long list of blocked resources for your domain. Are these resources like "forms2.min.js"? That has no effect on SEO.