#1
|
|||
|
|||
New Install Does Not Auto-Resume
Hello all!
My new/clean install of JD2 does not continue a DL when it finishes on, nor does it auto-reconnect when connection is lost :( I also noticed that when it is in this non-downloading state, the STOP button is *not* active (the GO button is greyed out). Any help correcting this issue would be greatly appreciated. |
#2
|
||||
|
||||
Screenshots, log and example links are missing.
GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#3
|
|||
|
|||
What will those provide? The links themselves don't matter - it is ANY link from ANY provider. Screenshots will only show the client in an active, but non-downloaded state.
What specific log do you want? |
#4
|
||||
|
||||
See my signature down below, a full log!
GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#5
|
|||
|
|||
With respect, the images in your sig docs are out of date - there is NO entry regarding Logging in the GENERAL tab.
|
#6
|
||||
|
||||
jdownloader.org/de/knowledge/wiki/support/create-a-jd-log?s=lng_de
Scroll down to JD2, as you can see no log level is needed here. GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#7
|
|||
|
|||
Ok, I see the option in JD2 now (not the same info as in your sig).
However, I want to know WHAT log files it is sending. Sorry, but I just don't send out unknown info to unknown people. You really do need to refine this process. You tell me which log files are necessary, and I'll be happy to review them (redacting as I feel necessary) and add them as an attachment here. |
#8
|
||||
|
||||
See your JD folder, logs folder.
It sends all of the logs in the marked timeframe. GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#9
|
|||
|
|||
Sending files that contain the URLs of items that are being downloaded is out of the question - and a foolish policy/procedure. SOME people use the program for transferring secure/private files - submitting the URL *could* be deemed a breech of security &/or contract.
Your logging procedures need to obfuscate the connection information (which would also include any account used). To do otherwise simply undermines users' confidence in the company. I *cannot* see how this is something that would be so complex for you to require ALL that information to figure out. |
#10
|
||||
|
||||
@DeathStalker
Clearly you have zero idea of the importance of logs, specially for identifying issues. It's far from a foolish policy or procedure! Once logs are uploaded very few people have access to them. a) they need to know your logid (jdlog://id), b) have a log reader tool, c) have an account to download log. We wont be obstructing information like connection info or account used. Those are all important fascists to identify issues. If its a breach of your contract with employer or provider, you should move away from download programs that log. I might add most download software have logs (in various forms). We have always logged in all versions of JDownloader, though at different levels. JD2 has new logging system, which is easier to identify issues from the geckgo vs having to change logging level, close program, reproduce issue to then upload reproduced event log. Now once issue has been experienced end users can just report issue and upload log from given time frame. This is way more user friendly specially for those that are no technically minded! We don't believe that this has in the past/current/future causes any serious shift in trust, or will cause issue with confidence in the company. By default logging events only happens for download download routine, and not fetch account (login info), If the download method requires a full login it will be logged. Generally our plugins use cached cookies to perform a quick login. fetch account info is only logged with debug mode is enabled (in plugin or in advanced settings). Logs are there for you and JDTeam if you wish to submit and no one else. Logs are used to determine faults which ALL information is pertinent. Obstructing log information would be against the purpose of such files. If you want issues identified and fixed send logs from an effected session, and not ALL sessions. If you rather not send logs from entire session, restart client and reproduce issue for that single event and then upload that log only. If you still don't agree, that is fine and your choice. But when you come for help, and your not willing to give logs or your user:password (if account based issue) to fix problem, we wont be able to assist you. That's just how it is! raztoki on behalf of JDTeam EDIT by psp Similar post of mine: http://board.jdownloader.org/showpos...2&postcount=10
__________________
raztoki @ jDownloader reporter/developer http://svn.jdownloader.org/users/170 Don't fight the system, use it to your advantage. :] Last edited by pspzockerscene; 06.12.2014 at 20:58. |
|
|