• Resolved amommy

    (@amommy)


    I saw the previous post but it is more than just an annoyance for new menu positions. It has completely destroyed the look of my main menus drop down list. Could not for the life of me figure out what happened. I was changing some css but nothing I did to the themes css had anything to do with menus. then looking through the code (THANK GOD FOR DevTools) I found the culprit: wp-content/plugins/shortcode-menu/css/superfish.css?ver=3.8.1
    I had just installed the plugin the day before.

    anything with sf- on the page is affected. This is a serious problem as it could and does affect the look of a site, whether or not we are using a menu created by the plugin.
    yes the theme css is overriding SOME elements but not all especially the black backgrounds.
    This is not a problem with your plugin specifically it is a problem with the way wordpress has us making plugins that require very common code, like superfish and jquery.
    A temporary solution to this is maybe add note specifying a SF will affect… that way we can fix the issue BEFORE it breaks the site.

    Here’s the list of items sf affects and are NOT overridden on my theme that I have to add to the css to fix

    .sf menu ul {
    background: rgba(0,0,0,.8);
    padding: 0.5em;
    }
    .sf-menu li {
    white-space: nowrap;
    -webkit-transition: color .2s;
    transition: color .2s;
    }

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Amit Sukapure

    (@amitsukapure)

    As lots of users facing same problem I’ve removed the superfish support from version 2.0.

    Thread Starter amommy

    (@amommy)

    there has to be a way to around it without totally removing it. Not totally sure with how it’s activated but maybe have a check box asking whether or not to use plugins superfish and have it accessed depending on that selection.
    Or more advanced and more work have css options page where users can select their own styles.
    But for sure in the instructions and the plugins options somewhere should be a warning message IF YOU HAVE SUPERFISH… here are the styles in the plugin you should edit… put these in your css and edit… something ..
    Just a thought.
    Thanks

    Plugin Author Amit Sukapure

    (@amitsukapure)

    Yes, I can easily provide an option in the backend to enable or disable superfish. But my point is, if we can achieve same functionality without superfish then what is the advantage of having above option? I think its totally useless. Instead it will enqueue 4-5 scripts and styles and will affect page load time.

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

The topic ‘Superfish Bug’ is closed to new replies.