gasurgaelach

The fact of the matter is a new feature like this should not be rolled out without internal plugin support. It is quite shameful and the reason people are sticking to community plugins (and glad to pay premium support) and not Woo/WP themselves. Do not roll out a feature and say you’re giving it priority when it should not have been made available in the first place because there was no support.

I’m with you Andrew, a feature should be a full feature, not an afterthought!

Kindly, no canned responses from Woo.

This plugin is blatantly to make Woo affiliate money. As as developer, going into the onboarding code is shameful. Stick to community plugins.

The Woo response is quite awful. If something new is introduced, it should be in the roadmap for all internally developed profit making plugins. Woo has simply let the ball roll with no plan whatsoever.

Introduce a GTIN field – brilliant – we can move away from custom fields, but at least make it supported. It isn’t even an exportable/importable field. Awful behaviour from Woo.

Despite moving to Woo’s official field, I have clients with thousands of products denied from Merchant Centre. It is quite horrendous.

• This reply was modified 1 week, 1 day ago by gasurgaelach.

Hi Andrew,

I managed to do it this way:

• Export products from Woo
• Add the column Meta: _global_unique_id
• Import via product import (make sure to tick ‘Update existing products’)

If you already have a list of products/SKUs, you can use VLOOKUP to match the GTINs. I hope this helps!

Robbi

• This reply was modified 1 week, 5 days ago by gasurgaelach.

I have exactly the same issue (exactly as described).

I would hate to go back to the original checkout, the block is so much more efficient. :0)

Hi Art Project Group,

I believe I may have found the problem.

It appears that the plugin does not calculate the total order depth and weight.

For example, I have the following rules now:

220|4.25|323x220x20
470|5.25|323x220x20
470|7.8|323x250x150
450|7.81|323x250x150
720|6.25|323x220x20
950|10.2|323x250x150

I have also tried entering them by order of weight (my usual method):

220|4.25|323x220x20
450|7.81|323x250x150
470|5.25|323x220x20
470|7.8|323x250x150
720|6.25|323x220x20
950|10.2|323x250x150

In the screenshot you will see a product that is 16mm in depth. So:

1x books = ￡5.25
2x books = ￡7.80

But I change the quantity to 2, the price ￡5.75. So total order depth is not calculated.

Is there a way that I can fix this? And thanks for your help ??
(I have had to temporarily remove some of those prices from the live website as it is currently active)

Unfortunately the latest update has removed the code to look for, and it is probably in another file, still clashing. Aghh! Will have a look through the files…

I am having the same problem, it seems that the underscores are missing from the thumbnail filenames in the NextGen admin..

Hi all, I didn’t know of a cool wee WordPress function ( wp_get_attachment_thumb_url ), sorry for the post!

Here’s what I’m using:

<img src="<?php echo wp_get_attachment_thumb_url(get_post_thumbnail_id($post_object->ID)); ?>" alt="<?php echo get_the_title($post_object->ID) ?>" />

I third it, it’s an odd problem. Thankfully the HTML was saved though…

Same problem here ??