Opened 16 years ago
Closed 16 years ago
#8125 closed defect (fixed)
using a custom query with parameter row=description raises an error at preview- or submit-time
Reported by: | xyanipheia | Owned by: | Remy Blank |
---|---|---|---|
Priority: | normal | Milestone: | 0.11.5 |
Component: | general | Version: | 0.11.2.1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
This query raises the error:
query:status=assigned&status=new&status=reopened&max=10&order=priority&priority=highest&priority=high&row=description
This query string was simply copied from a custom query. Just try it out in a wikipage
Attachments (0)
Change History (5)
comment:1 by , 16 years ago
Milestone: | → 0.11.4 |
---|---|
Owner: | set to |
comment:3 by , 16 years ago
interesting, in an older query I found a better workaround:
the keyword is "verbose=1". Use it instead of row=description and it's just fine.
query:status=assigned&status=new&status=reopened&max=10&order=priority&priority=highest&priority=high&verbose=1
comment:4 by , 16 years ago
Milestone: | 0.11.6 → 0.11.5 |
---|
comment:5 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Internal errors fixed in [8124]. They happened when either row
or format
was used in query syntax (the correct keyword for showing fields on a separate row is rows
).
Try again with:
Note the
?
afterquery:
, which indicates that this is a query string copied from a query URL. See TracQuery, and #7699 for a trying to reconcile query URL and custom query syntax.That a query with a bad syntax generates an internal error is quite ugly, though. I'd like to fix that.