Forum Replies Created

Viewing 15 replies - 166 through 180 (of 479 total)
  • Plugin Author RLDD

    (@rermis)

    Hi @acehobojoe,

    Thank you for your report. Can you click “Auto Coupons Status” in the top black admin bar on the cart page. This will give you a readout of the status of each coupon. Please let me know what it says.

    Plugin Author RLDD

    (@rermis)

    What you might be seeing occurs when a previously auto-applied coupon is manually removed, the system won’t try to auto-apply it again unless another coupon was applied and removed. This prevents auto-apply getting stuck in a cycle where a coupon cannot be removed manually.

    I appreciate your gratitude, and I would value most an honest review of your experience if you have the opportunity.

    Plugin Author RLDD

    (@rermis)

    Hi @pickleface, thank you for the example. I was able to determine it was not working because it was originally designed to substitute only the English word ‘coupon’.

    See version 2.2.16 released now. The new version should substitute line item names in any language. I’m not 100% sure it will work since I cannot test directly, so please let me know if it still does not work on your theme.

    Plugin Author RLDD

    (@rermis)

    Hi @pickleface,

    I am happy to take a look at this issue. Can you point me to an example flatsome theme cart page and provide me with a test coupon? That should be all I need to reproduce and create a fix.

    Thank you!

    Plugin Author RLDD

    (@rermis)

    Hi Thomas,

    Thank you for following up. The coupon parameter will work when the ‘Apply via URL’ setting is checked under the coupon settings. Let me know if this setting is on for the coupon and the URL is still not applying the coupon. The only scenario where it may not apply is if the coupon was manually removed from the cart previously… in this case, apply another coupon then remove it. This resets the coupon cache.

    Plugin Author RLDD

    (@rermis)

    Hi Thomas,

    Version 2.2.15 has been released. It now includes output buffering so that all notifications are returned in the content area. This should safely resolve your exact issue without changing when the function is triggered.

    Please let me know if any reason this doesn’t fix the root issue.

    Plugin Author RLDD

    (@rermis)

    Hi @tlartaud,

    Thank you for identifying this issue. I appreciate you letting me know about the impact of the wp_loaded hook. In your opinion, would the following fix work?

    if(isset($_GET['coupon'])) {
      add_action('init','wac_cache_coupon');
      add_action('template_redirect','wac_apply_coupons');
    }
    else {
      add_action('woocommerce_add_to_cart','wac_apply_coupons'); // Product
      add_action('woocommerce_before_checkout_form','wac_apply_coupons'); // Checkout
      add_action('woocommerce_before_cart','wac_apply_coupons'); // Cart
    }

    Plugin Author RLDD

    (@rermis)

    Thank you @geoffreyarce, I’ll go ahead and close this for housekeeping.

    Plugin Author RLDD

    (@rermis)

    You’re almost there. It looks like the theme is still adding some padding or margins around the container or entry-content blocks. You can experiment with a solution by adding styles below the shortcode. Here is a starting point that I hope will help…

    [dynamicTime]
    <style>
    #container,#container #main,#container #main .article,#container #main .article .entry-content{margin:0!important;padding:0!important;}
    </style>
    Plugin Author RLDD

    (@rermis)

    Hi @bigmoxy,

    If you are using the shortcode [dynamicTime] on a page, you may, you may remove the Google Translate module by copying & pasting this style below the shortcode in an html block.

    <style>#glang{display:none}</style>
    Plugin Author RLDD

    (@rermis)

    Hi @bigmoxy,

    Yes, it is possible in the current version. In the settings see the 5th option from the top, and select “Weekly Pay Period”. The 7 days will be laid out in a single row, but may appear on multiple rows depending on the screen width in which they are viewed. On a mobile device, the days will stack vertically.

    Plugin Author RLDD

    (@rermis)

    Hi @bigmoxy,

    Thank you for your question. Most browsers will save the settings once all fields are selected/completed. If for any reason the form does not save, just press enter in any text field (like the currency field).

    Please let me know if you continue to experience an issue.

    Plugin Author RLDD

    (@rermis)

    Hi @bounomid,

    Thank you for reporting this issue. I have not been able to replicate your issue by using the plugin in another language. The plugin is designed to trigger on the cart page in any language (or any URL with the cart), not just ‘/cart’ in English.

    Here are some things to check:

    • Try duplicating the coupon in the language you are using.
    • Ensure your coupon limits, restrictions, and auto apply options are correctly set.
    • Use /?troubleshoot on the cart page to trigger troubleshoot mode (as an admin)
    • If you have forcibly removed a coupon from the cart, it will not automatically attempt to re-apply it. You must apply another coupon, and remove it in order to refresh the cache. The Auto Coupons plugin will then attempt to auto-apply the original coupon again.
    • This reply was modified 2 years, 10 months ago by RLDD. Reason: Unable to replicate
    Plugin Author RLDD

    (@rermis)

    Hi @alexliii,

    Thank you for this report. I’m unable to reproduce the error specifically in any test cases, but I can add some checks on the line where the error occurs to ensure this error is not triggered. The error occurs when the $email is not an object, so I will add a check to make sure it’s an object before using get_id(). This fix will be released in the next few hours.

    Plugin Author RLDD

    (@rermis)

    Hi June,

    Thank you for this feedback and giving me the opportunity to improve this plugin. If you have a moment can you tell me which browser you are using that didn’t render the plugins page correctly? I have not yet been able to reproduce the issue as you have described, but I will try to resolve this before the next release.

Viewing 15 replies - 166 through 180 (of 479 total)