Oct 072015
‘this site's documentation for its users’, problem report NT5T3Z, problem solving NME8N3 Add comments
- NVUWH1 ‘This {post & its comments}’s ‘TOU(Terms Of Use) including copyright ©, confidentiality/privacy, & info’s allowed use’ is JotHere.com’s default TOU(Terms Of Use) except:’ none.
-
.
.NVV7V9 post name:
‘‘if you are impeded by most any problem, well at least tech problems, what to do ’NVUVL5’
- NVUWNZ ‘To reply & discuss, please use JotHere.com’s default methods (click) except:’ none.
- NVUWOC table of contents overall for remainder: ‘definition’ + ‘post history additional’
- NVTN8C ‘definition’:
- NVUWMT means what the name says
- NVUVMG –here’s generally what one should do for seemingly everything one is reasonably asked or invited to do, especially personally
- NVUVFL do in order:
- NVUVGM do self-diagnosis
- NVUVQI check for directions (that doesn’t significantly interrupt anyone)
- NVUVRN check the text or other content giving you directions that you followed them else if they’re good
- NVUV94 web search, as Google search, for what you’re doing especially what’s going wrong especially error message(s) you’re getting
- NVUT8U generally try again say up to 3x and try it say 3 different allowable ways
- NVUTJL generally including trying how you think or/and guess it should work, provided that approach would still be reasonably {acceptable else allowable}.
- NVUTS1 including, after say 2 or 3 attempts, as time allows, trying something else which will also need to be done for the mission else doing something else, then coming back to this to try a few more attempts, as time allows –as getting away from the matter regularly leads to solutions indirectly.
- NVUTDI provided
- NVUTG4 the attempts are quick, notably faster than it would take to report back problems and wait for help here
- NVUTEA you’re not trying something dangerous, as defusing a bomb or something that could reasonably could delete some data, which will rarely be the case unless say you’ve received reasonable-seeming warnings of such
- NVUVQI check for directions (that doesn’t significantly interrupt anyone)
- NVUWYS find & put in place workarounds –for until a better solution comes notably from the problem report(s)
- NVUTN7 If after the above, you’re still having significant problems with this mission, report back the problem you’re having in {full detail, notably so those you’re reporting to can significantly diagnose & help based on just that your report message}
- NVUU3J including, as best you can, do NOT reply on others helping you līve else very-interactively, say from you having ‘the līve-only mis-believe/practice’
- NVUX2X first reasonably try to find & use any existing report threads instead of creating a new separate report
- NVUX5Q typically the best of those likely found by your web searching
- NVUX79 as
- NVUXG9 for your report, use the best communication methods possible
- NVUXL9 including make it as public as effective to help & gather the most people.
- NVUTZ5 as well known by software developers and other techies, including full details, from generally most important:
- NVUULG what exactly are you seeing/experiencing that appears wrong
- NVUTZJ what error messages are you getting
- NVUUW0 where in the process did you run into problems –if not answered by question NVUULG (previous)
- NVUUMA where/when has this worked for you and not worked for you, including telling what attempts you tried and especially when/where exactly did it stop working.
- NVUX20 workarounds you’ve found
- NVUUQV what are the names of the relevant tools/components, especially software programs, you’re using to accomplish the job, and especially for each which aren’t current, what is the version/date of each.
- NVUULG what exactly are you seeing/experiencing that appears wrong
- NVUUBL so naturally do NOT say just make a vague report, including just generalizations such as ‘I can’t make it work’ or ‘I can make it out’(quote inspiration) –well unless you’re goal is just to obviously waste time so really frustrate others, which hopefully it isn’t.
- NVUV8B note just writing up the report is useful in itself: indeed in doing so, I find about 1/4 the time I solve the problem and nearly all the time I come up with general relevant solutions.
- NVV8J7 aside: per section subject, add post to category ‘problem report NT5T3Z’
- NVUXDZ work on something else until responses to your problem reports, then act on them.
- NVUVGM do self-diagnosis
- NVUVV3 ‘‘section history additional’ ‘in reverse start order’:’
- NVV7WT among many inspirations, recently is /5037#NVV2W1 then /4875#NVT6R7
-
- NVUVJZ annex
- NVTRIQ ‘post history additional’: ‘‘post history additional’ ‘in reverse start order’:’
- NVV8NV ‘{post.status.snapshot{;date ’20151007Wed1255pst‘;after ID ’minutes 0‘;revision ’1‘;version ’1.0‘;words ’910‘;as ’small TODOs but need to get this Published as being 1st linked to‘;do ’Publish 1‘}}’
- NVV8KW spellcheck;{update IDs to latest format: 56 replacements}
- NVV7RR add post to category ‘this site’s documentation for its users NQBFBL (31)’ as handy there
- NVV7MJ TODO: proofread + verify links:
- NVV7KJ completed initial content
- NVUW5P ‘{post.status.snapshot: date ’20151007Wed0825pst‘;after ID’ minutes 0‘;revision ’0‘;version ’0.0‘;words ’~300‘;as ’content requested for /5037#NVUT6O‘;do ’minutes ago, to get a reasonable template only (no source text), from http://1.jothere.com/wp-admin/edit.php?post_type=post pick the post with the highest post #, post revision http://1.JotHere.com/5037#NVTRF0 , and there do “Copy to a new draft”, so created fresh this post http://1.JotHere.com/5045#NVTR95 then “cut {all its content not to be reused here, so the content just applying to the template, so all the posts’ fully stated points including their KCGUIDs} replacing with new ones.”‘}’.