Hi there,

Please add ?ao_noptimize=1 to the URL and the console error will go. That way you will see that it is still there.

(the console error does not show for “non-backend” users of the frontend and the above parameter gets rid of it)

Could you take another look?

Thanks again,

R.

Hi Serg,

I have highlighted this to Woo. Their quantitiy selectors are available as default inputs, until in the specific context. Will keep you updated!

R.

Hello Serg,

Those errors are not related and only show in the admin page re some hosting plugin.

When viewing the site outside of admin, unlogged in, there are no JS console errors and the problem continues.

Could you relook please?

Thanks,

R.

Hi Serg,

Actually, your quantity buttons actually work beautifully within the Woocommerce Bundles plugin when used by itself on the same site. The problem is that normal prescribed use includes using bundles as composite options. i.e. bundles products can be component options within composite products. That combination of the two official plugins is actually marketed by woo….

It is only in that context of using bundle products in composites that quantiyy selection format breaks.

It looks bad for the user, and even worse that it works elsewhere on the same site when bundles are not composited.

Can you look at this again please?

Many thanks,

R.

You’re welcome

Hello Serg,

The problem is exactly as per the images I sent, but I have discovered the root of the problem. It is a responsiveness issue.

Like many people, I often have certain websites zoomed in or out (ctrl and +/- in Chrome). If REM or EM units are used, I guess that won’t happen. If px values are used, there will be problems.

I realised this only because another example came up and disappeared. I will often view sites 80% zoomed out to fit more in.

So the problems are with the two graphics I showed above and the right hand arrow that scrolls through product graphics. That’s what made me realise the issue. If you view it at 80% zoom, the greater-than arrow moves outside the box to the right. To see this you might have to refresh – in Chrome you do not see the problem if you just zoom out. It has to render the page while zoomed out:

https://dl.dropboxusercontent.com/u/46763137/rightscroller.jpg

Can you sort these three so they are responsive?

Thanks,

R.

For anyone who needs it, I managed to get Woo to add functionality to the Composites plugin code. Hopefully helps.

R.

Version 3.8.2 of Composite Products adds in a new script parameter that can be filtered. This will allow you to add a top offset for the scroll viewpoint using a snippet like this:

add_filter( 'woocommerce_composite_front_end_params', 'wc_ninja_composite_front_end_params_offset' );

function wc_ninja_composite_front_end_params_offset( $params ) {
    $params[ 'scroll_viewport_top_offset' ] = 100;
    return $params;
}

Hi Serg,

In principle it seems almost fixed. The format and style is different to the rest of the xstore quantity selectors though. Could you make it the same as the rest?

Could you also let me know where the fix is so I can reimplement?

And will the fix also be in the next theme update or not needed?

Thanks

R

Typos!

Hi there,

R

Hi Serg,

I see the fix for the first screenshot, but the second is still wrong 🙁

Could you look again?

Thanks,

R,

Thanks Olga.

I better look at this again. I just saw you screenshot, that included markup. That made me wonder if I had been mixing up which feature/plugin was showing the cross-sell. I will try again with different items for the linked product vs the cart addons plugin!

Festive wishes,

R

Hi there,

Thanks for the CSS ‘heads up’.

I see why you could not see the issue. If you look again, but at the same product link from other posts (I should have pasted here too, it’s now in the private area). You will see that cart addons plugin specified product does show under Storefront, but not under Xstore.

I just retested this and it is still all the case. Could you take another look?

I guess there could be two reasons you couldn’t see it. Firstly, if you offer a hidden item that is actually for sale, it would not be shown as an possible cart addon (crazy, but the plugin works like that). Secondly, the addon itself might have already been in that cart, hence not offered as a cart addon.

Thanks again,

R.