#1
|
|||
|
|||
AutoUpdate while reconnect
Hi,
i'd like to suggest a feature: JD2 could do an automatic update, before reconnecting, because all DLs are stopped at this moment ... Regards su |
#2
|
||||
|
||||
Indeed that is a nice idea!
Ticket: GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#3
|
|||
|
|||
Thx for opening a ticket!
|
#4
|
|||
|
|||
Could be nice if we also had a function like "if a new update is available and no download running, then autoupdate/restart JDownloader"...
|
#5
|
||||
|
||||
Updates are already installed in background if possible. For example plugin updates no longer need a restart of JDownloader. Only Core updates do and they are downloaded/collected and installed on next close/start of JDownloader.
__________________
JD-Dev & Server-Admin |
#6
|
|||
|
|||
Can't we use scripts to do it?
Restart and update JD before reconnect (using "Before a Reconnect" as trigger): Code:
// Check if updates are availiable if (callAPI("update", "isUpdateAvailable")) { // Restart JD and update callAPI("update", "restartAndUpdate"); } Code:
// Check if updates are availaible when JD is idle if (callAPI("update", "isUpdateAvailable") && isDownloadControllerIdle()) { // Restart JD and Update callAPI("update", "restartAndUpdate") } |
#7
|
||||
|
||||
Nope, that wont work. An Update needs a restart of JDownloader and internet connection (to verify update). So after update JDownloader no longer knows to reconnect
After a reconnect it could work
__________________
JD-Dev & Server-Admin |
#8
|
|||
|
|||
Because a reconnect has not been performed (as the trigger is before a reconnect), internet connection will be available for JD to restart and update (I have tested this).
The conditions which triggered a reconnect before the restart, would still be present after the restart. So a reconnect should be triggered again (I could not verify this as I do not have conditions which could trigger a reconnect). Only this time, even if the script is triggered, because there are no updates, JD would not require a restart and hence reconnect will be performed without any interruption ... or am I wrong in thinking it is so? I hope someone who uses reconnect could test this and give the feedback. |
#9
|
||||
|
||||
Yes, did not thought about this
But then you should do it after Reconnect to avoid enter captcha just to get another reconnect
__________________
JD-Dev & Server-Admin |
#10
|
|||
|
|||
Hello,
it is a pity that this great idea is apparently not being taken into account any more. Indeed, a script could do the job (in my opinion). Pseudo language: Code:
if (reconnect) { if (update_available) { write_environment ("reconnect", "Yes") do_update() restart_jD() } } Code:
if check_environment ("reconnect") { do_reconnect() } Afterwards (without having done the reconnect so far) the update including restart could be performed. Upon restart, jDownloader then checks if a reconnect is pending. If yes, it does it before starting the downloads. Unfortunately, I am not that much familiar with jDownloader's script feature to determine if that is a reasonable approach. Thank you very much and kind regards, DAC324 |
#11
|
||||
|
||||
@DAC324: you can ask mgpai (in english) for help to make your script working.
__________________
JD-Dev & Server-Admin |
#12
|
||||
|
||||
In case we add official support for it, we first would do the reconnect and then restart JDownloader. The other way around we would have to store the information (reconnect required).
__________________
JD-Dev & Server-Admin |
#13
|
|||
|
|||
Quote:
Use the above script with "Before a Reconnect" trigger. Since the external IP would still remain the same after the restart, a "Reconnect" should be triggered automatically when the downloads starts again. |
Thread Tools | |
Display Modes | |
|
|