Edgewall Software
Modify

Opened 13 years ago

Last modified 2 years ago

#4423 new enhancement

provide page decorators using wiki syntax

Reported by: ittayd@… Owned by:
Priority: normal Milestone: unscheduled
Component: general Version: 0.10.3
Severity: normal Keywords: post-process PageTemplates filter
Cc: Branch:
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 (0)

Change History (8)

comment:1 by Christian Boos, 13 years ago

Keywords: post-process template filter added
Milestone: 0.11
Owner: changed from Jonas Borgström to Christian Boos

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:2 by cmarschalek, 13 years ago

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 ;)

Last edited 7 years ago by Steffen Hoffmann (previous) (diff)

comment:4 by Christian Boos, 13 years ago

Milestone: 0.111.0

Not for 0.11.

comment:6 by Christian Boos, 10 years ago

Milestone: 1.0unscheduled

Milestone 1.0 deleted

comment:7 by Ryan J Ollos <ryan.j.ollos@…>, 7 years ago

Cc: ryan.j.ollos@… added

comment:8 by Ryan J Ollos, 5 years ago

Owner: Christian Boos removed

comment:9 by anonymous, 2 years ago

Keywords: PageTemplates added; template removed

comment:10 by Ryan J Ollos, 2 years ago

Cc: ryan.j.ollos@… removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.