Extend and debug your Roxen and ChiliMoon webserver
Posted at 2004-11-15 by Michael Stenitzer, Last updated at 2004-11-21 by Michael Stenitzer
There are as usual several ways to get your debug and error messages:
You can controll the logging and visibilty of error information on your web page by several settings:
Note: The debug logs (including backtraces of internal errors and - if set so in the configuration - RXML errors) are rotated in ../logs/debug/default.1 - ../logs/debug/default.5. So after one restart you’ll find debug information from the last run in ../logs/debug/default.2.
Applies to: Roxen , ChiliMoon
Posted at 2004-11-15 by Michael Stenitzer, Last updated at 2004-11-21 by Michael Stenitzer
You can start Roxen with the flags -DPC_DEBUG and -DSBNOTIFY_DEBUG to get more information in the debug log about what the persistent cache and notification systems are doing.
You can also find some general cache information in the admin interface’s Tasks -> Status -> Cache status tab.
Applies to: Roxen , ChiliMoon
Posted at 2004-11-17 by Michael Stenitzer
There is some documentation cluttered all over the place:
Applies to: Roxen , ChiliMoon
Posted at 2004-11-17 by Michael Stenitzer
This is the way to acces variables in the "form" scope:
id->variables->var1
All other scopes, especially the "var" scope, must be accessed through
RXML.get_context()->user_get_var("scope.myvar");
RXML.get_context()->user_set_var("scope.myvar","value");
or
RXML.get_context()->user_get_var("myvar", "scope");
RXML.get_context()->user_set_var("var","value", "scope");
Note: You can also use this method in inline Pike, although it is easier to use the form scope.context in the Pike processing instruchtion <?pike ?> (see Roxen Scripting FAQs)
Applies to: Roxen , ChiliMoon
Posted at 2004-11-17 by Michael Stenitzer
Reload your module (in the module's status tab) in the administration interface or flush the cache (Tasks-> Maintenance-> Flush chaches).
Applies to: Roxen , ChiliMoon
A module can also be reloaded in the modules status page inside a virtual server's configuration. By doing this a module will only be reloaded inside the selected virtual server making it possible to debug changes to the module withouth breaking it in other vritual servers.
Posted at 2004-11-17 by Michael Stenitzer
For Roxen: Use Crunch, a kind of bugzilla at community.roxen.com/crunch/ . You have to register at Roxen Community community.roxen.com/register/
For ChiliMoon: Currently you have to use bugzilla at bugzilla.lysator.liu.se/
Applies to: Roxen , ChiliMoon
Posted at 2004-11-17 by Michael Stenitzer
Use debug options provided by the start programme.
./start -help
gives you more information this.
Another way to debug Roxen's / ChiliMoon's modules or core is to insert something like this in the code:
werror("report a: %O, b: %O\n", a, b);
The result will be printed into the debug files. (logs/debug/default.1). Read more at community.roxen.com/articles/004_errors/
You can also write from RXML directly into the debug log
<debug werror="This is printed in the debug log"/>
Applies to: Roxen , ChiliMoon
Comments
Posted by Matt Oros (2006-03-29)
Dear anybody who helps me I am just started working with linux,and installed debian3.1 with 2.6.8.2kernel with Roxen4.0.325 (apt-get install roxen4). I try to compile with source php4.4.2 module (configure –with-roxen=/usr/share/roxen4 –enable-roxen –zts make make-install).Everything makes without errors my questions: Where can I find php module files and how can I add module to Roxen?