#1
|
||||
|
||||
Question: How to downgrade to a previous date
I'm currently experiencing quite a few new (!) problems with core version #46197. So, I'd like to downgrade for verifying whether or not these problems have something to do with one of the latest updates.
Question 1: Which is the easiest way to restore to a previous release, which - in my eyes would also have to include any plugins to the same date? Anyway, from now on I will use 'Live File Backup' from 'Infonautics' to backup any version-related files, which I already do for some other apps I'm running. Note: For such cases, this is better than Windows' 'Backup and Restore'. Question 2: Can somebody please tell me which files are or can be subject to change, during an update. I would need that list for 'Live File Backup'. Question 3: And how do I keep JD from updating again? Will try to answer this one myself: In Code:
.\JDownloader2\cfg\updateclient\setup.json Code:
"autoupdatecheckenabled" : true Last edited by StefanM; 12.06.2022 at 10:54. |
#2
|
||||
|
||||
@StefanM: I'm sorry but there is no downgrade support. When there are issues, report them and we will check/fix them. What *new* issues do you encounter? I regularly check forum and fixed the one reported issue (filer.net). Please report them so we can check/fix them
__________________
JD-Dev & Server-Admin |
#3
|
||||
|
||||
If you really need this, then create a full backup of the JDownloader folder. Changes may be plugins only, but also may contain core changes/fixes and even changes to other files (eg new configuration, or changed storage format...)
__________________
JD-Dev & Server-Admin |
#4
|
||||
|
||||
Quote:
We do NOT guarantee any downgrade support/stability as formats/interfaces/methods are ALWAYS subject to change
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 12.06.2022 at 10:55. |
#5
|
||||
|
||||
We don't recommend this at all because this just leads to more support. Ppl will complain about issues just to find out that they have been addressed/fixed already.
But you may do so by disabling Settings->Advanced Settings->UpdateSettings.autoupdatecheckenabled
__________________
JD-Dev & Server-Admin |
#6
|
||||
|
||||
Quote:
That's why I asked which files I would need to backup. Or - the other way round - which files I do not need to backup. Maybe you can answer this, if it is not too much efforts. Otherwise I will try to find out myself... Last edited by StefanM; 12.06.2022 at 12:05. |
#7
|
||||
|
||||
Quote:
I do already have weekly complete backups, and the latest backup does not show that problem. However, I updated to Core #46208 as next step, and now not all files/links show the above problem, which I will observe... Question: Since there is (still ) no changelog, and probably will never be again ... ... is there a way to figure out - e.g somewhere in the logs - when which update (core, plugins,... - has been performed? Haven't looked for that, yet. |
#8
|
||||
|
||||
Quote:
Just for testing! But in the meantime I found quite a few useful settings, like 'being asked to allow an update'. If this also applies to plugin updates etc. this setting would be very useful. Question: Is that so? If yes, I would use that as my standard setting, so I can see and tell, which update (and when) might have caused a problem, such as the one I described here. |
#9
|
||||
|
||||
And please forgive me for this one:
as the answer will probably be 'of course'. Question: Is there a mechanism, which makes sure that - in case of e.g. a plugin update, which can be performed with out restarting JD - this update will be held back until restart, in case it only works correctly together with a core update? |
#10
|
|||
|
|||
Quote:
Code:
Jdownloader\logs\updatehistory |
#11
|
||||
|
||||
Yeah, obvious!
Thanks for the reply! |
#12
|
||||
|
||||
Quote:
2.) no need to backup log files as they are log files, write only. 2.) As already explained, every file may be subject to be changed by update. may just be plugin chances, but also cause changes in configuration (eg new configuration settings) or stored lists (eg format changes).
__________________
JD-Dev & Server-Admin |
#13
|
||||
|
||||
I'm not aware of any problems here and no reports. Please provide logs. Please open separate thread for this.
__________________
JD-Dev & Server-Admin |
#14
|
||||
|
||||
Quote:
Update: just noticed mpgai was faster see https://board.jdownloader.org/showpo...9&postcount=10
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 12.06.2022 at 12:49. |
#15
|
||||
|
||||
Yes, this applies to all updates.
__________________
JD-Dev & Server-Admin |
#16
|
||||
|
||||
plugin updates that are not compatible with current core are not released in first place and thus blocked by core update updates are installed/applied in background (without restart) only if they do contain ONLY plugin changes. as soon as a non plugin file is part of the update, it's treated as core update
__________________
JD-Dev & Server-Admin |
#17
|
|||
|
|||
Were any new/test scripts active at that time? Scripts with sync. execution can block downloads.
|
#18
|
||||
|
||||
you can also sort the plugins directory by modified date.
__________________
raztoki @ jDownloader reporter/developer http://svn.jdownloader.org/users/170 Don't fight the system, use it to your advantage. :] |
#19
|
||||
|
||||
Quote:
I quoted just a few examples, why your suggestion of making a backup of cfg folder is much too much. I listed items that should not be backupped, when I just want to backup files which may be modified by updates. My objective was to learn about all those files, that I would not need to backup for the intended purpose... I know, I'm writing too much theses days, which might keep one or the other reader from reading my posts thoroughly enough |
#20
|
||||
|
||||
Quote:
And that script was the update notifier. But it is true, the problem showed up, after I had installed that script in that particular installation. |
#21
|
||||
|
||||
right!
|
#22
|
||||
|
||||
I'm sorry but I did not read it in that way but I understand how you mean it.
__________________
JD-Dev & Server-Admin |
#23
|
||||
|
||||
@StefanM: In case you still have the problem or can reproduce it, then restart JDownloader. wait for the issue to show up, then create a log and post logID (create new thread for this). the log will then show any blocking happening or why it stalls in that state.
__________________
JD-Dev & Server-Admin |
#24
|
|||
|
|||
@StefanM: You can use a script (similar to the update notifier) to track and automatically open unread logs.
|
#25
|
||||
|
||||
Quote:
Usually I would not read any logs at all. What are you referring to? Can you please explain? Because I assume, that your idea would be helpful, even though, so far I did not understand it |
#26
|
||||
|
||||
@StefanM: I guess he does mean to combine/accumulate those *update logs* that are new, show them and then mark them as being read.
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|