Forum Replies Created

Viewing 15 replies - 1 through 15 (of 75 total)
  • Plugin Support Ian Misner

    (@ianmisner)

    We really appreciate the kind words, thank you! If you ever need anything else, please reach back out to support.

    Always happy to help!

    Plugin Support Ian Misner

    (@ianmisner)

    Hi there,

    I definitely see your points around trust-conscious merchants. It’s a fair UX consideration, especially if you’re particularly sensitive to trust signals and privacy. I’m not 100% sure this is a behavior we should change in the CheckoutWC plugin, however.

    We try to strike a balance here: we default to respecting your explicit uncheck, but we assume a change to the email could signal a different choice.

    Most merchants want the checkbox to re-enable if the email changes because different email = potentially different customer intent. It’s also the standard pattern in identity-first checkouts, as you’ve noted. This is generally because the data shows that this has no negative impact on checkout conversion but has a positive correlation with either identifying or generating repeat buyers on a store.

    We’re definitely open to continued UX refinements if we see a larger pattern of feedback around this.

    In the meantime, we do actually offer a code snippet in our documentation to solve for changing the checkbox behavior on email validation. It allows you to set the default state for that checkbox to unchecked.

    Please let me know if you had additional questions or feedback. We really appreciate it!

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Thanks so much for the kind words, @fightsmarttrav. We try to make sure the free version offers everything you’d need to really benefit from the biggest bump in conversion rates with CheckoutWC, but I’m happy to hear the move into premium has been a good experience for you too.

    Please don’t hesitate to reach out if you have any other questions!

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hi there,

    We’ve run a few tests and are unable to replicate this issue. I’ll close this out as resolved as you have not followed up, but if you have any further difficulties, please don’t hesitate to open a new thread or reach out to our team directly. We’re more than happy to help!

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hi there!

    Just a quick followup as per Ruel’s note: we’ve queued this up and you should see it updated in the next plugin release. Thanks so much for alerting us to the nuances there! Please don’t hesitate to reach out with any additional translation improvement recommendations. We really appreciate it!

    Anything else we can help with?

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hey there,

    Thanks so much for sharing the solution here! This line removes the Kalium theme’s function kalium_woocommerce_single_product_add_to_cart_handler from the woocommerce_add_to_cart_redirect hook – so it looks like they have some custom cart handling in their theme that we’re not accounting for.

    I’ve sent a message to the team over at Kalium to see if we can get this fixed up through improved compatibility on one side or the other.

    In the meantime, let us know if you have any other questions!

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Thanks so much for the kind words, @jameslibb, we really appreciate it!

    Plugin Support Ian Misner

    (@ianmisner)

    Hey there,

    Thanks for contacting us regarding Custom Add to Cart for WooCommerce. I’m happy to help!

    I just tried this out on Storefront with WooCommerce and our plugin on the most recent version and things are working as expected. You could also try navigating to the correct fields by going to the plugins list and clicking the Settings link next to our plugin.

    If that does not work, would you mind confirming what versions of Storefront and WooCommerce you’re using?

    Thanks!

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hey @heijko!

    Since WooCommerce has integrated an EIN into the core product, we don’t intend to make further updates to this plugin at this time. While we are open to specific requests that are not covered by the WooCommerce implementation, they’ve really covered what the majority of users needed this for.

    You can read up on their implementation, added in WooCommerce 9.2.

    So for your particular request, is there something that you’re unable to do with the official implementation that you’re attempting to use our plugin to overcome?

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hey there!

    Ian here, jumping in for Juan. Thanks so much for reporting this issue! This is a bit of a quirk as a result of some underlying changes in WooCommerce that we haven’t addressed, as no one has reported any concerns. We’ll get a fix queued up to make this behavior more standard in an upcoming release. In the meantime, Juan’s code snippet should work.

    We’ll drop a note here when the fix should be available for anyone who happens on this thread in the future. In the meantime, let us know if you have any questions!

    Cheers!

    Plugin Support Ian Misner

    (@ianmisner)

    Hey Andre,

    We were working on updates for HPOS, but have not completed it as this functionality is now available in WooCommerce Core. https://developer.woocommerce.com/2024/09/12/woocommerce-9-3-optimizations-accessibility-improvements-and-more/#more-8760610

    My recommendation is to export the fields stored in our meta field and upload it to Woo core. The field is hwp_product_gtin and can be mapped directly to the new core field.

    Does that work?

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hi there,

    If you’re looking to export the field from our plugin to import into the other, you could do so by using any exporter that will export product meta fields, including the default WooCommerce product exporter.

    The field is hwp_product_gtin

    In the meantime, I should probably bring to your attention that WooCommerce has introduced a GTIN field in Woo itself as of version 9.3.0: https://developer.woocommerce.com/2024/09/12/woocommerce-9-3-optimizations-accessibility-improvements-and-more/#more-8760610

    Cheers,

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hey Christophe,

    Thanks for letting me know you found a solution to your most recent question! The Barn2 team originally developed this plugin and some of the documentation hasn’t been moved over. Thanks for bringing this to our attention 🙂

    Please let me know if you have any further questions!

    Ian

    Plugin Support Ian Misner

    (@ianmisner)

    Hi there,

    You can insert the shortcode just about anywhere in WordPress. Based on your current placement on the URL you provided, it appears you’re using a Widgetized footer. So to add this, you would go to the footer area, remove Better Recent Comments and add a Shortcode block instead.

    Can you try that out and let me know if it works for you?

    Plugin Support Ian Misner

    (@ianmisner)

    Hi there,

    Thanks for the question, I’m happy to help!

    In the default widget settings, there is currently no way to modify the size of the avatar in the settings, as you’ve found. We don’t intend to modify this at this time, but there’s some good news:

    1. You could modify the widget with CSS by targeting the avatar class
    2. Or you could use the shortcode to render Better Recent Comments, which gives you access ot the avatar_size option

    For example, this will show the comments with a much larger avatar:

    [better_recent_comments number="15" date_format="F j, Y" format="{avatar} {author} on {post}: “{comment}” {date}" avatar_size="150"]

    Where you can change the 150 value to fit your preferred size.

    So while CSS might work, I’d recommend switching to the shortcode and using these values to generate the larger avatar.

    Let me know if you have any questions!

    Cheers,

    Ian

Viewing 15 replies - 1 through 15 (of 75 total)