RLDD
Forum Replies Created
-
Forum: Plugins
In reply to: [Auto Coupons for WooCommerce] WooCommerce DepositsHi Toad, Yes you are correct that the coupon is applied to the future payment and not the deposit. But the plugin WooCommerce Auto Coupons does not affect this, as the same situation would occur if the coupon were applied without WooCommerce Auto Coupons.
The coupon is a native WooCommerce coupon. WooCommerce Auto Coupons only controls when the coupon is applied. But WooCommerce Deposits controls how (and to what) it is applied, and how the line item totals appear.
I would open an issue with the plugin developers for WooCommerce Deposits regarding it’s handling of WooCommerce coupons.
Forum: Plugins
In reply to: [Auto Coupons for WooCommerce] WooCommerce DepositsHi Toad,
Yes, this plugin simply controls if a coupon in WooCommerce can be auto-applied, and applies it in checkout. There should be no conflicts between these plugins because they work in different parts of the checkout process.
It is outside the scope of support that I can offer because the WC Deposit plugin is controlling the subtotal, amount due, and total.
However, it is easy to remove the first discount line with a CSS rule <style>.cart-discount.coupon-COUPONNAME{display:none}</style> You could also use a CSS ::before rule to add content “Eco-friendly SAVINGS…” to the last line. Modifying the template is also an option if you expect this to be a less flexible, permanent feature.
Hi Toad,
Thanks for asking! I looked into this and from what I can discern, the coupon is being applied to the future payment, and not the amount due. It is likely related to a WC Deposits setting under Coupon Handling: https://docs.woocommerce.com/document/woocommerce-deposits/#section-13.
The Auto Coupons plugin affects the conditions under which a coupon is applied, but nothing further. Once a coupon is applied, it has done it’s job. It cannot control if a coupon is applied to a deposit or total in cart.
Forum: Plugins
In reply to: [Dynamic Time] Approving on Month 1 disabled time entry on Month 2Understood. If you are able to provide the diagnostics I will be happy to continue troubleshooting this issue for you.
Forum: Plugins
In reply to: [Dynamic Time] Approving on Month 1 disabled time entry on Month 2Hi Dan,
The reason I proposed resolution #3 is because this will usually correct any inconsistencies in the database for the time period at hand. It will not be an action that you would have to perform for every time period.
For more personalized troubleshooting, please follow the “Support & Diagnostics” menu item at the top right of your Dynamic Time Admin page.
Forum: Plugins
In reply to: [Dynamic Time] Approving on Month 1 disabled time entry on Month 2Hi Dan,
There are many explanations, but since I don’t have access to your system I’ll provide a short checklist.
1) Make sure you’re using a modern browser (Chrome, Firefox, Edge) not Internet Explorer
2) Ensure the same time period and weeks are identical between the time period the user submitted, and the time period that’s being approved.
3) If all fails, reverse all timestamps for the period, and resubmit.Let me know if there’s anything else I can do to help.
Forum: Plugins
In reply to: [Dynamic Time] TranslateHi loolzor,
@knutsp has graciously begun translation on Dynamic Time at https://nb.ww.wp.xz.cn/plugins/dynamic-time/. You can also make further contributions at https://translate.ww.wp.xz.cn/locale/nb/default/wp-plugins/dynamic-time/.
Thank you!
Forum: Plugins
In reply to: [Dynamic Time] Single days onlyHi Taz,
Hopefully this will get you started. Paste this below the shortcode, and it will affect the timecard generated by the shortcode.
This allows only Mondays, but it could be changed to Tuesdays very easily…
<style>.dyt_day{opacity:.5;pointer-events:none}</style> <script type='text/javascript'> function allow_Mon() { var dyt_days=document.getElementsByClassName('dyt_day'); for(var i = 0; i < dyt_days.length; i++) { if(dyt_days[i].innerHTML.includes('Mon')>0) { dyt_days[i].style.opacity='1'; dyt_days[i].style.pointerEvents='inherit'; }} } window.onload=function(){setTimeout(function(){allow_Mon()},1000);}; </script>Forum: Plugins
In reply to: [Dynamic Time] TranslateHi loolzor,
I’m very sorry to hear that the translation is missing. I have not translated before, but I see the status on this page… https://translate.ww.wp.xz.cn/locale/nb/default/wp-plugins/dynamic-time/ I recommend contacting the Norwegian team @bjornjohansen or @knutsp and ask them what might have happened.
Meanwhile, I will make certain that the rate field accepts five digits on the next release. Thank you for this recommendation!
Forum: Plugins
In reply to: [Dynamic Time] Single days onlyHi Taz,
Let me see if I can give you a place to start with some code you can expand on. I might need a few more days to complete.
Thanks for your patience!
Forum: Plugins
In reply to: [Dynamic Time] Single days onlyHi Taz, thank you for your suggestion. Currently this is not a supported feature. Due to the specificity of this request and likelihood that other would not widely use a feature like this, I doubt we would consider adding it to future versions.
However, if you have a developer it is possible to add some custom code gray out the days that should not be used, with some custom CSS or javascript on pageload. Let me know if you need assistance. I am always happy to provide some direction.
Forum: Plugins
In reply to: [Dynamic Time] Changes not reflecting into frontendHi subhamkotnala. I will look and see if this feature can be made optional in the next release. Thank you for this input!
Forum: Plugins
In reply to: [Dynamic Time] Changes not reflecting into frontendThe submit button will not display to users until the end of the pay period, this is to prevent users from accidentally submitting too early. This rule doesn’t apply to the admin view. If the timecard is viewed from the WP admin, it can be submitted at any time.
Forum: Plugins
In reply to: [Dynamic Time] Approve button issueHi subhamkotnala, yes I understand the issue. Without seeing it firsthand I must assume it is one of two things:
1) The time period is not the same between the two screens. Can you verify the time period begin and end dates are the same on both the admin view and user view? If the dates do not match, click on the dates at the top of the timecard to navigate forward or back in one week increments.
2) There must be a page reload/refresh on the admin side after a timecard is submitted. You can ensure this by reclicking the Dynamic Time WP menu item to reload the page.