Interface broken in 0.7.11

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
smidley
Jr. Member
Jr. Member
Posts: 64
Joined: January 29th, 2010, 11:34 pm

Interface broken in 0.7.11

Post by smidley »

I updated my sab from version 0.7.10 to 0.7.11 tonight and now my top bar looks like this: http://i.imgur.com/r8EbleG.png

Not sure what is causing the issue, but i've tried restarting sab and also tried using different browsers to view it (chrome and IE). Is there a style bug?
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Interface broken in 0.7.11

Post by shypike »

It's not broken.
The Multi-ops bar is now shown by default, because few people were aware that it exists.
You can hide it through the dropdown menu at the top right of the queue (yellow down arrow).
smidley
Jr. Member
Jr. Member
Posts: 64
Joined: January 29th, 2010, 11:34 pm

Re: Interface broken in 0.7.11

Post by smidley »

Alright, thanks for clearing that up :) Maybe this should be in the changelog lol.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Interface broken in 0.7.11

Post by shypike »

smidley wrote:Maybe this should be in the changelog lol.
It should work for new users only.
However, the cookie that stores the setting is only created once you change the setting.
So the effect is that the bar now becomes visible for everyone who's never touched the setting.
Which isn't bad, but should indeed have been in the release note :)
Post Reply