You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cktricky edited this page Apr 9, 2011
·
4 revisions
The ModuleLogger module provides built-in functionality that can be utilized directly from a module by calling 1 of 2 methods: "output" or "dradis_output". Anytime these methods are called, wXf will automatically store the log under the wXflog folder (lib/wXf/wXflog/). Lets move on to utilization.
Output
** Two parameters **
output("some information to store in string value and can be a large data set", "filename.ext")
Three parameters
There really isn't much of a purpose of an additional "third" parameter as of now. It is currently under development. At the moment, it does nothing more than give an .html or .xml extension.
Example:
output("response", "response_file", "html")
...creates a file under the log folder called response_file.html
..OR
output("response", "response_file", "xml")
...which creates a file under the log folder named response_file.xml.
Again, this is for extensibility purposes (the reason for a third parameter). Although wXf performs basic checks like looking to see if you already have added the extension and then NOT appending an html/xml extension....it is really meant to convert the data you are storing to html/xml. To reiterate, this data is not converted into xml or html. It is simply given the extension