Changes between Version 26 and Version 27 of LogViewerPlugin

Timestamp:

May 13, 2020, 10:59:04 PM (4 years ago)

Author:

figaro

Comment:

Remove poll

LogViewerPlugin

@@ -5 +5 @@
 == Description
 
-This plugin allows you to view your `trac.log` logfile without needing shell access to the server, just via the Web-UI Admin interface. You can select to only display messages from a specified log level (e.g. only warnings), as well as optionally including higher levels. So if you select "Debug" and all higher levels, this means the entire log will be displayed. Moreover, you may restrict the output to the latest N lines, and even filter for lines containing a specified string or even matching a regular expression.
+This plugin allows you to view your `trac.log` logfile without needing shell access to the server, just via the admin interface. You can select to only display messages from a specified log level (e.g. only warnings), as well as optionally including higher levels. So if you select "Debug" and all higher levels, this means the entire log will be displayed. Moreover, you may restrict the output to the latest N lines, and even filter for lines containing a specified string or even matching a regular expression.
 
 Be careful with large log files: use the tail-function to limit the output to the last few lines, because it would otherwise take a long time to display.
@@ -21 +21 @@
 [[Image(logviewer.jpg, border=2)]]
 
-As you can see, the log lines are quite colorful: each log level has its distinct color assigned. If you like to change the choice of colors here, you can easily apply your own style sheets. All elements can be identified without problems: the different log levels use classes, and even the other elements of the GUI use classes and ids. Furthermore, in this example you might note that obviously nothing was logged at "Info" level.
+As you can see, the log lines are color-coded: each log level has its distinct color assigned. If you like to change the choice of colors here, you can easily apply your own style sheets. All elements can be identified without problems: the different log levels use classes, and even the other elements of the GUI use classes and ids. Furthermore, in this example you might note that obviously nothing was logged at "Info" level.
 
 A viewer for any log file that resides on the same disk as your Trac project is LogWatcherPlugin.
@@ -96 +96 @@
 The meaning of those three settings corresponds to the similarly named items from the autoload, with the difference that the values here only apply when autoload is disabled.
 
-== Feedback
-
-Your feedback here, please. Or if you don't want to write something, use the poll below (you must be logged in to vote):
-  * olemis: This plugin is cool and very useful (especially to manage remote Trac instances ''';o)'''. 
-   Nonetheless, if you are debugging then you might like to try TracDeveloperPlugin too.
-
-[[Poll(Let others know what you think about the LogViewerPlugin:;I use it and I like it!;I use it and find it acceptable.;I tried it and didn't like it;I think it's great stuff and will give it a try!;I don't know what to think about it.)]]
-
 == Recent Changes