<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Local Module Development: “host_template_types” property is being replaced with “content_types” in Developer Announcements</title>
    <link>https://community.hubspot.com/t5/Developer-Announcements/Local-Module-Development-host-template-types-property-is-being/m-p/913996#M596</link>
    <description>&lt;P&gt;Hello, today is 2024, Jan 30th and the `&lt;SPAN&gt;content_types` property is not available yet on our environment.&lt;BR /&gt;&lt;BR /&gt;It was stated that:&lt;BR /&gt;Starting January 29th, 2024, all accounts will begin referencing this new property when assessing if a module will be available for use within areas inside of HubSpot&lt;BR /&gt;&lt;BR /&gt;This is annoying because we then have a lot of errors `&lt;SPAN class=""&gt;Error: &lt;/SPAN&gt;&lt;SPAN class=""&gt;CSS and Javascript are not allowed on email modules` when trying to push to our QA Hubspot environment. It's like `content_types` is not considered at all.&lt;BR /&gt;&lt;BR /&gt;Do you know when `content_types` will be usable?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jan 2024 14:44:59 GMT</pubDate>
    <dc:creator>PierreND</dc:creator>
    <dc:date>2024-01-30T14:44:59Z</dc:date>
    <item>
      <title>Local Module Development: “host_template_types” property is being replaced with “content_types”</title>
      <link>https://community.hubspot.com/t5/Developer-Announcements/Local-Module-Development-host-template-types-property-is-being/m-p/888722#M569</link>
      <description>&lt;H2&gt;What’s Changing and why?&lt;/H2&gt;
&lt;P&gt;The &lt;CODE&gt;host_template_types&lt;/CODE&gt; array property for modules is being replaced with the &lt;CODE&gt;content_types&lt;/CODE&gt; array property. The new &lt;CODE&gt;content_types&lt;/CODE&gt; property is more robust and will allow for greater specificity regarding where modules can be used. Possible values for &lt;CODE&gt;content_types&lt;/CODE&gt; include:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"ANY"&lt;/CODE&gt; = Any of the areas listed below&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"LANDING_PAGE"&lt;/CODE&gt; = Landing pages&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"SITE_PAGE"&lt;/CODE&gt; = Site pages/templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"BLOG_POST"&lt;/CODE&gt; = Blog posts/templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"BLOG_LISTING"&lt;/CODE&gt; = Blog listing templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"EMAIL"&lt;/CODE&gt; = Emails and Email templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"KNOWLEDGE_BASE"&lt;/CODE&gt; = Knowledge base pages/templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"QUOTE_TEMPLATE"&lt;/CODE&gt; = Quotes templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"CUSTOMER_PORTAL"&lt;/CODE&gt; = Customer Portal templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"WEB_INTERACTIVE"&lt;/CODE&gt; = Web interactives&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"SUBSCRIPTION"&lt;/CODE&gt; = Subscription templates&lt;/LI&gt;
&lt;LI aria-level="1"&gt;&lt;CODE&gt;"MEMBERSHIP"&lt;/CODE&gt; = Membership templates&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If a module is not to be used in any area within HubSpot, you would set the value to an empty array &lt;CODE&gt;[]&lt;/CODE&gt; instead of &lt;CODE&gt;["NONE"]&lt;/CODE&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can view these values on our &lt;A href="https://developers.hubspot.com/docs/cms/building-blocks/modules/configuration" target="_blank"&gt;Configuring a Module&lt;/A&gt; page within the &lt;A href="https://developers.hubspot.com/docs/cms" target="_blank"&gt;developer documentation&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below is an example of the new &lt;CODE&gt;content_types&lt;/CODE&gt; property in &lt;CODE&gt;meta.json&lt;/CODE&gt; of a module:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;{
  "global" : false,
  "host_template_types" : [ "PAGE", "BLOG_POST", "BLOG_LISTING" ],
 "content_types" : ["SITE_PAGE", "BLOG_POST", "BLOG_LISTING", "QUOTE_TEMPLATE", "WEB_INTERACTIVE"]
  "module_id" : 136785808220,
  "is_available_for_new_content" : true
}
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;What will happen to my existing modules?&lt;/H2&gt;
&lt;P&gt;Existing modules will not be affected initially as updates to the &lt;CODE&gt;host_template_types&lt;/CODE&gt; property will sync to the &lt;CODE&gt;content_types&lt;/CODE&gt; property allowing it to be updated accordingly while this change is rolled out. Developers should begin adopting this new property as the new values for &lt;CODE&gt;content_types&lt;/CODE&gt; indicated above will not be available for the legacy property of &lt;CODE&gt;host_template_types&lt;/CODE&gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;When is this happening?&lt;/H2&gt;
&lt;P&gt;We are gradually rolling out this change over the next few weeks. Starting January 29th, 2024, all accounts will begin referencing this new property when assessing if a module will be available for use within areas inside of HubSpot (Email editor, Website page editor, etc…).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2023 16:05:39 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Developer-Announcements/Local-Module-Development-host-template-types-property-is-being/m-p/888722#M569</guid>
      <dc:creator>AJLaPorte</dc:creator>
      <dc:date>2023-12-04T16:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Local Module Development: “host_template_types” property is being replaced with “content_types”</title>
      <link>https://community.hubspot.com/t5/Developer-Announcements/Local-Module-Development-host-template-types-property-is-being/m-p/890934#M573</link>
      <description>&lt;P&gt;Any clues as to what&amp;nbsp;&lt;SPAN&gt;WEB_INTERACTIVE might include?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Dec 2023 09:07:55 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Developer-Announcements/Local-Module-Development-host-template-types-property-is-being/m-p/890934#M573</guid>
      <dc:creator>SSharples</dc:creator>
      <dc:date>2023-12-08T09:07:55Z</dc:date>
    </item>
    <item>
      <title>Re: Local Module Development: “host_template_types” property is being replaced with “content_types”</title>
      <link>https://community.hubspot.com/t5/Developer-Announcements/Local-Module-Development-host-template-types-property-is-being/m-p/913996#M596</link>
      <description>&lt;P&gt;Hello, today is 2024, Jan 30th and the `&lt;SPAN&gt;content_types` property is not available yet on our environment.&lt;BR /&gt;&lt;BR /&gt;It was stated that:&lt;BR /&gt;Starting January 29th, 2024, all accounts will begin referencing this new property when assessing if a module will be available for use within areas inside of HubSpot&lt;BR /&gt;&lt;BR /&gt;This is annoying because we then have a lot of errors `&lt;SPAN class=""&gt;Error: &lt;/SPAN&gt;&lt;SPAN class=""&gt;CSS and Javascript are not allowed on email modules` when trying to push to our QA Hubspot environment. It's like `content_types` is not considered at all.&lt;BR /&gt;&lt;BR /&gt;Do you know when `content_types` will be usable?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2024 14:44:59 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Developer-Announcements/Local-Module-Development-host-template-types-property-is-being/m-p/913996#M596</guid>
      <dc:creator>PierreND</dc:creator>
      <dc:date>2024-01-30T14:44:59Z</dc:date>
    </item>
  </channel>
</rss>

