#2294 closed defect (invalid)
Missing "entry_point" within setup.py
| Reported by: | Owned by: | yu-ji | |
|---|---|---|---|
| Priority: | normal | Component: | WikiIncludePlugin |
| Severity: | critical | Keywords: | |
| Cc: | hendy@… | Trac Release: | 0.11 |
Description
The file "setup.py" should contain an 'entry_point'
setup(name=PACKAGE,
version=VERSION,
packages=['wikiinclude'],
entry_points={'trac.plugins': ['wikiinclude.wikiinclude=wikiinclude.wikiinclude']})
Attachments (0)
Change History (6)
comment:1 Changed 18 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 Changed 18 years ago by
| Cc: | hendy@… added; anonymous removed |
|---|
comment:4 Changed 18 years ago by
The Include macro is rather useless compared to WikiInclude. I like the concept better, but is there a way to allow the included pages to render, e.g. provide similar function to WikiInclude?
comment:5 Changed 18 years ago by
Sure, use text/x-trac-wiki or application/x-trac-wiki as the MIME type just like in the browser. Probably make sense to have this be the default format for the wiki include source, I'll change that.
comment:6 Changed 18 years ago by
So far, I have not gotten it to successfully render anything. I am using the Tags plugin, and I previously used WikiInclude to include some canned search pages. When I try this, no matter what mime-type I use, it's not rendering the page. It encapsulates similarly to a {{{ }}}.
Am I doing something wrong?
comment:7 Changed 18 years ago by
This attachment at the IncludeMacro page appears to do this, but it's not ported to 0.11. I try later, I'll bet it's simple. However, it did do what I wanted (apparently).



This plugin uses the older style trac_plugin.txt file. If you need something more 0.11 compatible, try the IncludeMacro.