This would prevent users from futilely attempting to use rich text tokens (which seem to force <p> tags on you) when all we're trying to do is (for example) insert/modify some text that you do NOT want surrounded with <p> tags.
David, I've put at least 300 characters in a text token and it merged OK (didn't wrap however). What is the current limit and what do you think it should be?
We removed the p tags from the rich text token over a year ago but I do see that the problem has resurfaced. I consider this a bug and will look at fixing it.
Also, Cheryl — when you say you removed the <p> tags, does that mean the text is literally wrapped with nothing? So I should be able to wrap it with <span> tags and it'll display in line with surrounding rich text? Thanks for the help!
I just came across your response while looking for a solution to p tags being inserted into my rich text tokens. Still a bug 3 years later? Any solutions?
We enabled a feature (a while back) in admin that allows you specify whether or not you want the <p> tag to display, as some templates require it while other do not. To get this feature, you need to be using the new Rich Text Editor. You can configure your subscription to use Rich Text Editor 2.0 if you have Admin rights.
Thanks for the fast response, Cheryl. I was just reading about that -- wasn't sure if it was just the email editor or if it applied to the token rich text editor, too. Glad to know it works across the board! Thanks again!
.png)