grenersen
Aug 30, 2010
  4535
(1 votes)

New module, Epicode CrossPublish

Many RFI´s (Request For Information) and RFP´s (Request For Proposal) ask for the possibility to make one page available to multiple locations (eg. a local news article should be available in the central news article structure). Epicode CrossPublish lets you publish one page to multiple structures using the built in feature of "Fetch data from...". Even though this is possible to manually you can imagine the work needed in order to make one page available to multiple locations (Right click, create, select template, write a name, press “Shortcut/ external link”, select “Fetch data from”, navigate to the desired page, press Save and Publish (one down x to go…)

CrosspublishpublishCropped

The module was created as a Proof of Concept for a customer meeting and has later been updated with a simple report on where a specific page has been published to. In the specific customer case they wanted to publish one central news article to 7 regional news containers. The catch is that they wanted it to be searchable and appear as it was a local news article. To complicate the picture even more, the access rights within the region could differ (meaning that not all in the region should be able to read the article). Epicode CrossPublish overrides the access rights set on the receiving structure based on what is set on the “master”.

In the good name of sharing and as a proof of what can happen if we share, Epicode CrossPublish utilize a module available on Epicode, Logica Page Container in order to allow drag&drop pages from the EPiServer tree structure.

The module comes with a Deployment Center installation file (no login required) and the source code is available, both for browsing and check out (requires login).

To Epicode CrossPublish start page

Aug 30, 2010

Comments

Jeff Wallace
Jeff Wallace Sep 21, 2010 10:33 AM

Nice. I like. :)

Lars Bodahl
Lars Bodahl Sep 21, 2010 10:33 AM

This is a request we get a lot of times. I like the way you (Mari?) implement it :)

Please login to comment.
Latest blogs
Creating an admin tool - unused assets

Let's make an admin tool to clean unused assets and see how to extend your favorite CMS with custom tools and menues! We will build a tool step by...

Daniel Ovaska | Apr 15, 2026

Running Optimizely CMS on .NET 11 Preview

Learn how to run Optimizely CMS on the .NET 11 preview with a single-line change. Explore performance gains, PGO improvements, and future-proofing...

Stuart | Apr 15, 2026 |

Your Optimizely Opal Is Probably Burning Carbon It Doesn't Need To

Four patterns Optimizely practitioners could be getting wrong with Opal agents: inference levels, oversized tool responses, missing output...

Andy Blyth | Apr 15, 2026 |

Optimizely CMS 13: A Strategic Reset for Content, AI, and Composable Marketing

Optimizely CMS 13 is not just another version upgrade—it represents a deliberate shift toward a connected, AI-enabled, and API-driven content...

Augusto Davalos | Apr 14, 2026

The 74% Problem: Why Most Companies Are Getting AI Wrong

I’ve seen this before… The pattern. The rush, the excitement, the scramble to adopt something new before anyone has stopped to ask what problem it...

Mark Welland | Apr 14, 2026

Scheduled jobs with parameters

Scheduled jobs is an integral part of most Optimizely solution but the UI has, in my opinon, always been lacking in usability and features. Earlier...

Per Nergård (MVP) | Apr 14, 2026