Support » Themes and Templates » Where does one start to purge ALL that is weaver from WP3.1

  • Resolved Wudman


    Weaver 1.5.4 and our the Weaver Slider has somehow jacked up my ability to display in the primary menu location or a change was hard coded into my site.

    I can change themes and display secondary menu if the theme allows. Atahhualpa works. If I delete Weaver via WordPress and double check the folder is gone, when I re-install Weaver, my Primary location refuses to display menu. I have no CSS snippets installed but there is some code that was brought to my attention by another user:

    <div id="nav-bottom-menu">
    <div id="access" role="navigation">
    <div class="menu-header">
    <ul id="menu-secondary" class="menu">
    <li id="menu-item-405" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-405">. . . . . . . .

    [Please post code snippets between backticks or use the code button.]

    using firebug for firefox I found this information out.

    This is found around LINE 142 of your main page, inline, so you probably have CSS snippets added somewhere…

    #access {
    display: none;

    Any direction on this appreciated.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Bruce is All Powerful Thank you Bruce. As soon as I am finished eating crow and humble pie I will repeat triple check advanced options a hundred times.

    This problem has been solved – there was in fact a CSS snippet added to hide the primary menu.

    But Weaver does have a “reset” button found near the bottom of the Advanced Options page that will reset Weaver back to the default.

    In general, Weaver will retain your old settings in the database, and this almost always is a good thing. It means that you can switch themes, or upgrade to the newest version of Weaver, and all your old settings will still be there.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Where does one start to purge ALL that is weaver from WP3.1’ is closed to new replies.