[MAGNOLIA-1123] make templates useable in different repositories/workspaces Created: 10/Oct/06  Updated: 23/Jan/13  Resolved: 25/Oct/06

Status: Closed
Project: Magnolia
Component/s: templating
Affects Version/s: None
Fix Version/s: 3.0 RC4

Type: New Feature Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File patch.txt     Text File patch.txt    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Since we can map uri to different repositories (dms, ....) we should enhance the tags/interception so that they use this information. Currently they fall back always to the website repository



 Comments   
Comment by Chris Miner [ 24/Oct/06 ]

Here's a patch for the main bar, new bar, and edit button inline gui components which doesn't hard code the website references. With this patch, pages from alternate repositories can be opened for editing.

Comment by Philipp Bracher [ 25/Oct/06 ]

I commited. Nice feature

THANKS A LOT!

Comment by Chris Miner [ 27/Oct/06 ]

I noticed after working with it a while, that moving paragraphs around and deleting them doesn't work. I'll submit a patch with the simple changes I made to the MgnlInterceptorFilter. In the process I copy pasted setHandleAndMapping from MgnlCmsFilter. Probably that functionality belongs elsewhere. Perhaps even the first filter in the filter chain. Or maybe it is reasonably part of the MgnlContextFilter?

Comment by Chris Miner [ 27/Oct/06 ]

Here's the patch with changes to the interceptor.

Comment by Philipp Bracher [ 31/Oct/06 ]

Applied. Thanks!

About setHandleAndMapping(): I think we should extract a own filter for this processing. Something like a RepositoryToURIFilter.

I will add a task.

Generated at Mon Feb 12 03:23:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.