cfunkyk

Thanks for your follow-up! I’ll look into this – good insight. It looks like it may have switched to private somehow. I think it may have disappeared as an option b/c I had the post-format archives disabled in yoast settings. I reinstated them, and the sitemap option reappeared. I disabled the sitemap option, and then disabled the taxonomy archives again. Sure enough the sitemap option disappears again.

Thanks for your help in sorting this out!!

Let me know if you have any questions for me in trying to sort this out on your end. I tried this exact set of events I describe above in another site and the same thing happened. So if we disable the format-based archives before choosing not to show it in the sitemap, then they will appear in the sitemap, even though they are disabled.

Cheers!

I am using pro version on my sites too. I see that you put that in another request on the same subject.

It crashes my sites too:

/wp-content/plugins/wp-smush-pro//extras/free-dashboard/module.php): failed to open stream: No such file or directory in /wp-content/plugins/wp-smushit/wp-smush.php on line 861, referer: https://www.blahblah.com/wp-admin/update-core.php?action=do-plugin-upgrade

I’m automatically upgrading, and I believe I even did a manual upgrade. No issues before this version. Looks like maybe you have an extra / in your code?

I’m trying to do the same thing because I want all products to add the buyer to the same whishlist member membership level. We only want one membership level, but we have many different products that should add to the same membership level. For the same reason, WooCommerce forcing different sku numbers on each product, we cannot do this with the wishlist membership integration because we have to create different skus for each product in the shop.

I think I found the way to allow the same sku number on product variations, but cannot figure out how to apply this to allow the same sku on different products just yet.

I would be willing to test out this functionality also. The ‘active’ google maps for mobile users being able to click and pull the map up on their phone is super key! My friend owns a bike store and has not stopped talking about your app. He would very much like to use the maps and give you credit on his website. We live in a tourist/vacation area, so this would be huge for our bike shop and for riders all over.

Thanks for your response Justin, and looking forward to helping you make this a reality! Thanks for posting this review Gordo!

And, same as above re: responsive maps. If its an iframe code like embedded google maps, then we have css that can handle making it responsive. Seems like the 100% deal may be the best option from your development end, so that the map fits the container its being put in…?

I am having the same issue. I went through and refreshed the api keys and tokens, and even started a new feed, and I am still getting the same message.

I fixed it:

Change this:

// Return thank you page redirect
				return array(
					'result' 	=> 'success',
					'redirect'	=> add_query_arg('key', $order->order_key, add_query_arg('order', $order_id, get_permalink(get_option('woocommerce_thanks_page_id'))))
				);
			else :

To this:

// Return thank you page redirect
				return array(
					'result' 	=> 'success',
					'redirect'	=> add_query_arg('key', $order->order_key, add_query_arg('order', $order_id, $this->get_return_url($this->order)))
				);
			else :

The payjunction team should have had this fixed a long time ago…

Check my post below on how to fix the PayJunction Payment Gateway so that it uses the new WooCommerce 2.1 endpoints.