求助：Soliloquy插件出现Uncaught TypeError错误，更换jQuery版本无效

I’ve run into this exact error a handful of times with Soliloquy, so let’s break down the most likely fixes that go beyond just swapping jQuery versions:

• Verify script load order
  This error almost always happens when either jQuery loads after Soliloquy’s scripts, or the specific instance script for your slideshow (soliloquy_14) isn’t loading at all. Use your browser’s DevTools (Network tab) to check:

  1. jQuery loads first (look for jquery.js?ver=1.12.4 or similar)
  2. Soliloquy’s core script loads next
  3. The instance-specific script (something like soliloquy-14.js) loads last
     If the order is wrong, check your theme’s functions.php file—make sure Soliloquy’s scripts are enqueued with jQuery as a dependency using wp_enqueue_script('soliloquy', 'path/to/soliloquy.js', array('jquery'), 'version', true);

• Rule out plugin conflicts
  Other plugins can overwrite jQuery or interfere with Soliloquy’s namespace. Try disabling all plugins except Soliloquy, then reload the page. If the error goes away, re-enable plugins one by one to find the culprit. Common offenders include optimization plugins that minify or defer scripts incorrectly.

• Check your Soliloquy instance
  The soliloquy_14 reference points to a slideshow with ID 14. Double-check:

  1. This slideshow actually exists in your Soliloquy dashboard
  2. The shortcode or template tag on your page is correct (e.g., [soliloquy id="14"] not a typo like 144 or 4)
  3. The instance hasn’t been deleted or corrupted—try creating a new test slideshow and adding it to the page to see if the error persists.

• Clear all caches
  Caching plugins (like WP Rocket, W3 Total Cache) or CDNs often hold onto old, broken script versions. Clear your site cache, browser cache, and any CDN cache you’re using. Sometimes even server-side caching (like from your host) can cause this, so reach out to your host if needed.

• Reinstall Soliloquy
  Corrupted plugin files can cause weird script errors. Backup your Soliloquy settings first, then uninstall the plugin, download the latest version from your account, and reinstall it. Import your settings back and test again.

• Check for jQuery noConflict issues
  Some themes enable jQuery’s noConflict mode, which changes how scripts access jQuery. If your theme uses this, make sure Soliloquy’s initialization code is wrapped in a compatible wrapper:

  jQuery(document).ready(function($) {
    // Soliloquy's init code here
    soliloquy_14.soliloquy();
  });
  

  You can add this snippet via a custom JS plugin or your theme’s custom JS section to test.

内容的提问来源于stack exchange，提问作者WebBGW