search

proginosko / LeechBlockNG-chrome

LeechBlock NG (Next Generation) for Chrome is a simple productivity tool designed to block those time-wasting sites that can suck the life out of your working day. All you need to do is specify which sites to block and when to block them.
https://www.proginosko.com/leechblock/
Mozilla Public License 2.0
72 stars 14 forks source link

Countdown timer display with multiple rules #36

Open wpzdm opened 3 years ago

wpzdm commented 3 years ago

Settings: timer_not_shown.txt

In certain time intervals, "douban.com" matches multiple rules, but the timer is not shown.

wpzdm commented 3 years ago

Ref https://www.tapatalk.com/groups/leechblock/countdown-timer-display-with-multiple-rules-t474.html

proginosko commented 3 years ago

Based on a quick look at your settings, the timer is not shown because the time left (calculated as the shortest amount based on all the block sets that apply to that site) is based on one of the block sets (4, 5, and 6) where the option "Show countdown timer for this block set" (under Advanced Settings) is not checked. Try checking that option for all block sets and see if it resolves the issue.

proginosko commented 3 years ago

By the way, I think you can simplify some of your block sets by using the double-wildcard (**) which can include forward-slashes.

https://www.proginosko.com/leechblock/faq/wildcards/

wpzdm commented 3 years ago

Ah..this should be the reason, I totally do not remember why I unchecked it in the sets. Now checked, I will close this if it does not happen anymore.

nik312123 commented 1 year ago

I think it should be safe to close this issue at this point. @wpzdm ?

Le-G commented 7 months ago

I have the same issue. Two blocksets, with enforcing times not overlapping (but same days and websites). When a site is present in two blocksets, the countdown does not show (and doesn't close the windows when it reaches 0). Show countdown is enabled on both sets. Running Firefox on MacOS.

nik312123 commented 7 months ago

@Le-G I'd recommend creating a new issue as the issue of @wpzdm was resolved. Also, consider exporting and including the relevant rulesets and settings in your post.