Marco Pereirinha

Hi @joelfelkins:

Can you provide a link so I can try understand your setup and try do help?
The link for the newest version of the plugin is this one https://github.com/pereirinha/woocommerce-variation-details-on-page-product/tree/fix/multivariations-single-impact

About the data selector that is a wrapper added that you can use for styling. The plugin will add variation data to the placeholder DOM object.

Hi:

Just to make sure, are you using version from dev branch on GitHub? I’m on my phone so I’m not sure how I’ve named it, but it should show you on your dashboard plugin page as version 3.3.2

Hi @joelfelkins:

I’m really late on this one, but I think there is light. I’ve actively working on this and I think this is about to become a feature.

Can you please check this ticket https://github.com/pereirinha/woocommerce-variation-details-on-page-product/issues/4? It would be great if you could test before I deploy this.

Hi joeldfelkins:

I’ve dig a little deeper and found the issue.

At this point, the plugin requires you to fill all variations — State Outlines, Heart or Star and Heart or Star Color — since logic will try to match each of them.

I understand that this requirement is less then optimal for situations like yours. I’ve a solution on my head, but I can only roll out next week.

If that works for you, great. If it doesn’t, you’ll have to set manually a case for each combination.

Hi joelfelkins:

It seems that the issue is related with the selector for placeholder.
I’ve looked into your markup and I think you could use a different element.

Can you please try to set .product_meta as the placeholder for variation data on plugins settings: WooCommerce > Settings > Products > Variations.

Should be first option.

I’m so sorry, but for some reason I just saw this pending. Perhaps I didn’t get any warning email during transition of WordPress support system.

Any way, I was looking into these links you just sent and I don’t see this plugin running. Can you confirm that you’ve disabled/remove it?

Hi Lucy:

I’m not sure if I follow your issue. Can you post a URL for your website?

Just to let you guys know that I’ve found my issue. I was using protected meta fields (prepended with an _ “underscore”) and it seems to be an imposed limitation of WP API.

Sorry for any hassle.

Hi.

I’m facing similar issue. WordPress Multisite v4.4.2, WP REST API v2.0-beta12, ACF v5.3.5 and ACF to WP API v1.3.3 returns empty acf array.

Here’s a print screen.

https://cl.ly/1t2x3r1W2m2Y

Thanks

Hi Javier:

After some time to figure out why we weren’t getting any feedback from changes, I think I found the “issue”.

Have a look on this print screen
https://cl.ly/1h0B262j2d0u

At the button you’ll see the serialised data that the plugin is reading. Since it can’t find any absolute match between all attributes (note that panels has no data) then it doesn’t show any content.

In order to make it work for you, you’ll have to add all possible combinations of variations.

Ok guys!

You’re killing me ??
I’ll push this up on my agenda!

Well I surely can see them ??
And again, those boxes are added by WooCommerce. My plugin it’s only “responsible” to add dimensions, if they’re set.

Hi mimbee17:

Not sure if I fully understand your issue.

Variations are a core feature of WooCommerce. You can add as many variations as you would like. Those variations can help your customers to narrow down the desired specification of the product.

By enabling a product to have variations on the backend, dropdown fields will automatically be added to the frontend.

Some variations might have some physical properties like width, height, length or weight. By default, WooCommerce doesn’t bring that information to the frontend.

Is at this point that this plugin becomes valuable, as it picks up those details and show them on the frontend, depending on selections made by your customer.

Does this description help you?
Have you seen this page?

Hope that this helped putting you on the right track. ??

There. Can you test it now?

Hi Javier:

Dunno why I didn’t get and alert about this ticket. I’m sorry for the late reply.

I’m on it and you should expect a release very soon to fix this.

For now, you can avoid showing those nasty errors by adding this line
define('WP_DEBUG', false);
to your wp-config.php file. Usually is located at the root of the WordPress installation.