- NZBGET RETURNED LOG WAS NOT FULL
- NZBGET RETURNED LOG WAS NOT CODE
- NZBGET RETURNED LOG WAS NOT PASSWORD
- NZBGET RETURNED LOG WAS NOT DOWNLOAD
NOTE: Only post-processing scripts can have post-processing parameters. # POST-PROCESSING PARAMETERS # Video resolution (default, 480p, 720p, 1080p).
NZBGET RETURNED LOG WAS NOT PASSWORD
4 = wrong password (only for rar5 archives).
3 = write error (usually not enough disk space). 0 = unpack is disabled or was skipped due to nzb-file properties or due to errors during par-check. NZBPP_UNPACKSTATUS - v13.0 Result of unpack:. Deprecated, use NZBPP_STATUS and NZBPP_TOTALSTATUS instead. 4 = par-check needed but skipped (option ParCheck=manual). 3 = checked and can be repaired but repair is disabled. 0 = not checked: par-check is disabled or nzb-file does not contain any par-files. NZBPP_PARSTATUS - v13.0 Result of par-check:. FAILURE - at least one of the script has failed. NZBGET RETURNED LOG WAS NOT CODE
SUCCESS - all other scripts have ended with exit code “SUCCESS”.NONE - no other scripts were executed yet or all of them have ended with exit code “NONE”.NZBPP_SCRIPTSTATUS - v13.0 Summary status of the scripts executed before the current one:.The scripts interested in that info still can use parameter NZBPP_SCRIPTSTATUS.
NZBGET RETURNED LOG WAS NOT DOWNLOAD
Because most scripts don’t depend on other scripts they shouldn’t assume the download has failed if any of the previous scripts (such as a notification script) has failed. For example for a successful download the status would be SUCCESS/ALL instead. Even if one of the scripts executed before the current one has failed the status will not be set to WARNING/SCRIPT as method history will do. NOTE: one difference to the status returned by method history is that NZBPP_STATUS assumes all scripts are ended successfully.For the complete list see description of API-Method “history”.NZBPP_STATUS - Complete status info for nzb-file: it consists of total status and status detail separated with slash.
DELETED - download was deleted post-processing scripts are usually not called in this case however it’s possible to force calling scripts with command “post-process again”. FAILURE - download has failed or a serious error occurred during post-processing (unpack, par). WARNING - download is damaged but probably can be repaired user intervention is required. NZBPP_TOTALSTATUS - v13.0 Total status of nzb-file:. NZBPP_CATEGORY - Category assigned to nzb-file (can be empty string). If the file was added via RPC-API (method append), this can be any string but the use of actual file name is recommended for developers. If the file was added from web-interface, it’s only the file name with extension. NZBGET RETURNED LOG WAS NOT FULL
If the file was added from incoming nzb-directory, this is a full file name, including path and extension.
NZBPP_NZBFILENAME - Name of processed nzb-file. If download was renamed, this parameter reflects the new name. NZBPP_NZBNAME - User-friendly name of processed nzb-file as it is displayed by the program. NZBPP_FINALDIR - Final directory, if set by one of previous scripts (see below). NZBPP_DIRECTORY - Path to destination dir for downloaded files. The information about nzb-file which is currently processed: In addition the information about the file currently processed is passed as well: Nzb-file information vars with prefix NZBOP_) and Script configuration options (env. Like other extension scripts the scan scripts get NZBGet configuration options (env. This document describes the unique features of post-processing scripts. Please read Extension scripts for general information about extension scripts first! Post-processing scripts are a kind of Extension scripts. That is a global setting affecting all categories and also defining the order scripts are listed in the download details dialog. The order is controlled by the option ScriptOrder. If you use more than one script for one nzb-file it can be important to set the correct order of execution. To do so click on the nzb-file in the list of downloads, then click on Postprocess. However it’s possible to alter the assigned pp-scripts for each nzb-file individually. When you change option Extensions ( PostScript) this has no effect on already enqueued downloads. Please note that these settings define “defaults” for nzb-file. You can also define a different set of pp-scripts for each category. You can define what scripts should be called for the nzb-file using option Extensions ( PostScript in older NZBGet versions) in section EXTENSION SCRIPTS. When a new nzb-file is added to queue it doesn’t have any pp-scripts assigned to it by default. You can activate par-check/repair and unpack without using of any post-processing scripts. Please note that the par-check/repair and unpack are performed by NZBGet internally and are not part of post-processing scripts. The scripts can perform further processing of downloaded files such es delete unwanted files (*.url, etc.), send an e-mail notification, transfer the files to other application and do any other things. 
After the download of nzb-file is completed NZBGet can call post-processing scripts (pp-scripts).
0 kommentar(er)
