Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter develobaby

    (@bornefysioterapi)

    Stellar!

    Solved in under 3 hours. Works. Closed.

    ★★★★★

    Thread Starter develobaby

    (@bornefysioterapi)

    Oh, perfect, thanks for your super-quick response. And thanks for confirming an issue specific to PayPal in the plugin.

    I did not intend to report an issue wrt MobilePay or ApplePay, I just used them as examples to describe, what I used to see in the WC backend for PayPal – so no issue there! 👍

    And you are right. Country exceptions are custom code and as long as PayPal returns as first-class-citizen in WC, existing custom code handling available payment methods per country will work again. I referenced “creditcard, paypal, !paypal-dk” as the content for the field “payment methods” in section “Extra Gateway Settings” on page “admin.php?page=wc-settings&tab=checkout&section=quickpay&from=WCADMIN_PAYMENT_SETTINGS”. There is a link to learn.quickpay.net, which describes negations with the example: “creditcard, !jcb, !visa-us”. I don’t think, this is really plugin related, at all. It’s just a config string that the plugin sends to the QuickPay Gateway and the gateway simply doesn’t handle the case “creditcard, paypal, !paypal-dk” the way, I would expect it to be handled, given that the docs example does something very(!) similar for visa. So, but … none-issue in the WP-plugin, I suppose.

    Thread Starter develobaby

    (@bornefysioterapi)

    Folks,

    The issue appears to have been solved for me (and please note that I am the ticket op).

    I uploaded my WC-status report as requested by the Webtoffee team and it took them 24 hours to figure out that this was caused by a plugin conflict with another payment gateway plugin (QuickPay). Because this conflict was introduced in v5.0, they fixed it in a test version and I could confirm that it works. The whole process took them 24 hours.

    I will close this ticket now, as my issue is solved and because it is unlikely that any of you also use QuickPay – a Danish payment gateway.

    (I can only encourage you to create separate tickets for separate observations. “Me too” isn’t a thing in software support. Rather, the vendor determines a common theme across tickets.)

    Thanks to the WebToffee-team & Best wishes to everybody else!
    Maria

    Thread Starter develobaby

    (@bornefysioterapi)

    Hey Sean, thanks for your swift responses and for looking into this … all makes perfect sense!

    Best, Maria

    Thread Starter develobaby

    (@bornefysioterapi)

    Uuh – nice! Thank you, Dennis!

    Here’s a crude example (without any error handling) for anybody in a similar situation:

    add_action( 'wp_loaded', function() {
    $post_tx = array(
    'en_US' => 111, // adjust this array to your locales and post ids
    'da_DK' => 222, // (do this right or your will regret it!)
    'de_DE' => 333,
    );
    foreach(msls_blog_collection()->get_objects() as $blog) {
    $locale = $blog->get_language();
    $switch = $blog->userblog_id != get_current_blog_id();
    if ($switch) switch_to_blog($blog->userblog_id);
    $key = 'msls_' . $post_tx[$locale];
    $value = $post_tx;
    unset($value[$locale]);
    add_option($key, $value, '', false);
    if ($switch) restore_current_blog();
    }
    });

    Best, Maria

    develobaby

    (@bornefysioterapi)

    Hey Allan,

    Isn’t this pinned thread exactly what you are looking for?
    https://ww.wp.xz.cn/support/topic/get-the-related-page-id/

    Best,
    Maria

    Thread Starter develobaby

    (@bornefysioterapi)

    Thanks for your quick response. I appreciate it!

    1. Done.
    2. Yes, I did consider this, too. I already asked my hosting folks about the storage details and they confirmed that there is no difference between /tmp and /var/www/…/wp-content. Same physical, local disk. Same rules.

    I’ll monitor this and should it happen again, I’ll take a snapshot of the DB-file to see if it’s corrupt. I find this explanation more likely at this point.

    Again, thanks for pitching in and have great weekend!
    Uwe

    Thread Starter develobaby

    (@bornefysioterapi)

    UPDATE:

    Weirdly enough, the database file size is now at 49 megs (that is, bigger than when I first ran “flush now”), but the disk IO remains normal. Did the “Flush now” and its implicit “vacuum” (or possibly the subsequent catch block) perhaps repair a corrupt database file? That could indicate that the database file size was never the problem to begin with.

    Thread Starter develobaby

    (@bornefysioterapi)

    Thanks, Victoria!

    Thread Starter develobaby

    (@bornefysioterapi)

    Hi Shameem,

    thank you for pitching in!

    I’m not collecting health related information during the checkout, merely a billing address (literally name, street, zip, town, email). The products I sell are of educational nature on health-related topics. Is it possible that the product names themselves cause this? I’d surprised, because teh same product names are used when running meta-campaigns, so I would imagine that I’m stopped there, too. And what about the fact that these warnings only turn up for a tiny minority of sales?

    I am not aware of plugin settings that I could adjust that would trigger these warnings. I only, whats visible under wp-admin/Marketing/Facebook. Are there other places, where I could look? (FYI: I literally downloaded the plugin from the Pixel- setup page in Business Manager and installed it in my WordPress => done).

    Best,
    Maria

    Thread Starter develobaby

    (@bornefysioterapi)

    I’m not longer seeking advice on this as it appears to be a known issue:
    https://github.com/woocommerce/woocommerce/issues/34127

    Thread Starter develobaby

    (@bornefysioterapi)

    Thanks for the guidance, Lisa!

    Best,
    Uwe

Viewing 12 replies - 1 through 12 (of 12 total)