Dave Loodts

This is not possible in WooCommerce core, you’ll need a Wholesale plugin or custom coding to add extra pricing fields per role.

In the latest update of WooCommerce, they show these kinds of notifications to display which services on your site still uses the Legacy API. And SendCloud still does.

So, it’s for awereness that -if SendCloud is not adapting- you should install the Legacy API plugin from WooCommerce 9.0 onwards.

It can only be solved when SendCloud is moving over to the new REST API. But besides that: the size of the logfile won’t have any impact on your site performance, and in terms of extra space on your server, it is also not that impactfull.

I do expect SendCloud to follow soon with the new REST API, but we will see.

So 600.000 users have to “opt-out” for a speedy website… waw, just waw…

Thanks!

Thanks for the link.

But I do hope you get my point too that there is right now changelog link from the www.ads-software.com theme profile.

And on the Woo dev blog, the latest Storefront theme release post is from 2021; see category: https://developer.woo.com/category/release-post/storefront-theme-release-notes/

I asked a privacy expert about this new feature. It’s data stored on own server, so that is not an issue. Although for more clearity you can better add it to the privacy policy.
An order on it’s own has already a lot of personal information, WooCommerce also saves the IP-adress, so it’s already a must you should add what data you store in your privacy policy. Although this feature won’t be a big issue in my opinion, as UTM-tags are also mostly sees as save.

I know a few privacy-focussed people that dropped their Analytics tools, and just use it like this way: utm or get origin, save it in a cookie, connects the cookie in a hidden field of a contact form, and now they have a clear overview of the impact of their campaigns. And that is perfectly compliant. And WooCommerce does the same thing now. And as long as this data is stored on the own server, you’re save.

(I know it’s not really allowed to give advice on the matter in this forum, but i really checked an expert in this; he even tracks all the cases/fines in Europe, so that advice is legit: https://www.dailybits.be/item/overzicht-gdpr-boetes-rechtszaken/)

Hi, it looks like it is not a general issue. Sorry about that. We’ll have to dive deeper into that proect.

I’m gonna add the idea to the feature request list.

It’s not only Revolut that’s gonna reply like this. Big or small companies, the majority of it aren’t yet supporting the new cart or checkout block editor. We run +40 shops, none of them use the cart or checkout block. From my current experience as semi-developer; the classic cart and checkout is way more flexible to build out. More documentation and tutorials. Even if a build a new shop now, i’ll still advice the classic way in terms of cart and checkout. For me it’s certainly not a step back, it’s a step for more flexibility right now.

For a typical php developer in WordPress-land, it’s not easy to switch over to javascript. I see a lot of shortcomings in that part at plugin builders. But it’s not easy to follow up: the speed of development, full site editing testing and the HPOS-integration, that all takes a lot of energy and time for plugin builders. There is a lot of pressure and also legacy code to support.

On WooCommerce blocks that is involved with lot’s of other functionality like the checkout or cart, it is certainly not that easy. In fact: that part is thé most important feature of a shop. Other “basic” WooCommerce blocks are okay to use. So, you have to make that difference in blocks. As you said it’s the standard of using blocks, but it depends on the amount of external (plugin) functionality that is added. It will go in that direction for sure, but it will take more time for the majority of plugin builders. We have to be patience and be happy with the ‘classic’ part that is still working great and stable.

In particluar the Checkout block is indeed an issue for many plugins that connect with the checkout. The Checkout block plugin and the classic WooCommerce shortcode works totally different. The classic version has code hooks, usefull for pluginbuilder to hook their solution onto.
For Blocks, that is a different method and more complex cause it’s mostly written in javascript. Maybe in the upcoming future, plugins will adapt.

I’m not working for WooCommerce, but i know WooCommerce assures that both methods will be continue to work in the future. You can safely go back to the shortcode method, like [woocommerce_cart] and [woocommerce_checkout]

Hi, i’m so sorry and i was wrong. I have noticed it in the Premium version, i will sent a support ticket via the website.

Thanks, i’ll do that!

Hi, first handy to know: it’s better to post your question in the another support forum, and i guess it’s better to ask support on your theme builder Astra.
When looking the code, it seems like the featured image is set in the header. So, take a look at the Astra settings in the customizer on that part.

Are you referring to this plugin: https://woocommerce.com/products/viva-wallet-for-woocommerce ?
I guess it’s better to ask for support via woocommerce.com; cause it will be an issue with that plugin; maybe in conjucting with other plugins or theme on your site. I won’t be probably an issue with WooCommerce itself as it is all api-driven.

Hi, without knowing the link of the particular page we can not help you here.

That is because you buttons use the colour white, and white text on white background results in your problem.

Try to find the stylesetting in the theme settings. Also your links on the productpage are white, so the category and tag links aren’t either “displaying” properly