monomatic

Did you resolve this @rabbitwordpress ? We seem to be having a similar issue.

@kristymix The change is applied instantly for us. @enfueggo (JustinV) suggested the same method above. I doubt cache, at least page cache. object cache? same in new session/incognito?

for anyone experiencing this, it can be disabled within your Stripe settings (in stripe dashboard, not WC):

Stripe Dashboard > Settings > Link in the Payment Request Button

Same issue:
UK merchant. Changelog for 7.0.0 states:
Add - Restrict the Link payment method only for US merchants.

We have Link payment button displayed at cart, no option to disable in stripe payment settings.
It does work, and we may use it, but would rather be able to control and test it first – we run subscriptions, multi-region, multi-lingual.. definitely some scope for issues.

WooCommerce 7.0.0
WooCommerce Stripe Gateway 6.9.0

• This reply was modified 2 years ago by monomatic.
• This reply was modified 2 years ago by monomatic.

@gioni – agreed. Klaviyo are gaining a lot of traction these days and use AWS, I’m surprised their infrastructure works like this.

I believe our issue was that we were using JWT auth, which caused problems with wp-cerber (it would identify consumer_key as non-existent username, impacting several external services and requiring white-listed IPs). Since disabling this we have klaviyo working and our other services aren’t being incorrectly picked up by wp-cerber.

Thanks.

I do have the following in Traffic Inspector > Settings > Request Whitelist:

{\/wp-json\/klaviyo\/*}

That’s excellent, thank you.

..and while I’m here, including a hashed version of the user’s email address in the payload would be really handy, required by some trackers for privacy/anonymity (eg. fbevents, pinterest). If in the datalayer it can be picked up directly in gtm for embedding these through tags.

Perhaps also worth mentioning that /cart /checkout /order-received are typically all excluded from page caching, so transaction tracking data can still be generated with the page as normal, it’s just that user & cart items payload on all other pages that we’ve been having trouble with.

Hi.

I think we would use this if it were available, even though it would be one more request. to explain our use case:

With no page caching we typically have 1.2 – 1.8 second page generation, wp-rocket reduces this around 100-400ms (but a bit variable, sometimes longer).

We have implemented one post-load ajax request for mini-cart content + geoloate for the same reason we are discussing, so that the page is independent of the visitor and the same cached version can be served to all.

The post-load ajax request takes around 500ms, but is fired when the page is loaded, limiting its impact on performance metrics (important this year with Core Web Vitals).

Additionally, we are using wp-rocket’s delay execution facility so that GTM, a dozen other trackers and some other scripts aren’t executed until there is some interaction from the user (move/scroll/click/key). Perhaps not for everyone but it’s working for us, the performance gain is significant, particularly in google’s strict CWV assessment.

I expect I am underestimating the amount & complexity of data gtm4wp collects and presents, but.. If GTM4WP could load dynamic data in an ajax request I think we would use it. If the output was available through a do_action or do_shortcode that would give a little extra versaility, we could include it in our existing single ajax call.

Not sure if that helps, or if I’m missing some key problem of the issue…

Thanks
G

@mrlim Did you find a solution to this? I’m looking to do exactly this

Unless you’ve done something to use a different template for the loop, it’ll use the defualt loop regardless of what the post_type is.

To output the custom field on the page, you need to do this:

<?php
$ln = get_post_custom_values(‘latin_name’);
echo $ln[0];
?>

see function refernece here:
https://codex.www.ads-software.com/Function_Reference/get_post_custom_values