[Jon Schroeder]

Yep, perfectly clear! Basically, it's probably not the plugin causing this – the plugin is doing what it's supposed to do, and in fact the plugin itself is just saying "this widget goes on this page," and nothing else (I think, based on how you've described it). The thing that's missing isn't the menu itself – the markup is all there.

Think of it this way: you could move a menu from the primary menu to the secondary menu position (or however you have those labeled) and the same menu would appear, but it would look different. There are different styles in place for each of those locations.

Well, the sidebar is just another location, but there aren't any baked-in styles in place to address the menus, so right now it just displays as a simple unordered list, with submenus as nested unordered lists (ul and li, in the markup).

Baba, I'd be happy to talk through this with you more directly if you'd like; this isn't an offer to do work on your site, but if you'd like, I'll take 15 minutes or so and talk through it with you. Send me an email at [email protected] with a phone number if you'd like, and I'll call you.

[Jon Schroeder]

Try this, then:

@media (max-width:767px) {
.nav-secondary { position:static !important; }
}

See if that does what you're wanting.

[Jon Schroeder]

Hmm. Interesting. A jQuery accordion using the native WordPress menus actually is precisely what's called for here (this is pretty much the ideal way to do it).

Do try one or more of the plugins I'd posted above; they all do things that are pretty much like that. If you're still seeing errors (or if they simply don't work), that is the sort of thing I could probably help you troubleshoot. 95% of the time, the error will be loading jQuery the wrong way either in your theme or in one of your plugins.

Yes, if you're doing the css-only method, the styles will be placed directly into your child theme style.css.

Thanks!

[Jon Schroeder]

Here's a very quick codepen showing you using your markup how this could be achieved with CSS only (which is simpler, by a bit, than adding in that jquery accordion component that the plugins I'd linked added).

http://codepen.io/jonschr/pen/Kkobi

This would be a starting point, not an ending point, because while it does what you want it to do, it isn't very pretty.

[Jon Schroeder]

I can't really provide a ton of direction as far as CSS goes, in all likelihood, other than styling the following elements (this is a starting point). Teaching you enough CSS to do this on your own is really beyond the scope of these forums, I'd think. But here's a starting point for the items you should be thinking of styling:

.menu-recorder-container > ul > li {}
.menu-recorder-container > ul > li:hover {}
.menu-recorder-container > ul > li > a {}
.menu-recorder-container > ul > li:hover > ul {}

To learn to style these, here are a few tutorials:
http://www.devinrolsen.com/pure-css-vertical-menu/
http://webdesign.tutsplus.com/tutorials/orman-clarks-vertical-navigation-menu-the-css3-version--webdesign-5944

Here are three plugins that have been vetted by WPMU which will probably do just about what you're looking for, without doing any styling yourself: http://premium.wpmudev.org/blog/free-wordpress-accordion-menu-plugins/

Hopefully this helps!

[Jon Schroeder]

Could you add a link to your site so that we can see specifically what you're trying to do?

[Jon Schroeder]

I see a button there now which links to the blog. Can you confirm that you're still having an issue with this?

The markup you'll need to add a button is like this:

Button text here!

[Jon Schroeder]

Do you mean, for example, underneath "general info," you'd like a dropdown with the subitems there?

If so, this can be accomplished with some (relatively) simple CSS. Is that what you're trying to do?

[Jon Schroeder]

First, you'll want to be just editing this specific template. So the file to use would be something like single-yourposttype.php, and it should be located in the same folder as your child theme's functions.php file.

More on that here: http://codex.wordpress.org/images/1/18/Template_Hierarchy.png

The content of this file should look something like this:

-------------------------------
<?php

// your functions here, using hooks and filters

genesis();

-------------------------------

So far as using the Genesis column classes are concerned, there are lots of things you can do!
Here's more information on using those: http://my.studiopress.com/tutorials/content-column-classes/

[Jon Schroeder]

Are you wanting that menu to be there, but not sticky, or are you wanting to remove it entirely?

If you'd like to just be rid of it completely, here's a snippet to add at the end of your stylesheet which should hide it for everyone viewing the site at a width below 767px:

@media (max-width:767px) {
#subnav { position: absolute;left: -999px;top: -999px;}
}

[Jon Schroeder]

Try switching to a default (not genesis) theme to see if it's actually the theme causing the issues; I'd guess that it's not, since the admin area css isn't governed by the theme.

I use Genesis and Serverpress and have not run into this issue.

[Jon Schroeder]

Glad to hear that; the function name shouldn't matter, so I'm sure we were using the wrong hook is what happened. What was the right one?

[Jon Schroeder]

Huh. Everything looks right here to me, with the possible exception of the quote marks, if you copied and pasted directly.

I'll take another look at this with fresh eyes tomorrow.

[Jon Schroeder]

So if the include isn't the problem, then something else is. Make sure you're editing the child theme's functions.php file, first of all, and install the visual hooks plugin.

[Jon Schroeder]

Try echoing something instead of including the file. I have a feeling that's the issue. Once you've done that, you could put whatever you like in the function (perhaps the contents of the file), and then just call the function wherever else you want to add it.

[Jon Schroeder]

When you say header, do mean just the <h1> on the page?

If so, the Title Toggle plugin should do the trick.

[Jon Schroeder]

The Genesis Visual Hook plugin may help you to see which hook you'd want to use, but it'll be something like this in your functions.php file:

add_action( 'genesis_header', 'yourprefix_add_secondary_menu', 20 );
function yourprefix_add_secondary_menu() {
// your php code here... e.g. include()...

?>
<!-- or your markup here -->
<?php
}

[Jon Schroeder]

I'm not going to argue the point further after this post, but if your goal is to get your site faster, as the OP had said was his goal, then caching would help with that that.

It may or may not be a worthwhile use of time to set up (and yes, for low-traffic sites it's perfectly fine without), and there very well might be better things that could be done with that time (and of course good content outweighs just about anything else). But in 95% of cases, caching will make your site faster in a way that's measurable; in my experience, in a way that's a significant percentage (30-50%) of the overall load time (and more significantly, I might add, than lossless compression of images, which should make the site maybe 2-5% smaller overall, depending on the number of images being loaded and how large they are).

Here's a complete comparison of some of the more popular caching plugins for WordPress; this should sum up everything quite well and give you a feel for how much faster your site is likely to be with caching vs. without.

[Jon Schroeder]

Apply the background image that's currently on .wrap to .site-header instead (not both), and I think that will do the trick!

[Jon Schroeder]

Using a caching plugin is pretty much a waste of time these days, and tend to cause more problems than they resolve. Back in the day, when broadband had slower speeds, and cheap shared hosting was skimpier on resources, they made a difference. Nowadays, not so much.

No, that's simply false. Caching cuts loads times for my sites on average by 50-70% (I use Total Cache). I'm sure that server-side caching would be even better (this is a good point that @Summer and others made earlier in the thread). It's true that they can cause problems as well (read: it's either set up wrong or you forget to clear the cache when you meant to), but cached is typically significantly, noticeably faster than non-cached, and in particular for sites on servers lacking resources.

For images, if that's an issue on this site, use Imsanity and Smush.it (the yahoo lossless compression thingamajiger). If you're concerned about the Yahoo service going down, EWWW is a viable alternative as well.

[Author]

Posts