W3 cache possible conflict with Qode Minimum and drop-down menu

Hello @magdamunro

Thank you for your inquiry and I am happy to assist you with this.
It would be awesome if you could share our website URL so I can check and confirm this.
I am not sure which settings are enabled in W3 Total Cache in General settings, so please disable the settings one by one in Performance>general settings, save the settings and purge the cache after each setting is disabled, and see which one might be causing the issue?

I have already disabled all settings and this doesn’t help. Only inactivation helps. This issue seems more involved. I’ll investigate further what are the differences with this menu.

Hello @magdamunro

Thank you for the information. Have you made sure that after each set is disabled the settings are saved and the cache is purged? This is most likely related to Minify as I don’t see which other settings may be causing this.
If the case is true as you are saying, there must be a conflict with some other plugin so try disabling other plugins while W3TC is enabled and see which plugin may be causing the conflict.
Thanks!

On further investigation and analysis this problem seemed related to jQuery. It took me quite a while to realize the situation with jQuery in the WordPress platform and that W3 Total Cache has a setting for this. As far as I know I haven’t touched this setting, but “Disable jquery-migrate on the front-end” was checked.

The odd thing is that I understand it as jquery-migrate is NOT enabled by default and you need to explicitly enable this, otherwise you’re running the jQuery coming with your WP. However, as I didn’t run “Enable jQuery Migrate Helper” before I was under the impression I was running the current WP version. Using this plug-in does indicate at least one removed call in my theme, but it also indicates I’m running the latest jQuery. As far as I understand it, this would be so since quite a while and this menu was working before. I have to go back to check.

As removing the Total Cache plugin did NOT fix the issue —?I had to remove the “cache” and the “w3tc-config” folders manually —?this still doesn’t explain why this was active. Or does an uninstall warrant I find the settings W3 Total Cache has changed? I did turn off all cache functions before uninstalling. This wasn’t sufficient, you think?

To comment on your follow-up I didn’t see before posting as the page was open:

I always purge the cache, though possibly not when disabling it. I’d assume once a cache function is disabled it’s not functional anymore. This is not so?

I have naturally already disabled ALL other plug-ins to arrive at that the “Minimum core” plugin is involved. It’s possible this is indeed making use of jquery-migrate, but if so I was unaware of this. I’ll investigate further.

Hello @magdamunro

Thank you for the explanation.
This is what I meant about every setting, one by one in Performance>General settings, not just caching modules.
Glad to know you found where the issue was and you should keep this disabled in your case.
Not sure how this remained checked, however, and we can address some things with “Deus ex machina”
Thanks!