Forum Replies Created

Viewing 15 replies - 16 through 30 (of 197 total)
  • Thread Starter eclev91

    (@eclev91)

    I would ask at this juncture that you take the minimum steps to try to reproduce this issue yourself. I assume this will get you there:

    1. New WordPress install
    2. Install Woo
    3. Do the Woo setup (cart and checkout pages built with blocks)
    4. Set up a single flat rate shipping option? This is the only spot where things might get goofy
    5. Set Default Customer Location to “Geolocation (with page cache support)”
    6. Create a product
    7. Add product to cart
    8. Go to cart
    9. See “No shipping rates available” message, assuming the geolocation feature has managed to at least identify your country.
    Thread Starter eclev91

    (@eclev91)

    Yep, did that, issue persisted.

    Disabled “Default customer location” and that resolved the issue, which is to say, the label updated to say “Enter address for shipping options” (or something roughly equivalent to that). Re-enabled with “Geolocation (with page cache support)” and the issue came back. So I’m pretty sure that’s the issue.

    In fact, once I re-enabled that, I even got it to figure out I was in Oregon. So now it has the State and Country, but that’s still not enough for it to generate delivery options.

    Thread Starter eclev91

    (@eclev91)

    If you’re curious, staging environment here with blocks re-enabled: https://stg-rosehillsourdoughcom-staging.kinsta.cloud

    u – staging
    p – secretsecret

    But like I said, we’ve been unable to replicate the issue, and any impacted draft orders have long since been cleaned up by WooCommerce.

    Thread Starter eclev91

    (@eclev91)

    @doublezed2 I’m working on a staging environment for you.

    https://www.loom.com/edit/b1bc7bdeca8348a3a60d4815c6be4de0

    Reproduced @d0153 . Might be specific to being nested in other blocks. @bc0123 is that your experience?

    • This reply was modified 1 year, 4 months ago by eclev91.
    Thread Starter eclev91

    (@eclev91)

    Hi @doublezed2 , I appreciate your recommendation, but we’re going to switch back to shortcodes at this time. We simply don’t have the bandwidth to troubleshoot an issue we’re having trouble recreating, and if your team is unaware of any larger issues, then this ticket at least makes a nice data point if your team has other reports. I have been keeping an eye on this – https://github.com/Automattic/woocommerce-payments/issues/9939

    On the caching, I do have a couple thoughts:

    • You said “the JavaScript responsible for handling the button click action is not working properly”. That could certainly be true, but given draft orders are successfully generated without billing addresses, it seems like JS-driven AJAX requests are working just fine. I think it’s more likely that there’s some kind of validation error on the billing fields (which shouldn’t be validated at all when the “use same address” checkbox is checked), and if there are inline validation messages, they’re hidden to the end user because the “use same address” checkbox is checked.
    • Opening the site in an incognito window should give me the cache-iest of cached versions of the page, so you would think we would be able to reproduce if it were a cache issue.
    • It’s unclear to me why checkout is so dependent on Javascript that it might fail completely. I would hope, given checkout is a single point of failure for eCommerce sites, that the checkout form would more degrade more gracefully.
    Thread Starter eclev91

    (@eclev91)

    Hi @doublezed2 ,

    • I already shared the URL via the “The page I need help with…” field
    • Like I originally shared, “some customers”. More than one, and the issue has persisted.
    • I already shared “Unfortunately, I haven’t been able to replicate this issue myself, and haven’t yet gotten more browser information from any customers experiencing this issue.”

    But I do know it isn’t limited to one browser. At a minimum, we’ve had reports from Firefox, Brave, and I believe there was at least one mobile Safari complaint.

    Our plan is to revert to shortcode-based checkout later this week.

    I can’t speak to the wide variety of issues encountered by users here, but seeing a fix to dynamically declared properties would really be appreciated.

    Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$button_appearance_title is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374

    Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$enable_paypal_credit is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374

    Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$button_preview is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374

    Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$connection_settings is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374

    Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$pay_later_messaging_logo_type is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374

    Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$pay_later_messaging_logo_position is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374

    Deprecated: Creation of dynamic property WC_Gateway_Braintree_PayPal::$pay_later_messaging_text_color is deprecated in .../plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php on line 374
    Thread Starter eclev91

    (@eclev91)

    Just walked through the new migration workflow @jeffpaul. Worked great. Thanks so much!

    • This reply was modified 1 year, 7 months ago by eclev91.
    Thread Starter eclev91

    (@eclev91)

    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in .../wp-includes/functions.php on line 7300
    Call Stack
    # Time Memory Function Location
    1 0.0010 408416 {main}( ) .../index.php:0
    2 0.0012 445136 require_once( '...wp-admin/admin.php ) .../index.php:10
    3 0.3560 37487320 require( '...wp-admin/menu.php ) .../admin.php:158
    4 0.8579 40405536 require_once( '...wp-admin/includes/menu.php ) .../menu.php:412
    5 0.8596 40444528 do_action( $hook_name = 'admin_menu', ...$arg = variadic('') ) .../menu.php:161
    6 0.8596 40444744 WP_Hook->do_action( $args = [0 => ''] ) .../plugin.php:517
    7 0.8596 40444744 WP_Hook->apply_filters( $value = '', $args = [0 => ''] ) .../class-wp-hook.php:348
    8 0.8623 40567392 Tribe__Tickets__Commerce__PayPal__Orders__Report->register_orders_page( '' ) .../class-wp-hook.php:324
    9 0.8623 40567640 add_submenu_page( $parent_slug = NULL, $page_title = 'PayPal Orders', $menu_title = 'PayPal Orders', $capability = 'edit_posts', $menu_slug = 'tpp-orders', $callback = [0 => class Tribe__Tickets__Commerce__PayPal__Orders__Report { public $orders_page = NULL; public $orders_table = NULL }, 1 => 'orders_page_inside'], $position = ??? ) .../Report.php:163
    10 0.8623 40567640 plugin_basename( $file = NULL ) .../plugin.php:1478
    11 0.8623 40567640 wp_normalize_path( $path = NULL ) .../plugin.php:769
    12 0.8623 40567640 wp_is_stream( $path = NULL ) .../functions.php:2182
    13 0.8623 40567640 strpos( $haystack = NULL, $needle = '://' ) .../functions.php:7300

    This is me copying and pasting the XDebug output. But I’ve linked the line in your source code that is problematic. Regardless of whether or not WordPress gracefully handles what comes next (see above – it does not), you’re calling add_submenu_page in an unexpected and unintended way.

    This can be traced back to a fatal error the plugin is throwing:

    PHP Fatal error:  Uncaught TypeError: implode(): Argument #1 ($array) must be of type array, string given in .../wp-content/plugins/events-block-for-the-events-calendar/includes/ebec-block.php:93

    I run into a similar, perhaps related, issue every time I update the plugin. On my first page load or attempt to do something with WP-CLI, I get the same JSON feedback reported above:

    {"success":false,"data":{"message":"You're not allowed to do this","from":"mailchimp-for-woocommerce"}}

    This happens on a few different sites. Worth noting that “updating” the plugin is not being done via the WP interface or WP-CLI, but via Composer.

    Thread Starter eclev91

    (@eclev91)

    @shameemreza Do you ask non-technical users to submit tickets on GitHub?

    Seems like the minimal thing that the WP.org plugin support team for Woo could do is translate technical bugs over to the GitHub repo.

    But now that I’ve debugged the issue that your support did not debug on a previous thread, I will also report it on the GitHub repo. I look forward to being asked to implement the fix as well.

    • This reply was modified 1 year, 10 months ago by eclev91.
    Thread Starter eclev91

    (@eclev91)

    FWIW, the workarounds in the linked article are more complicated than they need to be. It has nothing to do with space or semi-colons. Just getting the browser to repaint the field will fix it. I went ahead and hooked into admin_print_scripts to get this working for us in the meantime:

    add_action('admin_print_scripts', function() {
    ?>
    <script>
    document.addEventListener('DOMContentLoaded', function() {
    var emailInput = document.getElementById('customer_email');
    if (emailInput && navigator.userAgent.indexOf('Safari') != -1 && navigator.userAgent.indexOf('Chrome') == -1) {
    var emails = emailInput.value;
    emailInput.value = emails;
    }
    });
    </script>
    <?php
    });
    • This reply was modified 1 year, 11 months ago by eclev91.
    Thread Starter eclev91

    (@eclev91)

    I figured this out. Someone before me had set the global content area spacing to 0 in the Customizer, which is what the setting described above handles on a page-by-page basis.

    Moving to unboxed removed the spacing I was concerned about.

Viewing 15 replies - 16 through 30 (of 197 total)