`DoxygenPlugin` object has no attribute `get_htdocs_dirs`

[anonymous]

Latest version of DoxygenPlugin using Trac SVN trunk, generates this error in the log file, trac.log running as a plugin, TracDoxygen-0.1-py2.3.egg:

2006-05-25 11:11:12,310 Trac[main] ERROR: 'DoxygenPlugin' object has no attribute 'get_htdocs_dirs'
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/trac/web/main.py", line 299, in dispatch_request
    dispatcher.dispatch(req)
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/trac/web/main.py", line 189, in dispatch
    resp = chosen_handler.process_request(req)
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/trac/web/chrome.py", line 219, in process_request
    for dir in [os.path.normpath(dir[1]) for dir
AttributeError: 'DoxygenPlugin' object has no attribute 'get_htdocs_dirs'

[anonymous]

Since DoxygenPlugin is an ITemplateProvider, it needs to implement the method get_htdocs_dirs(). The following patch adds an empty implementation.

*** doxygentrac/doxygentrac.py.orig     Mon Jun 12 01:04:53 2006
--- doxygentrac/doxygentrac.py  Mon Jun 12 01:01:42 2006
***************
*** 54,59 ****
--- 54,62 ----
  
      # ITemplateProvider methods
  
+     def get_htdocs_dirs(self):
+         return []
+ 
      def get_templates_dirs(self):
          from pkg_resources import resource_filename
          return [resource_filename(__name__, 'templates')]

[Christian Boos]

Replying to anonymous:

... The following patch adds an empty implementation.

By looking at the doxygen plugin code, it seems that an empty implementation would be OK, but this doesn't mean you should close the ticket as fixed: this has to be done by the plugin author once the problem has been effectively fixed in the code.

[Christian Boos]

(and therefore reopening it)

[anonymous]

... but this doesn't mean you should close the ticket as fixed: this has to be done by the plugin author once the problem has been effectively fixed in the code.

So that would be probably never :-).

[Noah Kantrowitz]

Replying to anonymous:

... but this doesn't mean you should close the ticket as fixed: this has to be done by the plugin author once the problem has been effectively fixed in the code.

So that would be probably never :-).

If you would like to help with development, just email the current maintainer, and ask them to send Alec a message indicating that he should add you to this project.

[Radek Bartoň]

If you would like to help with development, just email the current maintainer, and ask them to send Alec a message indicating that he should add you to this project.

Sorry for not logged reply. We are curently solving that with Alec.

[Radek Bartoň]

Fixed in changeset 871.