LovingBro (woo-hc)'s Replies - page 5

Forum Replies Created

Viewing 15 replies - 61 through 75 (of 3,134 total)

← 1 2 3 4 5 6 … 207 208 209 →

Forum: Plugins
In reply to: [Pinterest for WooCommerce] Conversions API events missing External ID, Order Value and Product ID parameter
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @gwenwruck,

Thank you for sharing the log details and for clarifying the PixelYourSite setup.

Reviewing the log you shared, it does confirm what Shameem mentioned earlier. The entries are almost entirely related to repeated ads_credit/redeem API requests failing with the Pinterest error:

OFFER_DOES_NOT_MATCH_ADVERTISER_INTEGRATION_PLATFORM

This appears to be tied specifically to Pinterest ad credit redemption attempts and not to Conversions API event delivery itself.

Importantly, there do not appear to be any logged checkout, add to cart, or conversion event failures in the log you shared, which suggests the plugin is still attempting to send conversion events normally.

That further supports the earlier assessment that:
1. The missing External ID is currently a known limitation in the plugin implementation.
2. The low IP address and user agent coverage is related to the bug already identified in PR #1175:
  https://github.com/woocommerce/pinterest-for-woocommerce/pull/1175
3. Since no conversion event failures are appearing in the logs, the missing Order Value and Product ID warnings in Pinterest Ads Manager may instead be related to how Pinterest is currently validating or attributing the incoming events after processing.
At this stage, your configuration does not appear misconfigured, and there is no indication from the logs that another plugin is blocking the events entirely.

The repeated ads_credit/redeem notices are also likely unrelated to your Event Quality issue specifically, though they may indicate an expired or incompatible Pinterest promotional credit attempt associated with the connected ad account.

For now, the best next step would be to continue monitoring after future plugin updates, especially once the fix from PR #1175 is released, as that is expected to improve the affected Event Quality reporting considerably.

We’ll keep the thread open in case additional findings become available or if you notice any changes after updating the plugin in the future.
Forum: Plugins
In reply to: [WooCommerce] Client histories wrong
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @ravanh,

Thanks for sharing those additional details and the System Status Report. The fact that only 922 out of 1430 orders are appearing in the Orders admin page is definitely a strong clue here, especially combined with the incorrect customer history calculations.

From what you described, it does sound possible that the manual order import during the migration may have caused inconsistencies between the WooCommerce order tables and the lookup tables WooCommerce uses for customer statistics and order history.

I also noticed from your report that HPOS is enabled on the site. Since HPOS stores orders in dedicated WooCommerce tables, partial imports or mismatched sync data can sometimes lead to symptoms like:

• Incorrect customer order counts
• Wrong average or total spent values
• Guest orders not being linked correctly
• Missing orders in the admin Orders list

To start narrowing this down further, could you please check the following:
1. Go to WooCommerce → Status → Tools
2. Run these tools one at a time:
  • Regenerate the product lookup tables
  • Recount terms
  • Clear analytics cache
3. Then check under: WooCommerce → Settings → Advanced → Features
Please temporarily disable HPOS compatibility mode if enabled, save changes, then re-enable it and allow WooCommerce to resync the order data.
1. Also, can you confirm:
  • Were the manually imported orders imported directly into the database, or through a plugin/tool?
  • Do the “missing” orders still exist in the wp_wc_orders table and wp_posts table, or only one of them?
Since the issue persists even in Health Check troubleshooting mode, this is looking less like a plugin conflict and more like a data synchronization or migration inconsistency.

Let us know what you find after the above checks and we’ll continue from there.
Forum: Plugins
In reply to: [Google for WooCommerce] Technical error
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @dazsmodels,

Thank you for sharing the detailed error log. The fatal error appears to be coming from the Google for WooCommerce plugin, specifically where it is trying to load the AssetGenerationServiceClient class, which suggests that part of the plugin files may be incomplete, outdated, or corrupted after an update.

To help narrow this down, please try the following:
1. Update both WooCommerce and Google for WooCommerce to their latest available versions, if not already done.
2. Reinstall the Google for WooCommerce plugin completely:
  • Deactivate and delete the plugin
  • Download a fresh copy from WordPress.org
  • Reinstall and reconnect the plugin
3. Clear all caching layers, including any server cache, plugin cache, and CDN cache.
4. If the issue still persists, run a conflict test by temporarily:
  • Switching to a default theme such as Twenty Twenty-Four
  • Deactivating all plugins except WooCommerce and Google for WooCommerce
Then test again and let us know the outcome.

If possible, also share your WooCommerce System Status Report via https://pastebin.com or https://quickforget.com so we can take a closer look: WooCommerce → Status → Get system report → Copy for support. Looking forward to your update.
Forum: Plugins
In reply to: [WooCommerce] Migration to HPOS: wc_run_batch_process fails
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @spitelis,

Thanks for sharing the detailed information and logs. From what you shared, this does not appear to be caused by leftover payment gateway metadata. The main issue seems to be that the HPOS order meta table itself, wpql_wc_orders_meta, is missing from the database, which is why the wc_run_batch_process action keeps failing during synchronization.

I also checked your system status report and can see that while some HPOS tables exist, the wpql_wc_orders_meta table is indeed missing.

At this point, I’d recommend the following:
1. Create a full backup of your site and database first.
2. Go to WooCommerce → Status → Tools and run:
  – Create the WooCommerce database tables
  – Verify database tables
3. After that, go to WooCommerce → Status → Scheduled Actions and check if the wc_run_batch_process actions are still failing. If they are, try clearing the failed actions and trigger the sync again.
4. Since database table creation may have failed earlier, it would also be worth temporarily disabling all plugins except WooCommerce and switching to a default theme such as Storefront, then retrying the HPOS sync.
5. If the table still does not get recreated, please share:
  – A fresh fatal error log after retrying
  – A screenshot of WooCommerce → Status → Tools
  – Whether this happens as well on a staging site
One additional thing I noticed is that your site has a very large Action Scheduler table and several outdated theme template overrides, which may not directly cause this issue but could contribute to background processing instability during the migration. Looking forward to your update.
Forum: Plugins
In reply to: [WooCommerce] Technical error
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @dazsmodels,

Thank you for sharing the detailed error log. The fatal error appears to be coming from the Google for WooCommerce plugin, specifically where it is trying to load the AssetGenerationServiceClient class, which suggests that part of the plugin files may be incomplete, outdated, or corrupted after an update.

To help narrow this down, please try the following:
1. Update both WooCommerce and Google for WooCommerce to their latest available versions, if not already done.
2. Reinstall the Google for WooCommerce plugin completely:
  • Deactivate and delete the plugin
  • Download a fresh copy from WordPress.org
  • Reinstall and reconnect the plugin
3. Clear all caching layers, including any server cache, plugin cache, and CDN cache.
4. If the issue still persists, run a conflict test by temporarily:
  • Switching to a default theme such as Twenty Twenty-Four
  • Deactivating all plugins except WooCommerce and Google for WooCommerce
Then test again and let us know the outcome.

If possible, also share your WooCommerce System Status Report via https://pastebin.com or https://quickforget.com so we can take a closer look: WooCommerce → Status → Get system report → Copy for support. Looking forward to your update.
Forum: Plugins
In reply to: [WooCommerce] Woocommerce shows Title SEO in vertical

LovingBro (woo-hc)
(@lovingbro)

2 months ago

Hi @cdelph75,

Thanks for reaching out. It sounds like the SEO Title column on the Products screen is taking up too much vertical space, which can definitely make managing products and categories harder.

From what you described, this SEO Title column is most likely being added by your SEO plugin rather than WooCommerce itself. WooCommerce does not control the layout of those SEO columns in the Products list table.

To better narrow this down, could you let us know which SEO plugin you are currently using, for example Yoast SEO, Rank Math, AIOSEO, or another one?

In the meantime, most SEO plugins allow you to disable or customize these admin columns directly from their settings. You can also try using the “Screen Options” tab at the top right of the Products page to hide columns you do not need.

If possible, please also share a screenshot of how the column is displaying on your end using https://snipboard.io so we can take a closer look.

Forum: Plugins
In reply to: [WooCommerce] Client histories wrong
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @ravanh,

Thanks for reaching out about this. That does sound unusual, especially if the customer purchase counts changed after the store migration.

WooCommerce calculates the “Customer history” data based on the orders linked to a customer account or billing email, so if something changed during the migration, such as user IDs, order associations, or duplicated data, it could affect the counts being shown.

To help narrow this down, could you let us know:
1. Was the site migrated to a new domain, server, or both?
2. Did you use a migration plugin or restore from a backup?
3. Have you already tried a conflict test by temporarily disabling all plugins except WooCommerce and switching to a default theme like Twenty Twenty-Four to see if the counts change?
4. Are the affected orders linked to registered customer accounts, guest orders, or both?
Also, please share your WooCommerce System Status Report so we can take a closer look: https://woocommerce.com/document/understanding-the-woocommerce-system-status-report/

You can paste it via https://pastebin.com or https://quickforget.com and share the link here.
Forum: Plugins
In reply to: [PayPal Enterprise Payments (formerly Braintree) for WooCommerce] Braintree Local Payment Methods broken on pay‑for‑order page
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @janez33,

Thank you for the detailed report and technical breakdown. The information you shared around the form#order_review flow and the missing nonce is very helpful.

Before we investigate this further on our side, could you let us know if you have already performed a full plugin and theme conflict test?

To do this, please temporarily:
1. Deactivate all plugins except WooCommerce, WooCommerce Subscriptions if applicable, and Braintree for WooCommerce Payment Gateway.
2. Switch to a default theme such as Twenty Twenty-Six.
3. Retest the pay-for-order flow with the Local Payment Method enabled.
If the issue still occurs after that, please also share whether this was tested on a staging site or a clean WooCommerce installation.

That will help us determine whether this is isolated to the plugin itself or being influenced by another plugin or theme integration.
Forum: Plugins
In reply to: [WooCommerce] PHP warning rest-api
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @kirstinv,

Thanks for taking the time to test this further and for sharing the updated logs, this additional detail is very helpful. From what you shared, the warnings now appear specifically when filtering products in the trousers category and after adding tags to those products. Since the warnings are coming from the WooCommerce REST API product categories controller trying to access a null post object, this suggests that one or more products, categories, tags, translations, or related taxonomy relationships may be incomplete or corrupted in the database.

As the issue could not be reproduced on staging, but reappeared on the live site after updating product taxonomy data, this points more toward site specific data rather than the WooCommerce core plugin files themselves.

To narrow this down further, please try the following on the live site or preferably a fresh staging copy of the live site:
1. Run WooCommerce > Status > Tools and use: • Regenerate product lookup tables
  • Clear WooCommerce transients
  • Recount terms
  • Regenerate the REST API cache if available
2. Check if there are any products in the trousers category that are: • Drafts
  • Trashed
  • Missing translations
  • Missing featured images or incomplete data
  • Duplicated products created by import plugins
3. Since your site is multilingual (lang=en appears in the request URL), temporarily disable the multilingual plugin and test filtering the category again. Some multilingual plugins can leave orphaned taxonomy relationships that trigger these warnings.
4. Please also temporarily disable any plugin related to: • Product filtering
  • SEO
  • Product tagging
  • Bulk editing/importing
  • Multilingual functionality
Then test the category filter again.

If the warnings still appear afterward, please share:

• Your System Status Report via https://pastebin.com or https://quickforget.com
• A screenshot of the active plugins page via https://snipboard.io
• Confirmation of which multilingual plugin you are using

That should help us narrow down exactly what object is returning as null here.
Forum: Plugins
In reply to: [Pinterest for WooCommerce] Conversions API events missing External ID, Order Value and Product ID parameter
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @gwenwruck,

Thank you for providing those details about your setup. I can see how concerning it is to have the Event Quality Score reporting missing parameters even though the Pinterest integration appears connected and actively sending events.

At the moment, the Pinterest for WooCommerce plugin does not provide a separate field to manually enter a Conversions API access token. The OAuth connection between the plugin and Pinterest handles the authentication automatically in the background.

Regarding the missing parameters, some event fields such as External ID, Order Value, and Product ID depend on the specific event type, the available customer/session data, and the information Pinterest is able to receive from the store during the event trigger. In some cases, Pinterest Ads Manager may flag these as “recommended” rather than strictly required.

To help narrow this down further, could you please share:
1. Your site’s System Status Report, via WooCommerce > Status > Get system report > Copy for support, then paste it using https://pastebin.com or https://gist.github.com
2. Whether you are using any caching, optimization, consent, or security plugins that could affect tracking scripts or cookies
3. A screenshot of the Event Quality diagnostics from Pinterest Ads Manager, uploaded via https://snipboard.io
This will help us check if there may be a plugin conflict, tracking restriction, or a limitation in the current implementation.
Forum: Plugins
In reply to: [Google for WooCommerce] Critical Error

LovingBro (woo-hc)
(@lovingbro)

2 months ago

Hi @healthmanifested,

Glad to hear the reinstall resolved the issue and everything is working properly again now 🙂

I’ll go ahead and close this topic as resolved. If you run into anything else or need any further help with Google for WooCommerce, please feel free to open a new topic and we’ll be happy to help.

Also, if you have a moment, we’d really appreciate a review of Google for WooCommerce. Your feedback helps other merchants make informed decisions about using the plugin: https://wordpress.org/support/plugin/google-listings-and-ads/reviews/#new-post

Forum: Plugins
In reply to: [WooCommerce] ‘Please choose product options by visiting’ error when navigating shop

LovingBro (woo-hc)
(@lovingbro)

2 months ago

Hi @ninjabeaver,

Thank you for the update and for confirming the results of the PayPal Payments test. That does help narrow things down considerably.

Can you recall if the issue started after a recent update to WooCommerce PayPal Payments, specifically version 4.0.3?

I also noticed that version 4.0.4 was released very recently, around 30 minutes ago, so before rolling back, could you first try updating to 4.0.4 and then test the navigation flow again between variable and simple products to see if the behaviour changes.

If the issue still persists on 4.0.4, I’d then recommend a temporary test of downgrading from 4.0.3 to an earlier release and testing again. That would help confirm whether this is a regression introduced in a recent version of the plugin.

You can download older versions of the plugin here: Advanced View for WooCommerce PayPal Payments. Please make sure to perform the downgrade test on a staging site first if possible.

For the scheduled actions you shared, they do not immediately look related to this issue. The wc-admin_import_orders actions especially do line up with the earlier store recovery/import work you mentioned.

As for WP Cron, your SSR earlier showed Daily Cron as not scheduled, which can sometimes happen even while WP Cron itself is enabled. A helpful check would be: WooCommerce → Status → Scheduled Actions. Then see whether scheduled actions continue processing normally over time, or whether pending or failed actions keep building up.

You can also ask your hosting provider to confirm that server cron or WP Cron is running reliably on the site, particularly since stores experiencing heavy carding attacks can sometimes run into resource or scheduling interruptions.

Hopefully the 4.0.4 update or rollback test gives us a clearer picture of where this started.

Forum: Plugins
In reply to: [WooCommerce] ‘Please choose product options by visiting’ error when navigating shop
LovingBro (woo-hc)
(@lovingbro)

2 months ago
Hi @ninjabeaver,

Thank you for checking that and for clarifying the reCAPTCHA setup. I can appreciate the need to keep it enabled, especially with the carding attacks you’ve been dealing with.

Since disabling the reCAPTCHA integration did not change the behaviour, that likely rules it out as the direct cause. From the earlier network test, the repeated ?wc-ajax=ppc-simulate-cart requests are still pointing back to the WooCommerce PayPal Payments plugin performing background cart simulations, which appears to be where the notice is getting added to the session.

I also reviewed the System Status Report you shared, and I can see you are using the Storefront theme directly, without additional variation plugins or custom product option plugins active, which helps narrow things down further.

At this stage, could you please try the following temporary test:
1. Temporarily disable the WooCommerce PayPal Payments plugin entirely
2. Clear your site and browser cache
3. Test navigating again between variable and simple products
4. Check if the notice still appears
This will help confirm whether the issue is specifically coming from the WooCommerce PayPal Payments plugin itself, rather than only the reCAPTCHA integration.

I also noticed there are a few failed scheduled actions in WooCommerce → Status → Scheduled Actions. While they may not be directly related to this issue, it would still be worth checking if any of them are connected to PayPal Payments.

Looking forward to your findings.
Forum: Plugins
In reply to: [WooCommerce] Conditional fields for the block checkout – Show Fields Based on Cart Contents
LovingBro (woo-hc)
(@lovingbro)

2 months ago
<span style=”font-size: inherit; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;”>Hi @james-feaver,</span>
Thank you for sharing those additional findings and the updated code snippet. I can see why this has been frustrating, especially after already running into inconsistencies in the documentation.
Looking at the latest snippet you shared, there does appear to be a syntax issue in the required argument:
```
<code class="language-php">'required' => false, [
```
The required parameter should either be a boolean:
```
<code class="language-php">'required' => false,
```
or a conditional array, but not both together. The extra [ after false would lead to malformed field registration and could explain the inconsistent checkout behaviour and generic checkout errors you are seeing with certain product IDs.
Your code should look more like this:
```
<code class="language-php">add_action( 'woocommerce_init', function() {

	if ( ! function_exists( 'woocommerce_register_additional_checkout_field' ) ) {
		return;
	}

	woocommerce_register_additional_checkout_field(
		array(
			'id'       => 'code-snippets/fragile-handling',
			'label'    => 'Enter name',
			'location' => 'order',
			'type'     => 'text',
			'required' => false,

			'hidden' => [
				'cart' => [
					'properties' => [
						'items' => [
							'not' => [
								'contains' => [
									'enum' => [ 5229 ]
								]
							]
						]
					]
				]
			]
		)
	);
});
```
One additional thing worth checking is whether the failing product IDs belong to product variations rather than the parent variable product itself. The cart condition may require the actual variation ID instead of the parent product ID in some cases.
Could you please test again with the corrected syntax above and confirm whether the issue still occurs with the same product IDs?
I look forward to your update.
Forum: Plugins
In reply to: [Google for WooCommerce] GA4 Ecommerce Events Not Appearing

LovingBro (woo-hc)
(@lovingbro)

2 months ago

Hi @mmk175,

Thank you for the detailed explanation and troubleshooting steps you’ve already carried out. I can see why this would be confusing, especially since the network requests appear to show ecommerce related events being sent.

One important clarification here is that the Google for WooCommerce plugin itself is primarily responsible for Google Merchant Center integration and product sync functionality, it does not handle Google Analytics 4 ecommerce event tracking directly.

To help narrow this down further, could you please let us know which Analytics plugin or integration you are using to connect GA4 to your site?

For example, are you using:
– Google Site Kit
– WooCommerce Google Analytics Integration
– Google Tag Manager
– GA4 via custom code
– Another analytics or tracking plugin

Could you also please share your WooCommerce System Status Report so we can check for anything else that may be affecting tracking behavior? You can find it via: WooCommerce → Status → Get system report → Copy for support. Please share it using: https://pastebin.com or https://gist.github.com

Once we can confirm which plugin or integration is actually handling the GA4 events, we’ll be in a much better position to guide you further.

Viewing 15 replies - 61 through 75 (of 3,134 total)

← 1 2 3 4 5 6 … 207 208 209 →