David

Thanks @illiagreen, I see I was referring to the theme with the link, sorry.

But yes your video goes over some nice features, which I have found mostly myself through using the block. But as one of the YouTube commenters has asked you on there, to make a “full width” mega menu seems to be limited to the menu container, as you also mention in the video.

The YouTube comment references the Apple menu for example, and this is similar to what I am trying to achieve.

If the Greenshift Navigation element is within a Gutenberg row, with a block for a logo like on the Apple site:

Logo block // GreenShift Navigation Element. // Cart, login, search etc

Then the megamenu controlled by the Greenshift block there will only fill to the width of the Greenshift block, not the width of the whole page as per the Apple site or other examples.

Whereas If we use the Navigation element block entirely on its own without a logo in horizontal layout, the mega menu full width displays the entire width of the screen. Hopefully I am explaining that ok?

Am I and the Youtube commenter missing something, or is this just not possible as yet? Again, apple’s website menu shows it visually as an example too.

Many thanks,

David

Thanks for the update @illiagreen !

Yes hopefully it comes back very soon.

Hi @supportfunnelkit

Apologies! I got this to work by using a code block in WP that allowed the shortcode to work in a much better way. Thanks for the reply.

Loving the plugin too, works brilliantly!

Best,

David

Thanks @helloxootix , that does work, but unfortunately it for some reason then overrides the custom css we added into the plugin’s custom css area and the subtotal text becomes visible again:

/* Hide subtotal */ span.xoo-wsc-sc-subt { display: none; }

Also I noticed, with this shortcode in the header block, it’s still “moving” the entire header/nav menu “downwards” for a split second as each new page loads. When I use some other unrelated shortcode in the same place, this doesn’t happen.

Thanks again,

David

Hi @architabasandrai20

Sorry for the slow reply, yes that works perfectly now! Thanks for the quick turnaround, love the Kadence plugin 🙂

Best regards,
David

I see, thanks for this @threadi

Happy to see it is being reversed in the next release then, its really derailed our workflow currently! But from that discussion on the Gutenberg GitHub I see how it was something they were considering for other types of users I guess.

So hopefully they find a solution, as this isn’t it! 😉 Thanks again.

Hi @michaeltarongoy

Ok great, thanks for the information. I see by the changeling you release updates around every 1-2 weeks, so we will keep an eye on it in this timeframe.

@architabasandrai20 mentioned there is not a timeframe for this fix, but it has been escalated. Does this mean it has been moved to near the top of the list, should we be looking at a fix in a few weeks or so in this case?

Many thanks,

David

Hello @shahzeenfarooq

Huh….that is so poor on WooCommerce’s side. Your product says this below in LIVE installs of WooCommerce and the WooCommerce documentation:

“Open drawer when adding
Toggle to open the Mini-Cart drawer when a shopper adds a product to their cart.”

That does not in any way suggest that the functionality is limited to a single location. And on top of that, is not possible on the product pages themselves. The place most add to carts take place!

None of you in support forum could suggest that until I made a fresh WP install myself, which suggests that this is not the default behaviour and rather a bug, no?

Your suggestion is we custom code it ourselves, this is incredibly frustrating Shahzeen. Because due to WooCommerce’s own product and documentation I’ve wasted all this time looking into incorrectly working or labelled NATIVE features in Woo? What?!