It likely worked with CB Content Bot 3.x because it would reverse the htmlspecialchars applied to the code since you were using < and >. My guess is it's actually your WYSIWYG editor that's applying escaping or wherever you're saving that code has escaping built into its store behavior. Since CB Content Bot 4.x no longer reverses htmlspecialchars it'd explain why it doesn't work anymore. Since your workaround no longer looks like an HTML element I'm guessing that escaping is no longer applied by the editor. At any rate thank you for providing your solution!