• Resolved relish1227

    (@relish1227)


    Hello,
    As a big fan of the Simple Section plugin, I was happy to see someone taking up the reins, as you put it.

    I have a question, however: I have installed both your plugin and the Simple Section one, so I could compare the output. Your plugin appears to render out the full sub-navigation tree. Whereas the SS one only shows the top level, unless you’ve clicked into an item that has children.

    For example, if I go into the top-level page of an About section, here’s how it plays out.

    BSN Widget:

    - History
    - Our Affiliates
    - Our Manufacturers
    - Professional ASsociations
    - Careers
    -- Job Application

    SS Widget:

    - History
    - Our Affiliates
    - Our Manufacturers
    - Professional ASsociations
    - Careers

    I wouldn’t expect “Job Application” to be displayed unless I had clicked on “Careers.” The SS plugin works this way, but it seems BSN does not? Is there a reasoning behind that?

    I suppose I could just control the display by doing:

    li.page_item_has_children ul.children {
        display:none;
    }

    And then displaying the children when that item is active:

    li.page_item_has_children.current_page_item ul.children, li.page_item_has_children.current_page_ancestor ul.children {
        display:block;
    }

    Is that what you intended?

Viewing 5 replies - 1 through 5 (of 5 total)
  • I was about to ask the same question so thanks for this. I have used your code in my style sheet and does the job.

    drywallbmb

    (@drywallbmb)

    Hi @relish1227 and @deputydawg,

    Sorry for the reeeeeeeally late response on this. Our intention was, I believe, to make this plugin functionally equivalent to the old one, with just some improvements and enhancements added on top. So I’m not sure why you’re seeing a difference, but we’ll look into it!

    Thread Starter relish1227

    (@relish1227)

    Thanks! For now I’ve just been updating the styles myself as mentioned.

    drywallbmb

    (@drywallbmb)

    @relish1227 We just pushed a new release that fixes this issue. If you update to 1.0.1 you should be able to remove your CSS workaround.

    Thanks for reporting this issue!

    Thread Starter relish1227

    (@relish1227)

    Woo hoo, thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Question Re: Display’ is closed to new replies.