matt-thomas-photography

I’d probably have to disagree with that statement, as within the WordPress admin app there’s really isn’t anything that’s configured as that all done within the main web app

The overview, cookie summary, consent trends and page views are not configurable options as it’s only pulling web data. Which isn’t easy to view at a glance given the mobile viewing is not optimal

It makes me feel like it’s better to just uninstall the plugin seeing as it doesn’t offer anything visually on the fly statuses. Just surprised with something like this it’s not mobile device friendly for viewing data, whilst I understand that setup is best suited for desktop applications, we shouldn’t be limited to this when viewing configured sites information

https://github.com/woocommerce/woocommerce-gateway-stripe/issues/3989

There you go

Well the issue is still there, last update wasn’t addressed to the problem. Therefore it’s NOT resolved and still awaiting development to fix this.

Amazing thank you! All sorted now

I can’t seem to get it work and hide the following

filter by coupon, filter by shipping, filter by item and metadata

Making sure to add the right #my-coupon etc to each option want to hide. As it’s not frontend doesn’t it need to be something more for the CSS as a function?

Thanks for the confirmation! I did spot that topic on the support site after I had sent the message. Makes sense so I’ll have to create a test and then update the form with the results

Is there any possibility of hiding filters that are not needed as there’s another user for this site and don’t want them to be overloaded with too many options when trying to export

Hi

Yes that’s the plugin, I haven’t actually had any orders processed yet through the site using the new Product Add On, so not sure if that’s why it’s not appearing? As no table with data maybe to pull?

I can’t see the Woo Product Add On field within that list, I can see the Variations options but this is using a 3rd party plugin so not sure if the key would be there?

I’ve raised a bug report on the GitHub however nothing seems to be happening, therefore no support raising this issue which is still ongoing

The side by side of buttons is only appropriate when it’s displaying the Amazon as well as that’s what the whole link I sent to was about, however if you have a UK store or any store not in the US (where the Amazon payment is available) you’d have this issue. So it’s not a fix it’s an issue that needs to be looked into

That’s because if you inspect the page you’ll see I’ve had to add extra CSS to fix the issue

#wc-stripe-express-checkout-element {
display: grid !important;
justify-content: unset !important;
}

As in that file I’ve linked above the flex grid layout compresses the size, which was bought in since the last update as per the commit log on that file

I’ve linked to the page in question on my first post and I’ve been very clear where the issue is coming from! If there is not the correct place for detailed support then please let me know where I should raise this issue.

The problem is from the updated CSS that’s been added since last update to the plugin that causes styling issues wherever the following class appears #wc-stripe-express-checkout-element {

So this can be product pages, cart or checkout. Plus see the above comment about where the new styling comes from causing the conflict

In 9.2.0 this was updated which is causing the issues

https://github.com/woocommerce/woocommerce-gateway-stripe/blob/8d95f3e613c235e6590dbabf3ab85cc388527bd6/client/entrypoints/express-checkout/styles.scss

The inclusion of the display flex CSS – if you check the previous version this wasn’t included and displayed the buttons fine. So looks like for stores that don’t have the updated Amazon payment (basically anything not in the US) there’s issues

It’s to do with the change in the file

/build/express_checkout.css

As now it’s including all this

#wc-stripe-express-checkout-element iframe{max-width:unset}

#wc-stripe-express-checkout-element{margin-bottom:12px;display:flex;gap:10px;flex-wrap:wrap;justify-content:center}

Where as previously all that was there was nothing to do with the display flex or wrap

Don’t think that is necessary true especially when using native iPhone and safari browsers as the user experience is so disconnected that you end up leaving the whole site and doesn’t work how native Google pay works on Android devices, same as how Apple Pay works on iOS devices