Opened 14 years ago
Closed 12 years ago
#7792 closed defect (invalid)
Error when viewing ticket
Reported by: | anonymous | Owned by: | Steffen Hoffmann |
---|---|---|---|
Priority: | high | Component: | AnnouncerPlugin |
Severity: | normal | Keywords: | configuration support |
Cc: | Trac Release: | 0.12 |
Description
I just installed AnnouncerPlugin-trunk and whenever I try to view a ticket I get the following error
How to Reproduce
While doing a GET operation on /ticket/3
, Trac issued an internal error.
Request parameters:
{'id': u'3'}
User agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/7.0.544.0 Safari/534.10
System Information
Trac | 0.12.1rc1
|
Trac | 0.12.1rc1
|
Babel | 0.9.5 (translations unavailable)
|
Genshi | 0.6
|
pysqlite | 2.3.3
|
Python | 2.5.1 (r251:54863, Oct 30 2007, 13:54:11) [GCC 4.1.2 20070925 (Red Hat 4.1.2-33)]
|
Python | 2.5.1 (r251:54863, Oct 30 2007, 13:54:11) [GCC 4.1.2 20070925 (Red Hat 4.1.2-33)]
|
RPC | 1.1.0-r9171
|
setuptools | 0.6c12
|
setuptools | 0.6c12
|
SQLite | 3.4.2
|
Subversion | 1.4.4 (r25188)
|
jQuery | 1.4.2
|
Enabled Plugins
AutocompleteUsers | 0.4.1
|
ChangeLogMacro | 0.2-r7927
|
DuplicateTicketSearch | 1.0.1
|
IsotomaTheme | 0.1
|
NatSkinTheme | 1.0
|
TicketBox | Rev
|
TracAccess | 0.1
|
TracAccountManager | 0.2.1dev-r9251
|
TracAjaxComments | 0.1
|
TracAnnouncer | 0.12.1.dev
|
TracDragDrop | 0.12.0.3-r8603
|
TracRecaptchaRegister | 0.2.1.2
|
TracThemeEngine | 2.0.1
|
TracXMLRPC | 1.1.0-r9171
|
Python Traceback
Traceback (most recent call last): File "build/bdist.linux-i686/egg/trac/web/main.py", line 511, in _dispatch_request dispatcher.dispatch(req) File "build/bdist.linux-i686/egg/trac/web/main.py", line 237, in dispatch resp = chosen_handler.process_request(req) File "build/bdist.linux-i686/egg/trac/ticket/web_ui.py", line 169, in process_request return self._process_ticket_request(req) File "build/bdist.linux-i686/egg/trac/ticket/web_ui.py", line 566, in _process_ticket_request get_reporter_id(req, 'author'), field_changes) File "build/bdist.linux-i686/egg/trac/ticket/web_ui.py", line 1515, in _insert_ticket_data req, ticket, action) File "build/bdist.linux-i686/egg/trac/ticket/default_workflow.py", line 321, in render_ticket_action_control return (this_action['name'], tag(*control), '. '.join(hints)) TypeError: sequence item 0: expected string, LazyProxy found
Attachments (0)
Change History (5)
comment:1 Changed 14 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 Changed 14 years ago by
No problem, but if you could give more details about the solution, it might be helpful. Maybe we could add better error handling? Or at least if someone else hits the issue you could leave the solution here.
comment:3 follow-up: 4 Changed 14 years ago by
Priority: | normal → high |
---|---|
Resolution: | invalid |
Status: | closed → reopened |
Trac Release: | 0.11 → 0.12 |
I have the same error, but I did not install any third party plugins at all. The error appears when I want to view the detail page of a ticket. I also got this error when creating a new ticket, but the ticket was created anyway. I can see the tickets in the timeline and in the ticket reports page, but i cannot access the detail page.
My environment:
System Ubuntu Server 8.04 32 bit Trac 0.12.1 Babel 0.9.5 (translations unavailable) Genshi 0.6 mod_python 3.3.1 MySQL server: "5.0.51a-3ubuntu5.7", client: "5.0.51a", thread-safe: 0 MySQLdb 1.2.2 Python 2.5.2 (r252:60911, Jan 20 2010, 23:30:56) [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu3)] setuptools 0.6c8 Subversion 1.4.6 (r28521) jQuery: 1.4.2
comment:4 Changed 12 years ago by
Keywords: | configuration support added |
---|---|
Owner: | changed from Robert Corsaro to Steffen Hoffmann |
Status: | reopened → new |
Replying to anonymous:
I have the same error, but I did not install any third party plugins at all.
Stop. So why do you bother reporting here? This is the wrong Trac instance for reports against Trac core, please go to trac.edgewall.org instead. Thanks for taking care.
comment:5 Changed 12 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
It seem to spring from configuration, so my best bet is, that's an local configuration error in your [ticket-workflow]
section.
Sorry for not reviewing that ticket much sooner. The previous author/maintainer is no longer in town to take care.
Scratch that... it's an issue with babel. My apologies