Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Justin Spradlin 139 posts 347 karma points
    Jun 09, 2011 @ 18:36
    Justin Spradlin
    0

    How are nodeId values transfered?

    When you do a transfer from Server 1 > Server 2 using Courier 2, are the node id values the same on both sides, or are they different and all links are just updated? 

    Here is my situation. I have a site that has a custom data type called 'Playlist'. I can add 'PlaylistElements' to a playlist. I have an external site that uses a simple page to embed the playlist in an iFrame. Right now I am exposing a page that renders the content for the external site at http://www.mydomain.com/embed?playlistId={NODEID_OF_PLAYLIST}. In the other application we have a syntax that we use to create an iframe that points to http://www.mydomain.com/embed?playlistId={NODEID_OF_PLAYLIST}. 

     

    I would love to use courier, but if the node ids will be different on production and dev environments then this would be a big issue, since my links to Umbraco hosted playlists will break. I just want to make sure that courier is not just updating any links and is actually doing identity inserts in the database for the new content. 

    I am open to any suggestions if anyone had a better way of doing this. 

     

    Thank you,

     

    Justin

  • Antony Briggs 78 posts 103 karma points
    Jun 09, 2011 @ 18:45
    Antony Briggs
    0

    I don't have any experience of Courier 2 yet, but with Courier 1 the NodeIds could be different on production and staging. The Courier framework would then deal with updating the Ids in the content.

    The issue is that the NodeId is the auto_increment id of the Node Table, and you can choose to courier different parts of your content tree at different times.

    In your scenario, I would suggest adding a property to your playlist nodes that identifies them. A GUID would be easyest.

    TTFN

    Ant

  • James Drever 118 posts 149 karma points
    Jun 09, 2011 @ 20:18
    James Drever
    0

    Just to confirm: with Courier 2 as well as Courier 1, you are not going to get identical node ids in different environments.  As Anthony suggests above, you are going to need a different solution, like a GUID.

    James.

  • Justin Spradlin 139 posts 347 karma points
    Jun 10, 2011 @ 07:53
    Justin Spradlin
    0

    Thank you, I think the GUID for an "embedCode" will be much safer than using the Primay Key value for the node. 

    Forgive me for getting off topic but, I have updated my document type and I am very new to XPath and XSLT. I am trying to use a Razor script to render this template. 

    I have the structure 

    Home

    -Playlists

    -Embed (page that renders a playlist using a Razor Macro by passing the query string value of the embedCode to pick the right Playlist)

    -Playlist (1)

    -Playlist (2)

    -Playlist (3)

    The playlist has the embedCode property. So how would I create an XPath request on @Model to give me the right Playlist DynamicNode? I am totally lost as to how to construct the request.


    Thank you,

    Justin

Please Sign in or register to post replies

Write your reply to:

Draft