Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
For what it's worth, I grabbed the code you posted and created a new template in Marketo and then spun up a new email asset from that code. I didn't have any issues with editing the Button Text or URL and wasn't able to recreate this glitch on my side. I'm not sure if it's the case for you, but I've...
It's very likely that this rule is removing the padding for your button from 0-480px viewports (on mobile). form.mktoForm, form.mktoForm * {padding:0px !important;} You could try adding a line of CSS to set the padding for your button at the bottom of the media query to help preserve the button pad...
Thanks for keeping me honest here Sanford, I'm always learning a little something more from you -- appreciate it!
All buttons on all Marketo forms should natively have the "mktoButton" class built into them. This might not exist if you're using a script to strip classes or something like that, but it should be a fairly reliable selector to script against. Another option would be to build a selector in the conte...
I feel your pain here, I've run into similar issue with the filter bar in the file tree since Marketo updated to the new UI for the file tree a while back. I think what's going on here is that the search feature uses an older "version" of Marketo and does the querying differently than what's going o...
You could use a "mktoString" variable to set the URL for the background image. I normally set this up using the "background" property in CSS so that you can also include things like color and linear-gradients (or even multiple images, or combos of all the above). First you'll want to setup the strin...
@Disha_Goyal6 -- where did you find this chart? It looks like a handy reference and I'd love to add it to my resources if you don't mind sharing? Thanks.
You might think about using a class like "text-link" on the parent element (
I'm not aware of a way to change the Fallback page at the asset level using the Set Expiration feature -- this seems like an obvious gap in the design here and maybe would make for a great Idea to suggest in the community? I'm not sure if it's as good of a solution as you're after here, but let's as...
This is the expected behavior for modules in the Email 2.0 editor as well as any content inside of an editable area (.mktoText) in a Guided Landing Page template. You're on the right track here with pulling in new modules to replace the existing versions in each of your email assets and then updatin...