ph1lm

Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Forum: Plugins
    In reply to: [Payment Plugins for Stripe WooCommerce] Place Order disabled when stripe default
    Thread Starter ph1lm

    (@ph1lm)

    4 months, 2 weeks ago

    The STAGING site has v3.3.97 which is OK (we updated a while ago so v3.3.97 was the latest at the time)

    The LIVE site updated to v3.3.98 which did not enable PLACE ORDER (stripe “Credit Card” is default payment method)

    Tried Troubleshooting mode via Health Check plugin with ACF Pro, WooCommerce and Stripe Plugins enabled. (theme assumes ACF Pro is enabled!) Same problem.

    (selecting another method enabled PLACE ORDER, and selecting strip also enabled PLACE ORDER!)

    (also can swap order of methods so other is default, PLACE ORDER enabled for both)

    Also tried a default theme. Same problem.

    Installing v3.3.97 on LIVE (upload zip of that version) instead made the PLACE ORDER button enabled as expected and as per STAGING.

    Hope this helps?

    • This reply was modified 4 months, 2 weeks ago by ph1lm.
    • This reply was modified 4 months, 2 weeks ago by ph1lm.
    • This reply was modified 4 months, 2 weeks ago by ph1lm.
    Forum: Plugins
    In reply to: [Payment Plugins for Stripe WooCommerce] Place Order disabled when stripe default
    Thread Starter ph1lm

    (@ph1lm)

    4 months, 2 weeks ago

    When we had the same versions on a STAGING site but with Stripe in TEST mode, the PLACE ORDER button was working.

    Actually on STAGIING we have Stripe v3.3.97

    Updating to v3.3.98 on STAGING causes the PLACE ORDER button to be not active, as per LIVE.

    Uploading the v3.3.97 files back causes the PLACE ORDER button to be active again.

    • This reply was modified 4 months, 2 weeks ago by ph1lm.
    • This reply was modified 4 months, 2 weeks ago by ph1lm.
    Forum: Plugins
    In reply to: [Payment Plugins for Stripe WooCommerce] Place Order disabled when stripe default
    Thread Starter ph1lm

    (@ph1lm)

    4 months, 2 weeks ago

    As a workaround we have swapped the order of the payment methods so PAYPAL is DEFAULT.

    The PLACE ORDER button works for both methods now.

    Forum: Plugins
    In reply to: [DynaMo] Warning: fread(): Length parameter must be greater than 0 mo-reader.php on line
    ph1lm

    (@ph1lm)

    4 years, 3 months ago

    I have this same error.
    The filename is wp-content/languages/wpml/wordpress-ja.mo
    and the value is zero

    Not sure how to show you this file!
    The content of the file is this hex:

    DE 12 04 95 00 00 00 00 07 00 00 00 1C 00 00 00 54 00 00 00 00 00 00 00 8C 00 00 00 00 00 00 00 8C 00 00 00 18 00 00 00 8D 00 00 00 18 00 00 00 A6 00 00 00 11 00 00 00 BF 00 00 00 07 00 00 00 D1 00 00 00 10 00 00 00 D9 00 00 00 0B 00 00 00 EA 00 00 00 00 00 00 00 F6 00 00 00 10 00 00 00 F7 00 00 00 0B 00 00 00 08 01 00 00 07 00 00 00 14 01 00 00 07 00 00 00 1C 01 00 00 10 00 00 00 24 01 00 00 0B 00 00 00 35 01 00 00 00 55 52 4C 20 70 72 6F 64 75 63 74 5F 63 61 74 20 74 61 78 20 73 6C 75 67 00 55 52 4C 20 70 72 6F 64 75 63 74 5F 74 61 67 20 74 61 78 20 73 6C 75 67 00 55 52 4C 20 73 6C 75 67 3A 20 70 72 6F 64 75 63 74 00 70 72 6F 64 75 63 74 00 70 72 6F 64 75 63 74 2D 63 61 74 65 67 6F 72 79 00 70 72 6F 64 75 63 74 2D 74 61 67 00 00 70 72 6F 64 75 63 74 2D 63 61 74 65 67 6F 72 79 00 70 72 6F 64 75 63 74 2D 74 61 67 00 70 72 6F 64 75 63 74 00 70 72 6F 64 75 63 74 00 70 72 6F 64 75 63 74 2D 63 61 74 65 67 6F 72 79 00 70 72 6F 64 75 63 74 2D 74 61 67 00

    Forum: Plugins
    In reply to: [DynaMo] _n broken when DynaMo active but not when inactive
    Thread Starter ph1lm

    (@ph1lm)

    4 years, 4 months ago

    I have another site that uses en_GB lanaguage, so uses MO files, but NOT WPML. It does use Query Monitor.
    In output/html/overview.php line 374 I get the same sprintf() fatal error.
    The fix for cached values I used above does not work, I needed a similar fix for “\0” translations at line 137 to catch the non-cached translations.

    esc_html__( ‘%s S’, ‘query-monitor’ ) was returning BOTH singular AND pural translations which is WRONG (esc_html__ calls ->translate)

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