Ticket #4423 (new enhancement)
Opened 5 years ago
Last modified 17 months ago
provide page decorators using wiki syntax
| Reported by: | ittayd@… | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | unscheduled |
| Component: | general | Version: | 0.10.3 |
| Severity: | normal | Keywords: | post-process template filter |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
right now, the PageTemplates proposal offers just a way of setting a template for a new page.
i'd like to have templates, for any page, using wiki syntax.
e.g., if i'd like to have each page list its tags at the top, i'll write a decorator like:
[[ListTags]]
{{1}}
Attachments
Change History
comment:1 follow-up: ↓ 5 Changed 5 years ago by cboos
- Keywords post-process template filter added
- Milestone set to 0.11
- Owner changed from jonas to cboos
comment:2 Changed 5 years ago by cmarschalek
I still think there should be a standard way for wiki page navigation and having breadcrumbs is (imho) a pseudo standard for wikis. But if it's only going to be possible via a template mechanism, here are my thoughts:
I believe in separating the formating code from the data, so I'm all for a way to define templates which are not just default text pasted into a new page. There are things which I don't want anyone to change, be it accidentally or deliberately.
Another thing to consider: What if I wanted to make a real comlex page layout with a large header and a footer. There would be a lot of text that gets in your way every time you want to create a new page. It would also be more error prone since you would have to be careful where you entered your own text into the "template".
Also, what if the template changes? The changes would only aply to new pages and you would have to manually change all the old pages (or use some form of search and replace).
So [2780] is certainly not solved for me with PageTemplates in the current form. It's not a duplicate for me neither (apart from the fact that this one is newer than mine) ;) As it looks right now, I will have to continue to aply the showpath hack everytime a new version gets released. :/ A nuisance, but one worth it since trac helps in so many other ways ;)
comment:3 Changed 5 years ago by cmarschalek
sorry, that should have been ticket #2780, not the changeset
comment:5 in reply to: ↑ 1 Changed 3 years ago by anonymous
Replying to cboos:
I think it's worth considering the option, but I'm not sure if it's the best way to implement customization for page layout.
0.11 will provide the possibility to write request post-processors which can filter the generated output, thereby introducing new possibilities to insert additional content in Wiki pages (or others).
Something similar to this was already requested some time ago for ShowPath integration (#2780, marked as duplicate).
comment:6 Changed 22 months ago by cboos
- Milestone changed from 1.0 to unscheduled
Milestone 1.0 deleted



I think it's worth considering the option, but I'm not sure if it's the best way to implement customization for page layout.
0.11 will provide the possibility to write request post-processors which can filter the generated output, thereby introducing new possibilities to insert additional content in Wiki pages (or others).
Something similar to this was already requested some time ago for ShowPath integration (#2780, marked as duplicate).