AttributeError: 'NoneType' object has no attribute 'perm'

[pv]

How to Reproduce

While doing a GET operation on /tags/blog, Trac issued an internal error.

(please provide additional details here)

System Information

Trac	0.11dev-r5823
Python	2.5 (r25:51908, Feb 4 2007, 01:17:05) [GCC 3.4.3 20050227 (Red Hat 3.4.3-22.1)]
setuptools	0.6c5
SQLite	3.3.12
pysqlite	2.3.3
Genshi	0.4.2
Pygments	0.8.1
Subversion	1.4.3 (r23084)

Python Traceback

Traceback (most recent call last):
  File "/usr/local/lib/python2.5/site-packages/Trac-0.11dev_r5823-py2.5.egg/trac/web/main.py", line 434, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.5/site-packages/Trac-0.11dev_r5823-py2.5.egg/trac/web/main.py", line 217, in dispatch
    resp = chosen_handler.process_request(req)
  File "build/bdist.linux-i686/egg/tractags/web_ui.py", line 182, in process_request
    TagMacros(self.env).render_listtagged(req, *tags, **args))
  File "build/bdist.linux-i686/egg/tractags/macros.py", line 214, in render_listtagged
    href, link, title = engine.name_details(tagspace, name)
  File "build/bdist.linux-i686/egg/tractags/api.py", line 362, in name_detail

[Emmanuel Blot]

This is not a Trac issue, but a tractags plugin issue.

Please report the issue to the plugin maintainer.

[Christian Boos]

The explanation on the bug report page should probably be enhanced. There are several options.

1. We could ask the users to not create a bug report here if the error is obviously related to a plugin.
2. We could have a line like |Create| a new ticket on |______| pre-filled with ​http://trac.edgewall.org. Ideally, we would even retrieve the appropriate URL from the plugin metdata, but that's a bit far fetched for now.
3. We could ask them to not really create the ticket but only to copy the generated description, which they can then paste in the right bug tracker.

Having those errors reported here is a bit inconvenient for us, but enables

[Emmanuel Blot]

Replying to cboos:

1. We could ask the users to not create a bug report here if the error is obviously related to a plugin.

The problem is that you have to teach the end user to search the very last line of the traceback to find whether it's a plugin or a Trac issue; not mentionning that it is sometimes difficult to figure out which plugin it is based on the egg name or path… Admins know that they have installed a plugin, end users don't care about the internals of the server install.

So as long as Trac is not able to report the issue comes from a plugin itself in the error trace, it is difficult to ask the end user to recognize the root cause from a Python traceback.

[Christian Boos]

Replying to eblot:

Replying to cboos:

1. We could ask the users to not create a bug report here if the error is obviously related to a plugin.

Admins know that they have installed a plugin, end users don't care about the internals of the server install.

Remember how semi-automatic error reporting works in 0.11: "end-users" are simply asked to report the error verbatim locally, and only the TRAC_ADMIN users are offered the possibility to report the error back on t.e.o.