You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.
Usage
debug(objects...)
Description
Depending on the structr.conf flag log.debug this function behaves either like a NOP or if enabled, it behaves exactly like the log() function.
Example
${debug('Hello, world')}
results in the output of
Dec 12, 2015 6:11:29 PM org.structr.core.parser.Functions$74 apply
INFO: Hello, world
in the structr log file (if log.debug = true in structr.conf)
This function either behaves like a no-op or it behaves exactly like the log() function. This depends on the configuration setting log.debug.
debug(objects...)
| nodeextender.log | Enables the logging of generated Java code of the dynamic schema entities to the logfile. This setting allows you to investigate and debug the generation of Java code for your schema entities in cases where something goes wrong. |
| nodeextender.log.errors | Enables the logging of Java compilation errors when compiling the dynamic schema of your application. |
| log.requests | Enables full request logging for all requests handled by Structr. Caution, the log file can get very large when a lot of requests with lots of content are made. |
| log.debug | Controls the debug() built-in function, which will behave exactly like the log() function if enabled. |
| log.functions.stacktrace | Enables stacktrace logging for script calls and built-in functions. If enabled, a scripting error will write the full Java stack trace to the logfile. |
| log.prefix | Sets the prefix for the request log file that is written when log.requests is enabled. |
| log.javascript.exception.request | Adds path, queryString and parameterMap to JavaScript exceptions (if available) if enabled. |
| log.directorywatchservice.scanquietly | Prevents logging of each scan process for every folder processed by the directory watch service. |