plugin conflicts

  • Resolved csgn

    (@csgn)


    6 years ago

    Hello, after the last update there were conflicts plugins.
    Uncaught TypeError: e.addTest is not a function
    at plugins.js:539
    at plugins.js:539
    main.js:289 Uncaught TypeError: $(…).liScroll is not a function
    at HTMLDocument.<anonymous> (main.js:289)
    at i (jquery.js:2)
    at Object.fireWith [as resolveWith] (jquery.js:2)
    at Function.ready (jquery.js:2)
    at HTMLDocument.K (jquery.js:2)
    After disabling this plugin, all errors disappear. When you enable this plugin, the search form stops responding. Please help me with my problem or tell me how to roll back to the previous version. All the information you need to provide. Thank you in advance.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support Blaz K.

    (@blazk)

    Hi @csgn,

    did you clear cache after the update (especially minify)? If not, this could cause issues. For starters, please try clearing cache and then save settings and customization again in the options.

    Blaz

    Thread Starter csgn

    (@csgn)

    Yes, thank you very much. I recently started my work with wordpress and haven’t quite learned how to work with it. Cleaned the cache plugin Fast Velocity Minify and it worked. Thank you again for your quick help. Five stars!

    Plugin Support Blaz K.

    (@blazk)

    You are welcome! It’s a good idea to clear minify and page cache on plugin updates. I’m happy we resolved the issues.

    Thread Starter csgn

    (@csgn)

    Sorry, from words I do not refuse. But the problem remained relevant. I so understand when the plugin of a minification, picked up something. It also conflicts on the page.
    First I cleared the cache Fast Velocity Minify, after the cache on the site, after the cache cnd. Tried in different order, but the problem is relevant. If possible, please give a list of js, I will try to add exceptions for this plugin.

    Plugin Support Blaz K.

    (@blazk)

    Uf, I’m sorry to hear that. Can you please disable minify for couple of minutes just that I check if there are any conflicts with other plugins. This would help to ensure compatibility in future versions.

    URL for JS is: /wp-content/plugins/rate-my-post/public/js/rate-my-post-public.js

    Thread Starter csgn

    (@csgn)

    Disabled the minifier, cleared the cache.

    Plugin Support Blaz K.

    (@blazk)

    I checked, but are you sure that this is connected to my plugin? All errors come from theme’s JS files and Rate my Post seems to work without a problem. It’s a bit hard for me to test this locally since you have a paid theme ??

    Please also try saving Rate my Post settings again. Click on Rate my Post in backend, clear browser cache (shift+f5 in chrome) and then click save.

    Thread Starter csgn

    (@csgn)

    Now disabled the rate my Post – WP Post Rating plugin. The search button works and I noticed that when the plugin disappeared scroll button up. Now disabled the plugin everything works, there are no conflicts. I’m sorry, but I think it was because of the last announcement. If you don’t mind coming in now. About 10 minutes, I’m not going to include after you try to add the script to the exceptions list. You really need this functionality of your plugin. If you still have the old version of the plugin or the ability to roll back to the previous version, I will be grateful to you.

    Plugin Support Blaz K.

    (@blazk)

    @csgn I found out what’s the issue – it’s the modernizr library that conflicts with your theme. Please contact me over Slack and I’ll give you a quick fix until I have the update out.
    Join here:
    https://join.slack.com/t/ratemypost/shared_invite/enQtNTE0MDcyNjg5NTM4LTljNjRjYzRjMGFiOWRhYmM0MWZkYTlmZDQ1MzIyZjM3YzU0N2U1MWRlODM5MjczNmFhZjU1ZDllZTgxOGE3Y2M

    Thread Starter csgn

    (@csgn)

    Many thanks to the author, helped to quickly correct the conflict. Keep it up, more of these. The plugin is super, even more than super. No problem, thread can be closed.

    Plugin Support Blaz K.

    (@blazk)

    Officially fixed in version 2.2.1. You can now update the plugin ??

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘plugin conflicts’ is closed to new replies.