[namyar]

Originally Posted by namyar

Works like a charm, thank you very much!

It seems that due to this script, links aren't always automatically transfered to the downloads tab but have to be added manually. Link crawler is set to transfer and start downloads by default, yet it fails to do so on occasion.

[sancrage]

Hello,

Sorry to bother you, but wonder if there is a way to rename the filename to be the same as the directory when I provide the save path?

Thanks.

[mgpai]

Originally Posted by sancrage

... wonder if there is a way to rename the filename to be the same as the directory when I provide the save path?

Currently it is only possible to dynamically update/sync filename and/or downloadpath with the packagename. There is no variable or placeholder to access the save path. You will have to set the save path first and then use a script to rename the file based on it.

If however there is common logic/pattern in genrating the save path, for e.g. based on file name, download url, source url, etc., you can use packagizer rule or script to set them both at the same time.

If you provide some working examples I can look into it.

[mgpai]

Originally Posted by namyar

It seems that due to this script, links aren't always automatically transfered to the downloads tab but have to be added manually. Link crawler is set to transfer and start downloads by default, yet it fails to do so on occasion.

The script is executed even before packagizer rules are applied, so it is very unlikely that it is caused by it. In other words, the problem cannot be resolved by modifying the script.

Please wait for feedback from @Jiaz. In the meanwhile, you can try increasing the following advanced setting:

LinkgrabberSettings.autoconfirmdelay

[A-Dude]

Hi there,

id like a modification of this script

https://board.jdownloader.org/showpo...&postcount=881

The script restart JD just when JD is in idle, but my JD is never in idle

Is it possible that when a new update is availible, JD doesn´t start new downloads but finish current running downloads and then do the restart?

[Jiaz]

Originally Posted by A-Dude

Is it possible that when a new update is availible, JD doesn´t start new downloads but finish current running downloads and then do the restart?

@mgpai: set stopmark on running download, then downloads will finish and then idle and then restart, that should work, via api
downloadsV2/setStopMark(long linkId, long packageId)

[mgpai]

Originally Posted by Jiaz

@mgpai: set stopmark on running download, then downloads will finish and then idle and then restart, that should work, via api downloadsV2/setStopMark(long linkId, long packageId)

New downloads can still start till the link/package with stop mark is finished.

[Jiaz]

Originally Posted by mgpai

New downloads can still start till the link/package with stop mark is finished.

set stopmark on disabled link and no further downloads will start, else further downloads will stop once the stopmark link is finished/failed or at least tried once

[mgpai]

Originally Posted by Jiaz

set stopmark on disabled link and no further downloads will start, else further downloads will stop once the stopmark link is finished/failed or at least tried once

Still a bit complicated since the trigger is interval. The stopmark will be set on each run. Also disabling a link just to set the stopmark is not an elegant solution. Will think of something.

[mgpai]

Originally Posted by A-Dude

Is it possible that when a new update is availible, JD doesn´t start new downloads but finish current running downloads and then do the restart?

/*
    if update is avaialble, finish running downloads and restart and update when JD is Idle
    Trigger Required: Interval
    Set Interval to 600000 or more
*/

var updateAvailable = callAPI("update", "isUpdateAvailable");

if (
    updateAvailable &&
    isDownloadControllerRunning() &&
    !getProperty("skipped", false)
) {
    getAllDownloadLinks().forEach(function(link) {
        if (!link.running && !link.finished) {
            link.skipped = true;
        }
    });

    setProperty("skipped", true, false);
}

if (
    updateAvailable &&
    !callAPI("linkcrawler", "isCrawling") &&
    !callAPI("linkgrabberv2", "isCollecting") &&
    !callAPI("extraction", "getQueue").length &&
    isDownloadControllerIdle()
) {
    callAPI("update", "restartAndUpdate");
}

/*
    if update is avaialble, finish running downloads and restart and update when JD is Idle
    Trigger Required: Interval
    Set Interval to 600000 or more
*/

var updateAvailable = callAPI("update", "isUpdateAvailable");

if (
    updateAvailable &&
    isDownloadControllerRunning() &&
    callAPI("downloadsV2", "getStopMark") == -1
) {
    callAPI("downloadsV2", "setStopMark", 0, 0);
}

if (
    updateAvailable &&
    !callAPI("linkcrawler", "isCrawling") &&
    !callAPI("linkgrabberv2", "isCollecting") &&
    !callAPI("extraction", "getQueue").length &&
    isDownloadControllerIdle()
) {
    callAPI("update", "restartAndUpdate");
}

[mgpai]

Originally Posted by Jiaz

@mgpai: set stopmark on running download, then downloads will finish and then idle and then restart, that should work, via api downloadsV2/setStopMark(long linkId, long packageId)

This is more suitable, but difficult to control precisely, since it is toggle:

/toolbar/toggleStopAfterCurrentDownload

[Jiaz]

@mgai: just set stopmark on any running download. I don't think that it's that impotant and the script will work fine again
I can also add new method to specifically set stopmark to stop new downloads instant, if you prefer that

[mgpai]

Originally Posted by Jiaz

@mgai: just set stopmark on any running download. I don't think that it's that impotant and the script will work fine again

The default behavior stopmark of is perfectly fine and as it should be. It might not be suitable in cases like this, especially if there are many downloads above the link/package on which the stopmark is set. If for e.g. connection is lost JD will try/skip several downloads and end up starting a new download way down the list, the stopmark could be set anywhere. It will not be an issue when the user sets the stopmark manually, since it is set specifically on a chosen link/package.

I can also add new method to specifically set stopmark to stop new downloads instant, if you prefer that

This might be a one off case, and the current solution should work just fine.

[Jiaz]

@mgpai:I can add new set stopmark method that also supports the *don'T start any new downloads* handling.

after next core update new logic for setStopMark
linkID and packageID = -1 = NONE, same as removeStopMark
linkID and packageID = 0 = HIDDEN, special mode to instant stop new downloads and just finish running ones

[mgpai]

Originally Posted by Jiaz

after next core update new logic for setStopMark

Nice. Thanks Jiaz.

[Jiaz]

Originally Posted by mgpai

Nice. Thanks Jiaz.

will be available in 5 mins

[mgpai]

Originally Posted by Jiaz

will be available in 5 mins

Updated the script with new method. Working fine. Thanks Jiaz.

[Jiaz]

@mgpai: Thanks for the feedback

[A-Dude]

Big thanks to mgpai and Jiaz!
I added the script (the first one for my JD ) and note the startup time.

Im realy happy now, my JD will be up to date and i don´t have to manually set stopmarks and trigger the restart

[Jiaz]

@A-Dude: All thanks goes to mgpai