• Resolved deforeman

    (@deforeman)


    Hi Mark!
    Your brilliant Sticky Menu Plugin quietly stopped working after more than three years.

    It is still visible, sitting gracefully on the homepage, but not moving with the scroll.

    Mine is a “custom” (version 99.9), and not the standard plugin, so I imagine that a theme upgrade or WP version change is to blame.

    Can you help?

    Dennis Foreman

    • This topic was modified 6 years ago by deforeman.
    • This topic was modified 6 years ago by deforeman.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Senff

    (@senff)

    A bit tricky to give support with a customized version (since I’m not sure what parts you customized) but I can take a quick look. Can you turn on Debug Mode for a bit?

    Thread Starter deforeman

    (@deforeman)

    Mark,
    I did not customize the plugin; you supplied a customized version, and, cautioned me not to upgrade it.

    I’ve turned on the Debug mode, what next?

    BTW, I too have forgotten why we customized the plugin ??

    • This reply was modified 6 years ago by deforeman.
    Thread Starter deforeman

    (@deforeman)

    Here is a grab of the developer console. Hope it helps…

    `content.js:4 [Deprecation] chrome.loadTimes() is deprecated, instead use standardized API: nextHopProtocol in Navigation Timing 2. https://www.chromestatus.com/features/5637885046816768.
    (anonymous) @ content.js:4
    content.js:5 [Deprecation] chrome.loadTimes() is deprecated, instead use standardized API: nextHopProtocol in Navigation Timing 2. https://www.chromestatus.com/features/5637885046816768.
    (anonymous) @ content.js:5
    copyscape-seal-white-120×100.png:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
    jquery-migrate-3.0.0.min.js:2 JQMIGRATE: Migrate is installed, version 3.0.0
    jquery-migrate.min.js:2 JQMIGRATE: Migrate is installed, version 1.4.1
    custom.js:1 Uncaught TypeError: $(…).find(…).addClass(…).end(…).superfish is not a function
    at HTMLDocument.<anonymous> (custom.js:1)
    at i (jquery.js:1)
    at Object.add [as done] (jquery.js:1)
    at a.fn.init.n.fn.ready (jquery.js:1)
    at custom.js:1

    Senff

    (@senff)

    The error you’re seeing is likely keeping my plugin from executing properly.

    However, this error is related to Superfish. Can you see if that can be solved first before we dig into it?

    Also, with the debug option on, the yellow bar stays stuck at the bottom of the page, is that what you needed?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Brilliant Plugin Stopped After 3+ Years’ is closed to new replies.