Basically - it does not work. The content editor flags up errors about finding the module name. I've scoured the forums here and found multiple posts that have different formats for invoking this tag and a related "module" tag. Very confusing for a newbie. So is the documentation fundamentally wrong or am I missing something here?
@SteveHTM , could you post more code? i dont feel like i am getting the full picture
HubSpot’s AI-powered customer agent resolves up to 50% of customer queries instantly, with some customers reaching up to 90% resolution rates. Learn More.
Well, I'm not sure what extra code woudl be helpful here. I'm trying to reference the custom module in the <additional head markup> of a blog page template. All other tags I have used in this markup work just fine, and I can see the data they contain in the blog post page via "widget_data" dict references. But when I try and add the custom module I see:
Basically, I can't see how this response - referencing the use of a {% module %} tag - can be accepted as a solution for inadeqaute documentation and/or support on a potentially related but different {% custom_widget %} tag. Is one of these tags deprecated in some way?