JDownloader Community - Appwork GmbH
 

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #10  
Old 05.09.2022, 00:58
JDmurphy JDmurphy is offline
Fibre Channel User
 
Join Date: Mar 2012
Posts: 120
Default

Quote:
Originally Posted by Jiaz View Post
I just want to make clear that we don't force them.
I just wanted to make clear that I didn't mean "forced" as in "required before the user is allowed to continue" (the definition you were referring to that was apparently understood) but as in "auto-installed in the background without any notification" (the phrasing from the knowledgebase article you linked which I had already found earlier before referencing it in my OP).

Quote:
Originally Posted by Jiaz View Post
the plugin system is able to load/exchange plugins without a java restart being required
This should be the meaning of
Quote:
Originally Posted by JDmurphy View Post
"pushed without user interaction/notification"
if I'm not mistaken. The ability to customize the update settings is very interesting! I take no issue whatsoever with the default behavior though, the only reason for mentioning this was to convey right away that I'm aware plugin fixes can be applied in the background so that JDownloader can directly make use of them while core updates do require a restart.

Quote:
Originally Posted by JDmurphy View Post
do I have to read it as: "Due to changes in the player.js library the JD youtube plugin wasn't working properly, and a core function had to be fixed to make the plugin work again while fixing the plugin itself wasn't required."
Quote:
Originally Posted by Jiaz View Post
The bugfix was outside of the plugin, within another part of JDownloader. But without this fix, the plugin was/is broken in meaning of not working as wished.
Is there any difference between the two that I might not be aware of which needed clarification?