katdidit

The code that worked for me was add woocommerce support in your theme functions file, if you have it hooked correctly and its still happening its maybe a plugin conflict.

add_action( 'after_setup_theme', 'woocommerce_support' );
function woocommerce_support() {
    add_theme_support( 'woocommerce' );
	add_theme_support( 'wc-product-gallery-zoom' );
add_theme_support( 'wc-product-gallery-lightbox' );
add_theme_support( 'wc-product-gallery-slider' );
} 

• This reply was modified 7 years, 10 months ago by katdidit.

If you are looking for a replacement Magento is pretty popular.

@mikejolley and @claudiosanches Thank you guys so much for your help. I am happy to report that my problem has been solved by using add_meta_data and adding a foreach item to the statement

foreach ( $item as $cart_item_key => $values ) {
    if( isset( $values['metakey'] ) ) {
        $item->add_meta_data('metakey', $values['metakey'], true );
    } 

• This reply was modified 7 years, 10 months ago by katdidit.

Set up a duplicate dev site in a separate folder or on your local machine to do the searches and changes (and testing) on. Yes its a pain, but its the only way you should be doing it for a live site anyway. Also you might want to contact the support for the woo plugins that you do have and ask them about 3.0 compatibility fixes.

It does not seem to be reading the values of the cart key – If I leave off the isset and $values it returns a string. If I leave the isset and leave off the values it returns nothing. – Leaving me to believe I am not saving the data correctly to the cart in the first place for the new method to pick up on it even though it shows up on the cart and in the checkout.

Same thing. Its showing in the checkout, and in the cart, but its not saving the values to the order itself?

For anyone else who has this problem, it was solved by using get_items() as key and isset.

$itemeta = $this->object->get_items();
          foreach($itemeta as $key => $lineItems)		
			if ( !isset($lineItems['recipient_email']))
		   return;

Thanks kursorA –

For anyone else who has this problem, it was solved by using get_items() as key and isset.

$itemeta = $this->object->get_items();
          foreach($itemeta as $key => $lineItems)		
			if ( !isset($lineItems['recipient_email']))
		   return;

Yes, Thank you Junior486!

Thank You, I don’t think you realize just how many people you have helped, mainly because there are so many of us who use twentytwelve child themes, and for me, the menu on every single one of them just broke with that update, not just the ones with a second menu. I have been trying to figure out what changed, but was looking in the js and the style changes that I had made, rather than the header.
Based on what you just spelled out, all it will take is to change that h3 to button in the header, and all are fixed for those not requiring changes in the js itself.

I would like to make a suggestion though, and maybe you are already doing it, rather than making changes to the parent theme js, copy it to your child theme to make your changes, then dequeue twentytwelve nav.js and enqueue childtheme nav.js. in your childthemes functions.php.

This will avoid overwriting of the changes in future updates.

Cheers and many thanks!

Sorry for the delay in answering. I did not have the time to develop a new plugin for this project after all and ended up using a custom post type to get the job done. perhaps in the future I will revisit it because I would think that a directory with descriptions for the native links would be a useful tool, but for now its on the back burner.