mikehenden

Hi Tom

Thanks for getting back to me.?I have also replied via email.

After further testing I now have Mega Menu working as expected on my development installation. 

The only thing I can’t figure is why the menu is NOT pushing content down when open, but ‘overlaying’ it on the web page. The ‘Overlay Content’ checkbox on ‘Mobile Menu’ is definitely unchecked!!

Thanks for feedback guys. Yes, it’s possible to do this in CSS only…

/* Navigation
--------------------------------------------- */
.main-navigation {
	display: block;
	width: 100%;
}

.main-navigation ul{
	display: none;
	list-style: none;
	margin: 0;
    padding-bottom:20px;
    padding-left:16px
}
.main-navigation ul ul {
	position: absolute;
	top: 100%;
	left: -999em;
	z-index: 99999;
}

.main-navigation ul ul ul {
	left: -999em;
	top: 0;
}

.main-navigation ul ul li:hover > ul,
.main-navigation ul ul li.focus > ul,
.secondary-menu ul ul li:hover > ul, 
.secondary-menu ul ul li.focus > ul{
	display: block;
	left: auto;
}

.main-navigation ul ul a {
	white-space:nowrap;
    width:100%
}

.main-navigation ul li:hover > ul,
.main-navigation ul li.focus > ul,
.secondary-menu ul li:hover > ul, 
.secondary-menu ul li.focus > ul{
	left: auto;
}
.main-navigation li {
	position: relative;
}
.main-navigation a {
	display: block;
	text-decoration: none;
    font-size: 12px;
    padding-top:10px;
    padding-bottom:10px;
}
.main-navigation a:hover {
	display: block;
	text-decoration: underline;
}
.main-navigation ul ul {
    width:100%;
    padding-bottom:20px
}
.main-navigation ul ul a {
    border-right:none;
}
.main-navigation ul li:hover > ul, .main-navigation ul li.focus > ul {
  position: static;
}
.main-navigation li > a:only-child:after {
    content: "";
}

.main-navigation li li > a:after {
    content: '\f501';
    position: relative;
    right: 0;
}
.secondary-menu {
    padding-right:20px
}
.secondary-menu ul{
    list-style: none;
    list-style-type:none
}

.secondary-menu li {
    float:left;
    display:inline-block;
    padding-left:5px;
    padding-right:5px;
    border-right:1px solid #000000
}

That’s ‘Mobile First’. And for Desktop we have:

@media screen and (min-width: 1085px){
    .main-navigation ul ul,
    .secondary-menu ul ul{
        float: left;
        position: absolute;
        width:auto;
        top: 100%;
        left: -999em;
        z-index: 99999;
    }
    .main-navigation li {
	position: relative;
    margin-right:20px;
    }
    .main-navigation ul li:hover > ul, .main-navigation ul li.focus > ul {
  position: absolute;
    }
}

Done and dusted!

Missed a checkbox in backend! Bugger!!

Come on guys — this is doing my head in! Why doesn’t this work? What am I doing wrong??

After more experimentation I have discovered that I can display gradients — just not images. This is after clicking the Upload Image link above the Gradient settings…

Thanks @lbell, I’ve submitted a feature request for this. Understand it could take you a while to get around to implementing so at the moment I guess I’ll be resorting to some CSS trickery!

• This reply was modified 1 year, 4 months ago by mikehenden.

Thanks for coming back to me @lbell

I’ve asked client (local High School) why the links are there. It’s possible that they are there for admin purposes (ie school staff can add to their personal calendars but they are not for use by the public).

So there’s no way to have links on events in Google Calendar but same events not ‘clickable’ on the website frontend? We do need the information within the links.

On Quote Request Page settings:

Request for Quote Page URL: full-url-to-site/quote-request (have also tried empty field as I believe this page is generated anyway?)
Session method: cookie

When i type the URL in the address bar I get a formatted page with heading ‘Quote Request‘. The rest of the page is empty ie no products.

What we have is:

1- Checkout Option: RFQ (checked)
2- Always Show Product Prices With RFQ Checkout: unchecked
3- Show Prices With Normal Checkout: unchecked
3-0 Allow quote items when they are out of stock: unckecked
3-01- Normal & RFQ Checkout-sold-out Message: empty field
4- Hide Prices from Visitors: checked
4-02 Allow checkout without payment at WooCommerce checkout. DOES NOT CREATE A QUOTE REQUEST: unchecked (have also tried checked)
4-03 No payment message: no payment

• This reply was modified 1 year, 6 months ago by mikehenden.

I can’t find a way to insert the image (without uploading to web somewhere and linking via URL) but I assure you, the RFQ box IS checked.

To confirm: ‘Quote Request’ page IS being generated. It’s just unpopulated with any product quote requests.

Tried to specify a manual link to a Quote Request page I set up. Used the shortcode provided. This didn’t work either.

I’m still investigating this (spent most of the day on it in fact).

Discovered the ‘Advanced Field Checkbox’ for RFQ. I can add this product to RFQ list — when I view the list it takes me straight to the Shopping Cart. From there I need to proceed to Checkout and add payment details. As I mentioned before, client wants RFQ ONLY.

*sigh* I don’t get it…

Hi @bcworkz , thanks for your feedback. I can’t see how to add the ‘nav-menu’ class to the secondary menu (other than applying this class to the parent div. Unfortunately this didn’t achieve anything).

What I would like is for Primary and Secondary navigation to play by the same set of rules. Unfortunately my Parent item doesn’t seem to know that it’s a button to show/hide submenu…

??

I also have the following code in functions.php:

	// This theme uses wp_nav_menu() in two locations.
	register_nav_menus(
		array(
			'menu-1' => esc_html__( 'Primary', 'website' ),
            'menu-2' => esc_html__( 'Secondary', 'website' )
		)

Hi @visualeight, happy to report that yesterday I was able to reverse-engineer the code and finally eliminate whatever was causing the problem (still don’t know what sneaked in there but it’s gone now). All that remains is to introduce my SECONDARY menu (which is just above main navigation) and hope it doesn’t break anything. And (more to the point) it might even handle second-level navigation as it is apparently supposed to (although I won’t hold my breath on that one…)

So the fist of my two navigation issues is resolved : )

Thanks for your support!