Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter cvf

    (@cvf)

    Solved.

    .menu_bar .current_page_item > a:hover, .menu_bar .current_page_ancestor > a:hover {
        color: #FFFFFF !important;
    }

    Had already tried this but left out !important; Doesn’t work without it.

    Thread Starter cvf

    (@cvf)

    Thanks for the effort. I’ve found changes to WeaverII much more challenging than previous versions – especially for menus.

    Changing the code above to #FFFFFF makes the text white all the time, so it will not show up at all unless you hover. I tried adding `.menu_bar .current_page_item > a: hover, .menu_bar .current_page_ancestor > a: hover {
    color: #008C82 !important;
    }`
    to no avail. I’ve tried repeatedly to style both .current_page_item and .current_page_ancestor, but I don’t understand the structure of the CSS the way it’s written in Weaver II and can’t get it to change anything.

    Here’s a screengrab of the settings I have for Weaver menus. I’ve removed all other custom CSS I’ve tried. The complete code (at least what I’ve been able to find) in the Weaver stylesheet is:

    [131 lines of CSS moderated as per the Forum Rules. Please just post a link to your site.]

    Thread Starter cvf

    (@cvf)

    Thanks, zeaks. I should have been more specific with my question. You’ve definitely identified the problem, but the real issue is that I haven’t found a way to fix it that only changes the color on hover. CSS help is what I really need here.

    Thread Starter cvf

    (@cvf)

    Thanks so much. That worked perfectly and helped me figure out how to fix an unrelated issue on another site.

    Thread Starter cvf

    (@cvf)

    If anyone else has this problem, I was able to solve it by adding z-index:0; to the bottom of the style in wp-cycle.php. Now reads:

    [Code moderated as per the Forum Rules. Please use the pastebin]

    Thread Starter cvf

    (@cvf)

    Downloaded the new index file and still do not see the require command. Did realize that when I move it to the url without /blog, it is pulling an older header.php file. Set to the the /blog url, it uses the correct header.php file. Looked through all of my files on the ftp and I can only find one header.php file, which is the correct one. Cleared my browsers history and cache repeatedly, so I’m completely lost at this point.

    Thread Starter cvf

    (@cvf)

    Yes, following those exactly, except I’m having to manually input<?php require('./blog/wp-blog-header.php'); ?> because there is no require in the index file. (There’s a link to the original index file in my first post.) When I set it up the first time before the site crashed, the require code was in there and I just edited it, but now it’s gone. If it seems completely out of whack, I can try downloading the original theme and manually inserting that index file, I guess. Would that mess up the site if I replaced the index file via ftp? Thanks for all your help.

    Thread Starter cvf

    (@cvf)

    All of my WordPress files are at https://www.visitcvfarm.com/blog. If I leave the blog url at https://www.visitcvfarm.com/blog, I have a right sidebar on my main post page and no sidebar on any of the other five pages created through wordpress (the way it’s supposed to be). When I move the blog url to visitcvfarm.com and put the index.php in my root directory, every page (the main post page and the other five wordpress pages) shows the sidebar.

    Thread Starter cvf

    (@cvf)

    Thanks. I reviewed that section and added <?php require('/the/path/to/your/wp-blog-header.php');?> The site now works from visitcvfarm.com, but it added the right sidebar to every page instead of just the blog page. I can switch the blog address back to the wordpress directory /blog, and the sidebar goes away. Any thoughts?

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