Darren Ethier (nerrad)

Hi there,

Carding attacks are the bane of online commerce! A solution like Anti-Fraud for WooCommerce might work for you?

Are the login issues still happening for you @qrest? I’ve done some checks internally as well as testing myself and there doesn’t seem to be problems with logging in at the moment but it may have been something that got fixed in between when you reported and I did the check.

Do the affected products have a large amount of variations/attributes? I noticed you have a high value for the PHP max_input_vars config.

Hi there! I see you mentioned this only appears to be happening to certain (duplicated) products. Are there specific routes you are seeing this happen (i.e. when editing a product, or when viewing the product on the frontend)?

Hi there, I posted an?update in a separate thread?about this issue. Submitting a ticket via the form should work now (but chat is not working at the moment – there’s an issue with the service provider that we’re working on).

Hi there, I posted an update in a separate thread about this issue. Submitting a ticket via the form should work now (but chat is not working at the moment – there’s an issue with the service provider that we’re working on).

You may need to set the max_input_vars configuration for PHP on your server to a higher value with that many variations.

It looks like there was an issue with the chat service that is being investigated further, in the meantime the form should work for submitting a ticket now. I checked and it seems to work. Let us know if you’re still not able to use the form.

Hi there, thanks for posting about this. I’ve shared this with the relevant folks on WooCommerce.com and it’ll be looked into. Will you share more details about what options you are selecting from the form?

Hey there, I appreciate you taking the time to leave your feedback. We’re definitely listening and want to work with folks to help them understand, utilize and get all the great value that is unlocked through the improvements shipped with WordPress and WooCommerce. I’m going to address a few of your points here which hopefully will help!

Documentation for DEV unclear and absent, major shortcomings

We’ve recently launched some updates and improvements to our developer documentation on developer.woo.com which you might not be aware of. What documentation is missing that is important to you?

Option settings scattered between customiser and settings

The WordPress Customizer is still available for classic theme development and ideal for that use-case. For block themes there’s much more rich customization options via the site and block editors. Are there specific options/settings which you would like to discoverability and usability improved with?

Release versions with major BUGs blocking normal operation

Our last couple releases did drop the ball there and we’re making some significant adjustments to avoid that in the future. No excuses, we must do better.

Gutenberg is handy, but there is no clear documentation on how to use it from the basics.

What would you consider are the basics? This will be helpful to understand the gaps in existing documentation that can be surfaced to Gutenberg and within Woo’s documentation.

The transition from?PHP to React?was too fast and with blocks that don’t work properly, even in BETA within a release for production sites? Perhaps you are exaggerating.

Very complex interactions will require some React knowledge, but PHP isn’t going away. A good example is the thought going into ensuring the new product editor is extensible via PHP.

If you are experiencing firewall issues, this advisory should provide some guidance.

Hi there. Thanks very much for the report. This is not good and I’ve created an issue for our team to look into this. We’ll update this thread once we have more info.

Hi @overyah

You mentioned earlier:

Also noted one more thing in the protocols sections of Redirecting plugin , this url?https://sab1000.com/wp-content/themes/storefront/storefront-style.min-rtl.css/?is showing 404 error. Is its the reason that website speed is effected . Please help me understand this.

That file is not present in the built Storefront theme and I don’t see anywhere in the repository where the Storefront theme requests/enqueues that style. The request for that URL might be coming from something custom on your site or child theme.

Where as in the Storefront child theme every thing is fine because SG optimiser has that combining option enabled for me.?

Is this a custom child theme you are using for Storefront, or one of the themes in the WooCommerce marketplace? If from the marketplace, can you share the name of the child theme you are using? Also what does “SG optimiser” refer to? Is this a special plugin/extension provided by your host or is it something downloaded from the www.ads-software.com plugin repository?

You also mentioned that you ran your site through the GTMetrix tool. I’m not seeing any of the original errors you reported in this thread via that report. Have you made changes since first starting this forum thread?

Hi @jbaker2112, that definitely is not a great experience and one we want to avoid as much as possible for users of the Cart and Checkout blocks. Would you be able to expand on what is breaking for you between updates? Any information is helpful!

Hey there! Thanks for taking the time to leave a review. I’m interested in learning more about the lack of value you received from the documentation and appreciate any insight you can give.

To be clear on what documentation you viewed, can you share with me the URL of what you referenced?

What were you hoping to find in the documentation that wasn’t there?

What were you hoping to accomplish with WooCommerce Blocks but were unable to?

Thanks!