[MAGNOLIA-38] Subscriber URI mapping Created: 12/Aug/04  Updated: 23/Jan/13  Resolved: 06/Nov/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.0 Final
Fix Version/s: 3.5 RC1

Type: New Feature Priority: Critical
Reporter: Boris Kraft Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to DOCU-50 document subscriber folder mapping Closed
is related to MAGNOLIA-1546 Subscribers with custom contexts are ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

It would be nice if we could configure from/to URI mapping so that I can do things like:

server a/whatever/news.html pubishes to server b/hoem/sameer/mynews.html



 Comments   
Comment by Sameer Charles [ 16/Aug/05 ]

we have to first decide the concept for incremental activation

Comment by Sameer Charles [ 03/Mar/06 ]

since we do not have transactional/ incremental activation, I will implement this for Simple activation for the final release

Comment by Sameer Charles [ 16/May/06 ]

Syndicator interface allow this, but you need to think how to present this to the user (config or runtime)

Comment by Magnolia International [ 10/Oct/07 ]

status ?

Comment by Magnolia International [ 06/Nov/07 ]

From/To subscriber mapping has been implemented

Comment by Boris Kraft [ 14/May/08 ]

Sameer, can you comment on how this feature works and if it is fully implemented or if work still remains? This feature has been requested by one of our clients now.

Comment by Sameer Charles [ 14/May/08 ]

This is fully implemented, I am not sure if this has been documented yet.
Until magnolia 3.0 each subscriber had the possibility to define on which path(s) its subscribed to, since 3.5.x content
subscribers can also define the landing url.

For instance:
Subscriber A

  • website workspace
  • fromURI = /site1
  • toURI = /
  • data workspace
  • fromURI = /
  • toURI = /

Subscriber B

  • website
  • fromURI = /site2
  • toURI = /
  • No data workspace
Generated at Mon Feb 12 03:13:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.