night / betterttv

BetterTTV enhances Twitch with new features, emotes, and more.
https://betterttv.com
Other
1.21k stars 267 forks source link

Can't remove recommended or similar channels in sidebar. Sidebar Error? #6773

Closed mothehalf closed 7 months ago

mothehalf commented 7 months ago

Describe the bug

Using Firefox (up to date). I've recently switched from Chrome to Firefox and installed BTTV to watch my favorite streamers with my favorite emotes! But unfortunately since I've switched to Firefox, BTTV doesn't turn off Recommended or Similar channels in the sidebar. I just checked Chrome and it doesn't show any of my subscribed channels on the left bar at all now! But for now I'm more concerned that it's not working on Firefox. I'd love to stop seeing channels I'm not interested in, and I'm not sure how to solve this.

Steps to reproduce

Install Firefox, install BTTV, attempt to turn off recommended and similar channels.

Expected behavior

Recommended and Similar channels will stay, despite what you do.

Screenshots

Screenshot 2024-04-27 212640

Device information

Device: PC Desktop // OS: Windows 11, Version 23H2 // Browser: Firefox (latest update/up to date). Other extensions: Adblock, Adblock plus, privacy badger, ttv lol pro (installed after this problem began to occur), ublock origin). Turning them on/off hasn't changed anything.

Additional information

Doesn't seem to be a problem on every device/firefox/chrome monitor. Does feel like ever since Twitch has really brought out the adblocker guns that it's even messing with BTTV? Unsure.

dclstn commented 7 months ago

I cannot reproduce this, is there any errors in the console and what version of betterttv are you using?

night commented 7 months ago

Please upgrade to version 7.5.20 and see if problems persist.

mothehalf commented 7 months ago

The update works!!! Oh thank you so much! Sorry to dclstn, I was busy at work and forgot to reply. :) Thank you guys very much!!!

github-actions[bot] commented 4 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related issues or feature requests.