For example; You navigate to the health section of a site beacause you are interested in training and diet. An article has been published under food recipieswhich is on a different section of the website - or even wors, on a different web site using the same EPiServer.

It's bad usability to "move the user" from one place to another. My guess is that the user would like to stay on the same section without having to navigate back.

But the tab "Shortcut/External" also gives you the option to "Fetch data from page in EPiServer".That would allow you to create an article under section X, create a reference page under section Y (linking to the first page), and when clicking the link to your page under section Y, you'd stay in section Y but the contet of your Y page would be fetched from the article under the X section.

-start (id: 1)

-X(id: 2)

--article(id: 4)

-Y(id: 3)

--article from x (id: 5, fetch data from 4)

I might have misunderstood you, but isn't that what you are requesting?

Perhaps this thread is kind of dead.....long time since it was created. But issue is still relevant.

We use this feature and want to use use it more frequent. BUT - the problem is that writers do not have a clue about that a page might be shown elsewehere than the original source. Even if the made the "Fetch data from page in EPiServer" themselves.

They forget and they start to build threes below that page. And that threestructure is NOT shown at the other places. So writers believe then have updated information but information is missing at the "other" place.

I would like to have either:

a warning mechanism that tells me that this page is shown elsewhere when I start to build threes udner it

or a checkbox telling CMS to show the new three structure at the "other" place - if it is relevant