report-openoffice-team team mailing list archive

["Marcel van der Boom \(HS-Development BV\)" <mrb@xxxxxxxxx>]

Perhaps my comment #1 was not that clear. What I meant to say was this:

1. If *any* parser sits in a .py file on disk, the report does not get generated if it contains an item from a localcontext.update in the parser. Without a custom parser, the report works fine, although I have not tested this thoroughly as all my reports use a custom parser so far.
2. If I take the code of the parser and it into the parser field, with the parser type set to 'definition' the report does get generated.

- there is no difference is output set to pdf or odt

-- 
report generation does not work when server 5.0.10 started from init script
https://bugs.launchpad.net/bugs/582753
You received this bug notification because you are a member of Report
OpenOffice Team, which is the registrant for Report OpenOffice.

Status in OpenOffice.org Reporting Engine for OpenObject: New

Bug description:
After a server upgrade to 5.0.10 there is a difference with earlier versions. 

running the server from command-line works fine, but if the server is run from the init-script (debian style), the reprt generation does not work when a localcontext.update section is used in the parser.

The behaviour I am seeing is that the GTK client hangs, the web client times out after 15 seconds with an 'internal server error'. There are no error messages in any logs.

If i do not use any of the entries in the report which are coming from the added data in a localcontext update, both ods and pdf generation works fine (including data usage of user.company, data from a wizard)