If I am copying and pasting in my local template design and Marketo throws the "Validation Error" how the !@*& am I supposed to know what line that error is on? This is driving me insane trying to debug this thing.
Whats even more insane is I will comment out a line I think might be throwing the flag, and the validation clears. Then I will uncomment, and get the error. Then I will comment out again that *same* line and get the error again whereas it cleared the first time!
Solved! Go to Solution.
You mean "Validate Syntax" in the marketo menu? That's what is throwing the error, along with trying to approve and close the editing template window. The problem is it doesn't say what line the error is on, and with a LP template with over 1000 lines of code and 60 lines of marketo variable tags, it's a little difficult to locate exactly what is causing the error.
I just got another error for unique ID tags and that one actually highlighted the error (to my delight!) The issue must be with the error type. If I get the error:
There is no code highlighted showing where the variable declaration error is. I finally figured out that it was where I was trying to use "RGBA(255,255,255,0)". I debugged by commenting out line by line default marketo meta variables until I got a clean validation. Related to this question here. Unfortunately, it looks like RGBA(255,255,255,0) doesn't work...
As an added pain, you have to wait a hot second for marketo to auto-save before validating. If you deleting the offending line and immediately hit validate, your still gonna get the error, making debugging even more challenging. I think this is why I was getting the early issue mentioned in the initial post:
"Whats even more insane is I will comment out a line I think might be throwing the flag, and the validation clears. Then I will uncomment, and get the error. Then I will comment out again that *same* line and get the error again whereas it cleared the first time!"
the fact that it takes a couple of seconds is because Marketo has to save your draft before it can validate it. When you hit the validate button too quickly, it is fact validating the previous version.
OK, got it. The <meta> variable declaration is the culprit.
We usually set the opacity with 2 variables. One is the color itself. The second is for the opacity and can be a toggle (that will render 0.5 if on and 1 if off) or a picklist that will render a few values between 0.1 and 1.
The CSS will look like this:
But Greg, if you look at my example in the related thread, setting rgba as the default works in my simple test. Something's not being communicated right, I think.
On the other thread, you are using a mktoString Variable. Here I am using a mktoColor. And my understanding is that Douglas is having issues with the RGBA in a mktoColor.
Now I fully agree that the mktoString solution is probably the simpler one , but then, no color picker.