<?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 Wordpress Leadin plugin conflict with siteorigin in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/266499#M23892</link>
    <description>&lt;P&gt;Hi, I've made my wordpress website using &lt;A href="https://siteorigin.com" target="_self"&gt;siteorigin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It was all working fine, but then once I activated the leadin plugin, the editor breaks and I get:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;TypeError: Cannot read property 'post' of undefined
    at i.value (siteorigin-panels-layout-block.min.js?ver=2.10.5:1)
    at i.value (siteorigin-panels-layout-block.min.js?ver=2.10.5:1)
    at zc (react-dom.min.js?ver=16.6.3:146)
    at wc (react-dom.min.js?ver=16.6.3:138)
    at fa (react-dom.min.js?ver=16.6.3:137)
    at gg (react-dom.min.js?ver=16.6.3:135)
    at Ca (react-dom.min.js?ver=16.6.3:133)
    at Object.enqueueSetState (react-dom.min.js?ver=16.6.3:191)
    at r.q.setState (react.min.js?ver=16.6.3:20)
    at r.value (data.min.js?ver=4.2.1:1)&lt;/PRE&gt;&lt;P&gt;I've gone with the embedded form route for now, and the form loads, but it's definitely inconvenient. Is it possible for you to look into this?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 24 Apr 2019 10:05:45 GMT</pubDate>
    <dc:creator>dannio</dc:creator>
    <dc:date>2019-04-24T10:05:45Z</dc:date>
    <item>
      <title>Wordpress Leadin plugin conflict with siteorigin</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/266499#M23892</link>
      <description>&lt;P&gt;Hi, I've made my wordpress website using &lt;A href="https://siteorigin.com" target="_self"&gt;siteorigin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It was all working fine, but then once I activated the leadin plugin, the editor breaks and I get:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;TypeError: Cannot read property 'post' of undefined
    at i.value (siteorigin-panels-layout-block.min.js?ver=2.10.5:1)
    at i.value (siteorigin-panels-layout-block.min.js?ver=2.10.5:1)
    at zc (react-dom.min.js?ver=16.6.3:146)
    at wc (react-dom.min.js?ver=16.6.3:138)
    at fa (react-dom.min.js?ver=16.6.3:137)
    at gg (react-dom.min.js?ver=16.6.3:135)
    at Ca (react-dom.min.js?ver=16.6.3:133)
    at Object.enqueueSetState (react-dom.min.js?ver=16.6.3:191)
    at r.q.setState (react.min.js?ver=16.6.3:20)
    at r.value (data.min.js?ver=4.2.1:1)&lt;/PRE&gt;&lt;P&gt;I've gone with the embedded form route for now, and the form loads, but it's definitely inconvenient. Is it possible for you to look into this?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2019 10:05:45 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/266499#M23892</guid>
      <dc:creator>dannio</dc:creator>
      <dc:date>2019-04-24T10:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Wordpress Leadin plugin conflict with siteorigin</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/266887#M23944</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/16537"&gt;@dannio&lt;/a&gt;&amp;nbsp;, it seems other customers are seeing this issue as well. We will have an update to the plugin on Monday, so we hope this will fix the issue. In the meantime, I'd suggest making sure the HubSpot plugin is the most recent version.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2019 20:13:09 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/266887#M23944</guid>
      <dc:creator>cbarley</dc:creator>
      <dc:date>2019-04-25T20:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: Wordpress Leadin plugin conflict with siteorigin</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/266950#M23952</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/11385"&gt;@cbarley&lt;/a&gt;&amp;nbsp;I only downloaded and installed it 2 days ago, so pretty sure it's the latest version.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 02:37:19 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/266950#M23952</guid>
      <dc:creator>dannio</dc:creator>
      <dc:date>2019-04-26T02:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: Wordpress Leadin plugin conflict with siteorigin</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/267059#M23972</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/16537"&gt;@dannio&lt;/a&gt;&amp;nbsp; got it, there should be a fix rolled out Monday, so let's give it until then and go from there. If the update doesn't work out the issue, I'd suggest calling into HubSpot Support so they can hop on a screenshare with you and use some more in-depth real-time troubleshooting steps with you!&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 15:41:04 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/267059#M23972</guid>
      <dc:creator>cbarley</dc:creator>
      <dc:date>2019-04-26T15:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: Wordpress Leadin plugin conflict with siteorigin</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/267293#M24004</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/11385"&gt;@cbarley&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately, the new update didn't solve my issue. I just updated and refreshed (including cache) and the plugin still breaks.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2019 06:29:32 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/267293#M24004</guid>
      <dc:creator>dannio</dc:creator>
      <dc:date>2019-04-29T06:29:32Z</dc:date>
    </item>
    <item>
      <title>Re: Wordpress Leadin plugin conflict with siteorigin</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/267408#M24024</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/16537"&gt;@dannio&lt;/a&gt;&amp;nbsp;, are you able to call into support or create a web ticket with them so they're able to troubleshoot more effectively? candidly, i'm pretty limited in my troubleshooting steps here from the forums.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2019 16:02:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/267408#M24024</guid>
      <dc:creator>cbarley</dc:creator>
      <dc:date>2019-04-29T16:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: Wordpress Leadin plugin conflict with siteorigin</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/270176#M24403</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/11385"&gt;@cbarley&lt;/a&gt;&amp;nbsp;no need, it seems the most recent update fixed the errors. Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2019 04:10:32 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Wordpress-Leadin-plugin-conflict-with-siteorigin/m-p/270176#M24403</guid>
      <dc:creator>dannio</dc:creator>
      <dc:date>2019-05-15T04:10:32Z</dc:date>
    </item>
  </channel>
</rss>

