Most cardinal rules of “real” programming apply to CSS and HTML, too. One is to avoid magic numbers, like hard-coded ˂form˃ IDs, and use names instead. →
Starting from the new v22, use x-user- headers to pass any secret stuff to FlowBoost. Custom headers don’t show up in the Marketo Activity Log, so only Admins know about them. →
You probably know that email addresses are teeeeeechnically case-sensitive but, like most sensible creatures, you treat them as if they’re case-insensitive. (As Marketo Smart Lists obviously do!) Wouldn’t →
💡This code does not work in any version of Internet Explorer, as it relies on URLSeachParams and Custom Elements v1. An earlier post showed how to append form field values →
Clearing the Munchkin cookie does one thing, and does it well. But chances are you want this other thing, too. →
Velocity is in essence a way a more “sugary” way to write Java, and has almost nothing in common with with JavaScript. But even I forget sometimes and think it plays by JS rules. →
Marketo gets curiously angry when you try to add <style> elements in the Rich Text Editor, though such elements can make strategic sense. They don’t apply the same punishment to <script> elements nor custom elements, so that gives us a workaround. →
Call it an unwelcome feature, call it a bug, call it a security vulnerability. Whatever you call it, here’s how to call it off (mostly). →