Kaushik S. a11n

Hello @paulschiretz,

We are pleased to inform you that the issue you reported has been addressed, and we have released version 2.0.2, which includes the fix. I will be marking this thread as resolved. Should you encounter any further concerns, please don’t hesitate to reach out.

Also, if you enjoy using Google Analytics for WooCommerce, we would greatly appreciate it if you could take a moment to leave us a review. Your feedback is valuable to us.

Wishing you a wonderful day ahead! ??

Hi there @erykszczepanski!

I understand you cannot deactivate plugins and change the theme on the live site. We suggest creating a staging site of your live site to do the conflict testing. You can ask your host to create a staging site for you or use a plugin like WP Staging to create one.

Let us know how it goes!

Hi @erykszczepanski

Thanks for confirming about the attributes.

Are you able to confirm if the issue persists when you deactivate all other plugins except WooCommerce and switch the theme to a default theme like 2022?

If that doesn’t help, please feel free to create a ticket by going to https://woo.com/my-account/contact-support/

You’ll need to create a free Woo.com account before accessing that page.

Hi @nicowob123

Thanks for sharing the transient name. Could you confirm how many such transients you see getting stored in the database? You can run a LIKE query to find that out.

wc_product_loop seems to be related to the product shortcodes in WooCommerce: https://woocommerce.com/document/woocommerce-shortcodes/#products

Do any of your pages use the [products] shortcode? If yes, could you share URL of those pages?

We look forward to your response!

Hi @nicowob123

entries such as _transient_timeout_wc_xxxxxxx

Thanks for sharing the system status report. A lot of WooCommerce extensions/plugins could be using the common prefix _wc_ for their own transients. At this point, it isn’t clear if the transients are actually generated by WooCommerce core plugin.

Are you able to share a screenshot or the full name of the transients being generated?

We look forward to hearing from you.

Hi there @bitma

Thanks for contacting us! ??

I tested snippet and it seems to be totally removing the featured image. You’ve mentioned you want to include the featured image in gallery but not as the first one – does this mean the featured image should come on second or later position and the first immediate gallery image should be shown in place of featured image?

It would be great to have some more clarity regarding your goals.

We look forward to hearing from you!

Hi @kaarlomatias

I understand you wish to pull the attribute descriptions and display them on your product pages.

You’d want to use the wc_get_product_terms to pull all the data related to the attributes OR the wp_get_post_terms() with taxonomy slug product_attributes

A better way is to use the WooCommerce Brands extension which provides an easy way to pull the Brand data via shortcodes or custom code. It also has a separate placeholder for brand image/thumbnail.

Let us know if you have any questions!

Hi there @hyp0xia

Thank you for sharing your status report. This issue was reported here a long ago https://github.com/woocommerce/woocommerce/issues/32854

However, I am unable to replicate this on the latest version of WooCommerce. Are you able to share a few screenshots showing:

• Your Product’s Variation settings
• Your Product’s Attributes settings
• Confirm if you’ve used custom attributes or global attributes under (Products > Attributes)
• Confirm if you are able to replicate it on a default theme like 2022 and only WooCommerce active.

Hi there!

Thanks for getting back and providing us with more details.

It appears that some elements on your product page such as the add to cart form have been applied CSS float property.

As a result – the float effect is propagated to the Apple Pay button. To resolve this, you can clear the float:

.wcpay-payment-request-wrapper {
  clear: both;
}

OR give it float:right to align it with the add to cart form:

.wcpay-payment-request-wrapper {
  float: right;
}

Let us know how it goes!

Hi @shozon ??

Thanks for reaching out to us! I understand you’re having issues with your store’s checkout.

Have you been able to consult this with Phonepe and the Partial COD payment support team yet? Do customers see any error messages on the checkout page?

Can you try deactivating both Phonepe and Partial COD plugins and placing an order with the default WooCommerce COD method?

Hi there @nois3

In general, if you change the WordPress Address – the Rest API path will throw 404.

You’d want to go with method 2 described here to ensure WP Json works well: https://www.ads-software.com/documentation/article/giving-wordpress-its-own-directory/

As an example, I changed the WordPress Address (URL) to /wp/ at the back and followed method 2 described above. I was able to get the Stripe Json calls working:

Let us know if you have any questions!

Hi there @sitebolts team!

I looked further into it and was able to replicate using the default Gutenberg editor.

I’ve gone ahead and filed an issue here on WooCommerce’s GitHub repo: https://github.com/woocommerce/woocommerce/issues/40157 Our developers will be taking it further.

We greatly appreciate your vigilance in reporting this issue. Please do not hesitate to reach out if you have further queries or concerns.

Hi @y2vikram

From your description, the problem appears to be intermittent, which can make it hard to diagnose. I see that your old payment method was CC Avenue. Do you remember the specifics of its integration on your site? Did you use a specific plugin for this?

I noted that you’ve attempted turning off all other plugins. It would be helpful to know if you also tested the issue using a default theme like 2022. If you haven’t already, could you give this a shot when/if the problem reappears? Additionally, you can also download your wp-content folder to your local system and carry out a keyword search using tools like Sublime Text or Notepad++. By using “Avenue” as a search term, you may be able to identify potential sources of the issue. This might provide further insights into the problem.

Lastly, if the payments made via CC Avenue go to your own bank account, it may be just a technical issue rather than malware.

Hi there @hastibe @oyondo @naresh11381 !

We understand your concerns and apologize for any inconvenience caused. The WooPayments Menu is a new update from WooCommerce core. It was never our intention to interrupt the user experience, nor to be unprofessional or appear as excess bloat. We truly value your opinion.

This issue is being tracked and discussed here: https://github.com/woocommerce/woocommerce/issues/39668

I’m unable to confirm whether our team will keep the current display or any amendments will be made, however, I encourage you to join this conversation by sharing your thoughts directly on the GitHub link.

Please feel free to reach out in case you have questions or need any further assistance. We’re here and happy to help!

Hi there @philjw

I am just trying to understand this better:

For example if shipping is $10 and the order is for $80 of zero-tax items and $20 that are taxable, shipping tax should only be on 20% of the shipping cost. ($2 in this example)

Do you mean:

• Zero tax items: $80
• Taxable items: $20
• Shipping is $10

What tax is applied to the items currently? Are you able to share a screenshot?

Do you mean regardless of the tax % to be applied to the items, you’d want the shipping tax to be 20% of the shipping cost?