frensis

Hi Peter, thank you for your clarification.
“Local changes” status was due to slightly differences like spaces in notification emails list.

Anyway I didn’t know “Review changes” feature… I got it!

Hello there… I only get back into this right now, sorry for the delay.
After few tests I found something which could cause an issue about styling credit cards fields: I’m using a child theme for Storefront and I started style from scratch dequeuing parent templates:

add_action( 'wp_enqueue_scripts', 'sf_child_theme_dequeue_style', 999 );
function sf_child_theme_dequeue_style() {
    wp_dequeue_style( 'storefront-style' );
    wp_dequeue_style( 'storefront-woocommerce-style' );
}

If I comment these lines, credit cards fields inherit some style and they look better.
But for me isn’t possible to apply default Storefront style cause I will loose tons of ready-made work.

Is there a way to get style only for woopayments iframe? Or dequeue all except checkout payment fields?

Hi @shameemreza, thank you for your reply… I will check with Storefront (parent) and deactivating other plugins.
Anyway, I read somewhere that I need to wait 24h to see changes: is it right?
If so, is it possible to force changes to see it quickly?

Thank you @doublezed2 …. I only followed @ckadenge reply.
https://www.ads-software.com/support/topic/stripe-checkout-fields-background-colour/page/2/#post-17997661

I’m replying just to subscribe to future updates because no-one solution found on these pages works for me.
Everyone link these pages:
https://woocommerce.com/document/stripe/customization/style-payment-form/
https://woocommerce.com/document/woopayments/customization-and-translation/customize-payments-appearance/

No changes appear to me, no matter what I did.
Clear transient via the code below broke the site:
delete_transient( 'wcpay_upe_appearance' );
delete_transient( 'wcpay_wc_blocks_upe_appearance' );

Is’t easier and less time-consume for everyone to post an how-to video?

Folks just asking for 3 simple options:

• font color
• fields background
• fields borders

I suppose these things are easier then collecting payments all over the world in different currencies, from different methods ??
Please help lot of wp developer!

After a quick search, I suppose the issue is due to something in this part of code in this file:
/wc-fields-factory/assets/js/wcff-client-src.js

I hooked field outside form cart with a custom hook but this code clone fields in form.cart on submit even if validation results fails for one/some field.

The logic should check for a previous failed validation and update cloned fields rather than create new ones at every click on submit.

Is it right?

/**

*

* Last minute cleanup operations, before the Product Form submitted for Add to Cart

*

*/

$(document).on( "submit", "form.cart", function() { console.log("on submit called");

// To remove hidden field table

$(".wcff_is_hidden_from_field_rule").remove();

if (typeof(wccpf_opt.location) !== "undefined") {

var me = $(this);

$(".wccpf_fields_table").each(function() {

/* Make sure it is not from related products - If show archive enabled then this happens */

let liParent = $(this).closest("li.product");

if (liParent && liParent.length > 0) {

return;

}

if ($(this).closest("form.cart").length == 0) {

var cloned = $(this).clone(true);

cloned.css("display", "none");

/* Since selected flaq doesn't carry over by Clone method, we have to do it manually */

/* carry all field value to server */

if ($(this).find(".wccpf-field").attr("data-field-type") === "select") {

cloned.find("select.wccpf-field").val($(this).find("select.wccpf-field").val());

}

me.append(cloned);

}

});

}

});

• This reply was modified 6 months, 3 weeks ago by frensis.

remove_action( 'wpcf7_swv_create_schema', 'wpcf7_swv_add_select_enum_rules', 20, 2 );

This code in functions.php works for me.
Is it possible to be more specific and deactivate validation only for certain form (eg. by form id)?

Hello Xue,
for everyone who may be interested, I created a ticket to Woocommerce.com and after an investigation support team wrote me that errors was about old Stripe plugin (the one I replaced with Woocommerce Plugin).

The suggested solution was to delete that endpoint url in Stripe Dashboard.

Some issues can be generated only by subscription products (they say).

Hello Igor, you are right… I replaced WC Stripe Payment gateway with the WC Payments.

I received email after switching to WC Payments, and this is the message (original email was in Italian, I searched it in English on the web -something may diverge-):
“We’re contacting you because we’re still having trouble delivering data to a webhook endpoint associated with your account in live mode. Webhooks are used to notify your server about events that happen in your Stripe account, such as a payout completing or an invoice being created.

You or someone on your team has added that endpoint in your Stripe webhook settings, which you can view and edit here:?https://dashboard.stripe.com/account/webhooks.

Please note that in most cases a failing webhook does not impact your payments or payouts. However, if you use subscriptions we rely on your webhook endpoint to notify you of new invoices. These invoices may be delayed for up to three days if your webhook is unable to successfully receive them. If you use Checkout, you may be handling the?checkout.session.completed?event as part of your purchase fulfillment process as described here:?https://stripe.com/docs/payments/checkout/fulfillment#webhooks. If you do, failure to handle these events may interfere with purchase fulfillment.

We’ve attempted to notify the endpoint 17 times since Aprile 25, 2023 at 03:47PM. If this endpoint is important to your application, please try and fix the issue. If you do not need the webhook endpoint you can delete it from your Stripe webhook settings. We will stop sending notifications to your webhook by May 4, 2023 around 03:47PM.

Here is the summary of errors we have received when sending you webhooks:
17 requests had other errors while sending the webhook event.

You need to return anything between a HTTP 200 to 299 for the webhook to be considered successfully delivered.
For more details on the errors, you can find your events page here:?https://dashboard.stripe.com/events.”

I’m not intentioned to switch back to WC Stripe Payment but to solve this problem… if this is really a problem!
I choosed WC Payments to integrate Google Pay and Apple Pay and this is not possible with WC Stripe Payment plugin.
Anyway credit card payments continue to work fine beside all and I’m wondering if Stripe endpoint errors may result in failed transitions or others issues.
Keep in mind that the website is the only channel where I collect orders and payments so communication should be only in one direction: from the website to Stripe.

Are webhooks only needed for communications from Stripe to website?
And webhooks are really necessary to collect payments on my website? The message says “If you do not need the webhook endpoint you can delete it from your Stripe webhook settings“

Could you be more clear about it?
Thank you