NZBs with embedded passwords + "AutoPAR/UnRAR"
Posted: Fri May 06, 2016 10:25 am
Hello,
I've recently updated from a pretty much out-dated to the latest (6.70, B4600) version of NBP and instantly run into the issue, that a manual call of the "AutoPAR/UnRAR" function with an entry (generated from a nzb with an embedded password in the filename) in the "Downloading Files" window no longer produces the intended result (for me).
Before, "AutoPAR/UnRAR" directly extracted the passworded RARs, using the password that was added to the password list of the "Password Manager" while parsing the NZB file, for example, filename{{password}}.nzb.
Now "AutoPAR/UnRAR" just opens the "Password Manager" window and I'm expected add the related password.
Ironically the necessary password already exists in the list, that means, the parsing of the NZB file itself appears to be working.
It is in my case, as if "AutoPAR/UnRAR" doesn't take a look into the password list in order to use the associated password.
Maybe someone has a clue?
I've recently updated from a pretty much out-dated to the latest (6.70, B4600) version of NBP and instantly run into the issue, that a manual call of the "AutoPAR/UnRAR" function with an entry (generated from a nzb with an embedded password in the filename) in the "Downloading Files" window no longer produces the intended result (for me).
Before, "AutoPAR/UnRAR" directly extracted the passworded RARs, using the password that was added to the password list of the "Password Manager" while parsing the NZB file, for example, filename{{password}}.nzb.
Now "AutoPAR/UnRAR" just opens the "Password Manager" window and I'm expected add the related password.
Ironically the necessary password already exists in the list, that means, the parsing of the NZB file itself appears to be working.
It is in my case, as if "AutoPAR/UnRAR" doesn't take a look into the password list in order to use the associated password.
Maybe someone has a clue?