Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Group association lost when deactivating a group #2291

Closed
mbierman opened this issue Aug 10, 2022 · 1 comment
Closed

Group association lost when deactivating a group #2291

mbierman opened this issue Aug 10, 2022 · 1 comment

Comments

@mbierman
Copy link

Versions

  • Pi-hole: v5.11.4
  • AdminLTE: Latest: v5.13
  • FTL: v5.16.1

Platform

  • OS and version: Linux pihole 5.4.0-1066-raspi Ubuntu SMP
  • Platform: Raspberry Pi,

Expected behavior

Group should remain in place when deactivated and reactivated.

  1. Create Blacklist domain. e.g. (\.|^)foo\.bar$
  2. Go to Group Management > Domains see it is assigned to Default Group.
  3. Assign to another group and remove Default.
  4. Go back to Domains and disable the rule.
  5. Reenable the same rule.
  6. Go to Group Management > Domains see it is assigned to the same group(s) originally selected in step 3.

Actual behavior / bug

The rule will be assigned to no group (and presumably) be ineffective.

Steps to reproduce

  1. Create Blacklist domain. e.g. (\.|^)foo\.bar$
  2. Go to Group Management > Domains see it is assigned to Default Group.
  3. Assign to another group and remove Default.
  4. Go back to Domains and disable the rule.
  5. Reenable the same rule.
  6. Go to Group Management > Domains see it is assigned to no group.

Debug Token

By the way your instructions are poor. I think you mean:

pihole -d OR https://docs.pi-hole.net/core/pihole-command/#debugger

[✓] Your debug token is: https://tricorder.pi-hole.net/8Sba6LHP/

Screenshots

image

Additional context

Add any other context about the problem here.

@yubiuser yubiuser transferred this issue from pi-hole/pi-hole Aug 10, 2022
@yubiuser
Copy link
Member

I guess this step

Go back to Domains and disable the rule.

Involves going to Black/Whitelist and not Group Management > Domains?

Then this is a duplicate of #2260

@dschaper dschaper closed this as not planned Won't fix, can't repro, duplicate, stale Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants