Forum Replies Created

Viewing 15 replies - 196 through 210 (of 479 total)
  • Plugin Author RLDD

    (@rermis)

    Thank you for the heads up. I’ve found the issue, and predictably it’s related to the virtual order. I’ll make sure the fix is included in the next release!

    Plugin Author RLDD

    (@rermis)

    Hi @flytrap21,

    Thank you for the insight you’ve provided. I looked into the capabilities of the woocommerce_cart_shipping_packages filter you mentioned and it makes sense now. I understand you’ve chosen to group by shipping class and there is also the functionality to group by various items, or even custom meta.

    I’ll look into this a bit further since you’ve given me a head start. Maybe the estimates could be continued to be stored as they are now, but with one additional option that associates them to a individual shipping package. If there are any future updates on this top, I’ll be sure to post them here. Thank you!

    • This reply was modified 3 years, 4 months ago by RLDD.
    Plugin Author RLDD

    (@rermis)

    Hi @flytrap21,

    Thank you for this recommendation to improve the Ship Estimate for WooCommerce. Natively, WC handles one shipment per order, so the shipping estimate plugin runs in the cart and checkout pages. It calculates once based on the ship method and products only at the time of checkout, assumes the contents of the cart will ship together, and stores the final estimate on the order level.

    I assume you must have a plugin or add-on to WC that builds in a feature to allow multiple shipments per order. Compatibility for multiple shipments per order might require the ship estimate plugin to know which products ship together, or reassess the estimate at every shipment, and store the data per shipment level instead of per order. It’s a great concept. Factoring in the complexity, such a feature would likely only come to life in the form of a paid (or pro) plugin.

    Nevertheless, I’ll certainly make note of your request as it would be a great way to make this a well rounded fully featured plugin.

    Plugin Author RLDD

    (@rermis)

    Awesome, thanks for confirming. Fix has been released as version 2.2.4.

    Plugin Author RLDD

    (@rermis)

    Hi @homu9,

    Can you try adding this on line 137 ?

    global $woocommerce,$coupon_codes; // add under this line
    if(!is_object($woocommerce->cart)) return;

    If this works, I’ll release it asap.

    • This reply was modified 3 years, 4 months ago by RLDD.
    Plugin Author RLDD

    (@rermis)

    Hi @homu9 ,

    Thank you for reporting this issue. Can you let me know which version of WooCommerce is installed? And PHP version if possible? Did this issue begin after any recent upgrade of WC?

    Plugin Author RLDD

    (@rermis)

    Hi @titsmaker,

    Today’s release resolves the locations in admin and email where only one date (maximum) is shown when “Display Exact Date” is turned on.

    A single date is used to pass to Google reviews which was the only date stored when “Display Exact Date” is turned on. But now, dates ranges are also stored for redisplay in admin and email instead of discarded after checkout.

    Plugin Author RLDD

    (@rermis)

    Hi @alexliii,

    Thank you for reporting this error. I will fix the line item error referencing Ship Estimate for WooCommerce on the next release. Note that the root issue is from within PayPal and it is creating a domino effect, so you may want to report this to the PayPal developer to ensure the root problem is resolved.

    Plugin Author RLDD

    (@rermis)

    Hi @sorinv,

    Thank you for this great suggestion. I will add this to a list of potential features. There is some difficulty implementing because the date estimates shown at checkout consider all products in the cart, so an estimate of just one product may not accurately reflect the estimate for all products in the cart at checkout. Also, not all shipping methods may be available, and this information is not known until the customer provides a shipping address.

    Plugin Author RLDD

    (@rermis)

    Hi @titsmaker,

    Thank you for these recommendations. It’s rare to get such detailed feedback, so I consider this valuable. I can assure you that the plugin is headed in the direction to address some of these features.

    The plugin has been an active project for almost 2 years and it’s taken a lot of work to this point. I am the only developer on this project, so most features are slow to release. That said, I’ll try to prioritize some of these based on yours and others feedback and try to work on the most useful (by popularity).

    Thank you!

    Thread Starter RLDD

    (@rermis)

    Hi @nauriskolats,

    Thanks for looking into this. You are correct, the bots crawl the site and create carts as part of the Google Shopping program. The one consistent factor for all the carts email domain is @fakemail.com.

    It would be nice to be able to skip recovery emails, and possibly even exclude the bot’s carts from the abandoned cart list. I think the easiest route could introduce a field in plugin settings where certain email domains can be excluded from recovery. That would be equally effective while leaving accuracy and adjustment up to the admin.

    If you want to cut directly to the root issue, you could exclude from the recovery process based on IP host if google is returned from the function gethostbyaddr(). However this leaves little control up to the admin and is probably not the best solution for a widely distributed plugin.

    Plugin Author RLDD

    (@rermis)

    Hi @alexliii,

    Thank you for confirming the fix. I appreciate the recommendation regarding rules for categories.

    At this time rules are only supported by method or product (parent product or product variation). I will add categories to the development list but I do not have a timeframe yet. Thank you!

    Plugin Author RLDD

    (@rermis)

    Hello, I have released a fix within version 2.2.3 or greater that should resolve this issue. Alternately, you may also update to WP version 6.1.1 or greater which should also resolve it.

    Plugin Author RLDD

    (@rermis)

    Hello, I have released a fix within version 1.4.6 or greater that should resolve this issue. Alternately, you may also update to WP version 6.1.1 or greater which should also resolve it.

    Plugin Author RLDD

    (@rermis)

    Ok, I’m unable to replicate, but I think this is related to WP versions. I will release a fix in the next 5 minutes with a conditional. Can you let me know if this resolves the issue?

Viewing 15 replies - 196 through 210 (of 479 total)