Title: Plugin Conflict
Last modified: May 20, 2019

---

# Plugin Conflict

 *  Resolved [Michael Aronoff](https://wordpress.org/support/users/masterk/)
 * (@masterk)
 * [6 years, 12 months ago](https://wordpress.org/support/topic/plugin-conflict-236/)
 * Since the latest update of 5.2 with new security features the plugin has a conflict
   of some sort.
 * Before 5.2 everything worked fine. However since 5.2 I can no longer save pages
   or posts with both your plugin active. If I disable your plugin everything works
   once again.
 * Have you had this reported by others and do you think an update with a fix will
   be coming soon?

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Aaron Landerkin](https://wordpress.org/support/users/alanderkin/)
 * (@alanderkin)
 * [6 years, 12 months ago](https://wordpress.org/support/topic/plugin-conflict-236/#post-11552241)
 * Thanks for letting me know. This is the second report of a bug with this symptom,
   but the first one that is linking it to WP v5.2.
 * If it is indeed the same bug that was already identified; then a fix is in place
   and will be uploaded in the next update which will be in the next week or two.
 * In the meantime, the bug comes from jQuery namespacing. If you’d like to try 
   it and not wait for the update, you can edit the `seotoolset/templates/post-widget.
   php` and replace the entire `<script></script>` block at the bottom with this:
 *     ```
       <script>
       (function(b, c, s, e, o){
         SEOToolSet.events.bind('post-widget');
   
         c('#ajax-post-meta-description[data-ajax-load]').each(SEOToolSet.events.elementAjaxLoad);
   
         function run() {
           if (c('[data-ajax-load]:visible').length < 1) {
             setTimeout(function(){ run(); }, 500);
           } else {
             SEOToolSet.events.bind('post-widget');
           }
         }
         run();
       })(document, jQuery);
       </script>
       ```
   
 *  Plugin Author [Aaron Landerkin](https://wordpress.org/support/users/alanderkin/)
 * (@alanderkin)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/plugin-conflict-236/#post-11585368)
 * I believe this should be resolved with the latest update.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Plugin Conflict’ is closed to new replies.

 * ![](https://ps.w.org/bruce-clay-seo/assets/icon.svg?rev=2078825)
 * [Bruce Clay SEO WP](https://wordpress.org/plugins/bruce-clay-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/bruce-clay-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/bruce-clay-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/bruce-clay-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bruce-clay-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bruce-clay-seo/reviews/)

## Tags

 * [jquery](https://wordpress.org/support/topic-tag/jquery/)
 * [pages](https://wordpress.org/support/topic-tag/pages/)
 * [posts](https://wordpress.org/support/topic-tag/posts/)

 * 2 replies
 * 2 participants
 * Last reply from: [Aaron Landerkin](https://wordpress.org/support/users/alanderkin/)
 * Last activity: [6 years, 11 months ago](https://wordpress.org/support/topic/plugin-conflict-236/#post-11585368)
 * Status: resolved