package details-> refresh = error

Report & discuss bugs found in 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
leecher3k
Newbie
Newbie
Posts: 5
Joined: January 5th, 2012, 11:34 am

package details-> refresh = error

Post by leecher3k »

hi there.

if you click on your download content to see the details (which rar part is downloaded atm etc) and stay there till your download is finished and then click refresh you will get this message:

Code: Select all

500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last):
  File "cherrypy\_cprequest.pyo", line 618, in respond
  File "cherrypy\_cpdispatch.pyo", line 25, in __call__
  File "sabnzbd\interface.pyo", line 489, in default
  File "_Program_Files__x86__SABnzbd_interfaces_Plush_templates_nzo_tmpl.py", line 105, in respond
NotFound: cannot find 'filename' while searching for 'slot.filename'

Powered by CherryPy 3.2.0
Version: (Ex: 0.6.14)
OS: (Ex: Win 7 64 bit professional )
Install-type: (Ex: Windows Installer )
Skin (if applicable): (Ex: Plush)
Firewall Software: (Ex: Win 7 Firewall)
Are you using IPV6? (no)
Is the issue reproducible? (yes)
Top
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: package details-> refresh = error

Post by shypike »

Known problem.
Hard to solve due to the fact that we have a web-ui.
Given that there's no real damage, we decided to let it be.
Top
Post Reply

Return to “Bug Reports”