I'm guessing that David Peterson's "Linking Plugin" [1] could be extended to provide this functionality and in addition we could have a seperate macro that could be placed in to templates (such as the "Scaffolding Plugin" [2]) so that when a template is used the page is given the label as you mentioned in your post to the list.

Adaptavist have a client who's going to need auto-labelled pages so we' be happy to contribute to the development

Guy
http://adaptavist.com

[1] http://www.randombits.org/display/CONF/Linking+Plugin

[2] http://www.randombits.org/display/CONF/Scaffolding+Plugin

To really support that functionality (with metadata-report in particular) it would be excellent if you could create page templates that automatically have a given label. This way you could make standardized entry forms that can be used in a single step (without users also needing to add a label). Auto-labelling when generating from a template would also just be generally useful.

Another option could be to have a macro like {setpagelabel:BogusLabel} that when executed adds the label to the page. You could just put this in the template and get the same result I'm after. Does such a macro exist? It seems reasonable that it might be possible as a user macro if I were to dig into what happens when you set a page label (or with a nice velocity one-liner if I could ever sort out the Confluence objects there), but if it is already done that would obviously save me some time.

In some ways, I want to be able to create a page in Confluence and then declare it as a template. Then all of its labels etc would come along naturally. It would also allow templates to be versioned which would be a huge help. Really, any time you type text into Confluence it should be stored as content. That covers templates, layouts, macros, user profiles etc. Of course, this is a much bigger issue.

I second that - that would be great. "All it would take" is in locations where you can set up template, add an option for "use markup below" or "use markup from page name", where in the latter you can put a space:page reference from which to grab the markup at the time of requesting a template.

Added bonuses:

• display the current markup from the page in the already-provided "large" text box (uneditable in this case)
• have a "take me to this page, please" link so you can tweak the template

On the same subject - the dynamic sizing on the template editing textbox is brutal! It uses screen space very inefficiently and my markup wraps too easily. It should be widened. It is nowhere near as bad as the puny user macro textbox, though...

If searching for features in the Conlfuence JIRA weren't so time-consuming/painful I'd either vote for or add these... right now my laziness is taking over.

Russ

And, slightly off-topic, I agree that it would be good to update the template editing UI so that it is pretty much the same as the 'Edit Page' UI, including the notation guide summary and Rich Editor (even though I don't actually use it myself). Same goes for personal profiles.

http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134

I'm currently testing a work around using the 'where' attribute but I have concerns that this where clause won't be respected on cascaded delete. i.e. if you remove all templates for a space this could also lead to all ContentEntityObjects (Pages) for the space being deleted.

More details when I have them...

When is this functionality going to find its' way into a public Confluence release? I'm really looking forward to having access to this.

Thanks!

This is implemented and will be part of 2.6. This is expected to be release within the next 6 weeks or so.

Cheers,

Paul C