Ticket #770 (closed defect: worksforme)

Opened 2 years ago

Last modified 9 months ago

reports broken for 0.10: $NEW not defined

Reported by: fux@users.berlios.de Assigned to: bobbysmith007
Priority: normal Component: TimingAndEstimationPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10

Description

Hio,

trac 0.10 and the standard reports don't seem to work together (not even on the demopage):

https://216.155.103.1:50219/projects/TestForTimingAndEstimation/report/12 

{12} Ticket Hours
Report execution failed: Dynamic variable '$NEW' not defined.

thx for fixing or pointing me to a solution,

sincerly,

/fux

Attachments

Change History

10/05/06 08:18:31 changed by bobbysmith007

  • status changed from new to closed.
  • resolution set to worksforme.

THe reports are not broken. They use custom variables that are filled from the Billing and Estimation UI that was added. On the demo site this page is : https://216.155.103.1:50129/projects/TestForTimingAndEstimation/Billing

Please see the User Manual for more info.

Also if you want that page to work you need Javascript enabled (this is how it is building the links from the UI).

03/10/08 10:09:13 changed by anonymous

  • status changed from closed to reopened.
  • resolution deleted.

Do you mean this:

The reports can only be called from the Management Page. They will not work from the Trac View Tickets page. (Due to the custom variables that need values).

If I call the reports from the Management Page, it shows me another error. Report execution failed: near "AS": syntax error

However no report available.

03/10/08 10:25:41 changed by anonymous

PS: I've forgot it.

Using SQLite 3.3.8 on Ubuntu.

03/10/08 10:29:28 changed by bobbysmith007

Well then this is not really the same problem as this ticket describes, but either way. Please paste in the contents of the report you are trying to run. Also any trac logs you have related to this might be helpful and might also give you the contents of the report you were trying to run when it failed.

Thanks, Russ

03/10/08 10:31:55 changed by bobbysmith007

ps. that error usually comes from not being able to CAST(col as OtherType?). This was unsupported in previous versions of sqlite, though I thought that 3.3.8 was well past that revision. You should be able to check this by running a query like "SELECT CAST(1 as text)" in the sqlite command line program.

03/10/08 11:07:03 changed by anonymous

  • status changed from reopened to closed.
  • resolution set to worksforme.

Sorry for reopening the bug.

Just need to rebuild Python SQL binding because they were using an older version of SQLite.

Then upgrade all projects databases.

Sorry again for not posting in the right place. Thanks for your time.

03/10/08 13:43:58 changed by bobbysmith007

Glad this worked out for you

Cheers,

Russ

Add/Change #770 (reports broken for 0.10: $NEW not defined)




Change Properties
Action