joncon62

Logically thinking, specifying 0 should disable the updates. As my podcasts will no longer be added to it seems an unnecessary use of resources to have to plugin check them. However I can live with it.

• This reply was modified 9 months, 2 weeks ago by joncon62.

Ah, thanks. I didn’t think of doing that. I was looking for a setting on the Style tab. All good now.

Thanks for the fix, I can confirm 2.2.4 works now. I have one other issue, I’ll open a new thread so you can close this one.

I am running PHP 7.4.30 on a localhost machine. I do have a console error which is:

Uncaught TypeError: Cannot read properties of undefined (reading 'contentWindow')
    at HTMLDocument.<anonymous> (tsvg-builder.js?ver=1706891953:965:48)
    at e (load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=6.4.3:2:27028)
    at t (load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=6.4.3:2:27330)

It doesn’t matter what theme I choose, I cannot change the description field using 2.2.2. Just try it yourself. Downgrading to 2.2.1 works as expected.

Thanks for the ‘copying theme’ info. I resisted trying that initially as it warned me it couldn’t be undone. Not sure why that warning is there as it’s not a destructive task.

By the way, I think your plugin is superb, the best of the video gallery plugins and I’ve tried them all!

Hi @sev,

All I did was search for statement_descriptor which you will find in the wp_options table and the option name is woocommerce_stripe_settings.

I then edited woocommerce_stripe_settings and blanked out the statement_descriptor so it looks like this:

s:20:"statement_descriptor";s:0:"";

Backup your database first or test it out on a localhost if you have that capability.

I am using your API but I was enclosing $FormField.SetText($value) in a setTimeout() function as at some point I think I needed that, but removing it makes it work. Thanks for getting back on a Sunday!

You are right, I have just created the name fields in js and can now capture the form data. The plugin is eventON which is quite well documented so I need to see if I can create the new registration fields from the captured data.

I am thinking of using the form(s) on the woocommerce checkout page so I want to capture form data with the ‘Place Order’ submit button, I’m not using the AIO submit button. I am trying to add more registration checkout fields to an order. If the form fields had a name attribute that I could define then I could get the data.

I don’t think the snippet has anything to do with the statement_descriptor problem. That’s due to the fact that at some point I must have specified it in the settings and I can no longer edit it as that option has been removed.

I have now fixed the problem by editing the option in phpMyAdmin.

This will no doubt affect other users too so I think you need to address this.

Thanks for the help so far.

It looks like I can’t use the New checkout experience because I’m using the following snippet to allow me to use multiple Stripe accounts (vendors) in one woocommerce installation.

https://www.businessbloomer.com/woocommerce-multiple-stripe-accounts/

On the checkout page I get an Unhandled payment Element loaderror in the console when I enable the New Checkout Experience.

This snippet has been working well for years but just threw up the statement_descriptor error recently on a newly created Stripe account (vendor).

Thanks for your quick reply and the snippet. Are you sure that the [statement_descriptor] and [statement_descriptor_suffix] live in the $metadata? Looking at the log they are defined one level up.

I think I need a different filter.

2024-01-08T19:45:06+00:00 DEBUG 
====Stripe Version: 7.8.1====
====Start Log====
payment_intents request: Array
(
    [amount] => 1000
    [currency] => gbp
    [description] => Snappy Tickets - Order 35759
    [metadata] => Array
        (
            [customer_name] => {removed}
            [customer_email] => {removed}
            [order_id] => 35759
            [site_url] => https://snappytickets.co.uk
        )

    [capture_method] => manual
    [payment_method_types] => Array
        (
            [0] => card
        )

    [payment_method] => {removed}
    [customer] => {removed}
    [statement_descriptor] => Snappy Tickets
)

====End Log====


2024-01-08T19:45:06+00:00 DEBUG 
====Stripe Version: 7.8.1====
====Start Log====
Error: stdClass Object
(
    [error] => stdClass Object
        (
            [message] => The statement_descriptor parameter is not supported for the payment_method_type card. To continue supporting payment_method_type card, please pass in statement_descriptor_suffix or remove the statement_descriptor parameter altogether. Please see https://support.stripe.com/questions/use-of-the-statement-descriptor-parameter-on-paymentintents-for-card-charges for additional details.
            [request_log_url] => {removed}
            [type] => invalid_request_error
        )

)

Any update on when you might publish your next release with the GC filters?

Ah! Your comment about settings answered my question. I hadn’t realised there was a settings page. I just checked the correct post type and the metabox appeared. Thanks so much.

That’s great news, thank you so much!