Changes between Version 17 and Version 18 of TracTroubleshooting

Timestamp:

Mar 13, 2017, 11:33:35 PM (7 years ago)

Author:

Ryan J Ollos

Comment:

Minor editing.

TracTroubleshooting

@@ -30 +30 @@
 == Check the Logs
 
-The log output is an excellent source of diagnostic information. If a //Component// has been enabled but the corresponding feature is not available, the immediate cause may be that the //Component// is failing to load. //Component// loading is logged at //DEBUG// level when restarting tracd or the web server. Additional debug information and tracebacks may also be logged.
+The log output is an excellent source of diagnostic information. When a feature is unavailable it's often the case that the Trac or plugin //Component// that implements the feature has failed to load. This could be due to a programming error, missing dependency or installation problem. //Component// loading is logged at //DEBUG// level when restarting tracd or the web server. Additional debug information and tracebacks may also be logged.
 
-Set the [TracLogging#LogLevels LogLevel] to //DEBUG//, restart tracd or the web server and then inspect the log.
+Set the [TracLogging#LogLevels LogLevel] to //DEBUG//, restart tracd or the web server and then inspect the log. See TracLogging for additional information.
 
 == Debugging Trac