Support Forum

We were both right though.

Hi and welcome to the forum.

I don't think this NAS supports installation of user applications, it's an entry-level NAS only.

https://www.cnet.com/reviews/wd-my-cloud-2-tb-review/

edit: oops, too-late.

I even post those release notes on the QNAP forum. I should probably read them a little closer though.

Ah, I now realise this selection box was moved from the front SABnzbd page, into Config -> Switches -> Queue -> On queue finish script.

So, not a bug, just a change.

Might be this? https://github.com/sabnzbd/sabnzbd/comm ... b7f5a7f00a

It looks like 'interfaces/Glitter/templates/include_menu.tmpl' had some changes related to end-of-queue operations.

update:

• works in 4.2.0Alpha1
• works in 4.2.0Alpha2
• not working in 4.2.0Alpha3
• not working in 4.2.0Beta1

If filesystem.py hasn't changed, maybe it’s the interface?

Just did a test: went back to SABnzbd 4.1.0 (running from source), and it correctly lists my scripts in the same environment 4.2.1 doesn't.

I'll continue checking the later releases and see if I can find out where it stopped working.

#Metoo!

Ah, no worries.

And did you click the ".." to jump back to the parent directory?

Have you tried entering the full path manually?

Hi and welcome to the forum.

Are you using forward-slashes or backslashes when creating your path?

Your post shows backslashes (used only in DOS, Windows environments).

Linux paths use forward-slashes.

No worries, thanks @safihre.

Hi guys. :) Using SABnzbd 4.2.1 on Debian 12.4 and it's all working very well. Nice job. I noticed a short time ago, there's now an additional processing counter shown (with a cyan background), along with what appears to be the original history counter. However, the display of these totals is a litt...

Yes, you could also watch that folder as SABnzbd is running and see if anything is written to it.

Try this one too (please correct the path if it’s wrong):

And where is your home folder located? It appears your /dev/shm (a temporary path used by the OS and created in RAM) is the same size as reported by SABnzbd. I suspect your temporary folder is actually on that RAMdisk.