florianbepunkt

Okay, found the issue. In case someone else experience a similiar problem: Our CD pipeline accidentally committed the w3tc-config folder (inside wp-content) to source control and deployed this folder on every CD run, thereby resetting the production specific settings.

Danke!

Hello @robert681

this error still exists in /wp-content/plugins/wp-security-audit-log/classes/Sensors/WooCommerce.php on line 983

The reason for this is that the $product object has no post status property

Sorry, I was not clear enough. This is not what this was about.

We use a third-party-consent management plugin (Borlabs Cookie) that implements gtag.js

There are two scenarios:

(1) User gives consent to being tracked -> gtag.js is loaded
(2) User gives no consent to being tracked -> gtag.js is NOT loaded

We use your plugin only for the enhanced ecommerce functionality.

Problem: Your plugin throws errors if gtag.js is not loaded.
Suggestion: Your plugin should check if gtag.js is loaded before executing your js

All current consent/opt-in solutions for GA work the same: They only load gtag.js if the user has agreed to it.

hey @patrickha

can you give q uick overview on how to implement invisible reCaptcha plugin with TML? Or does it work just out of the box?

Thank you,
Florian

@chrleth Hey ChrLeth, have you found a solution for this? I have the exact same use case but can’t find a solution.

• This reply was modified 7 years, 11 months ago by florianbepunkt.

To be more specific: How can I add my own WC ajax action?

I tried with a normal wp_ajax action. My function triggers an ajax call when country field changes on checkout page. On php side the function is super simple

function() {
$packages = WC()->shipping->get_packages();
FB::log($packages, ‘$packages’);
}

The function gets triggered, but $packages is empty (which it shouldn’t be).

@anphira Okay, I see. PayPal Pro is available in the US only.

@anphira – thank you. is it possible to process paypal payments directly on the site?

Hi Mike,

so there is no chance to bypass this validation except modifying the core? I know how to disable it in wc-form-handler class but it would be nice if I could spare myself the hassle with messing around with core files. Are there any plans to add such a hook in the future?

I think there are plenty of use cases where this would be helpful… I’m working on a project that sells digital memberships and users will assume that their billing data (especially) their billing name will be their account names as well.

Thanks,
Florian