{"id":12909096,"date":"2020-05-29T08:49:49","date_gmt":"2020-05-29T08:49:49","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/plugin-javascript-conflict\/"},"modified":"2020-05-29T08:49:49","modified_gmt":"2020-05-29T08:49:49","slug":"plugin-javascript-conflict","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/plugin-javascript-conflict\/","title":{"rendered":"Plugin Javascript conflict"},"content":{"rendered":"<p>I&#8217;m posting to ask if you are likely to be doing an update on your plugin for compatibility with  WP 5.4.1 in the near future.<\/p>\n<p>Reason for asking is that we&#8217;ve identified a javascript conflict between ACADP and our SiteOrigin Custom CSS plugin. Here&#8217;s the detail of their report:<\/p>\n<p><em>&#8220;To avoid a conflict with the color picker we use, we intentionally disable wp-color-picker when viewing WP Admin &gt; Appearance &gt; Custom CSS. This is normally fine as no other plugin affects WP Admin &gt; Appearance &gt; Custom CSS but acadp-admin.js is set to enqueue (read: output) on all admin pages and it&#8217;s resulting in this issue. A resolution to this issue might be to add a screen check for the enqueue of acadp-admin.js.&#8221;<\/em><\/p>\n","protected":false},"template":"","class_list":["post-12909096","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/12909096","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/12909096\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=12909096"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}