Is it broken for you only when using Courier? Does it work withour Courier? What's your 301urlTracker version and Umbraco version?

Yes, it works without courier. Umbraco is 4.11.10, courier is 2.7.8.35, 301 tracker is 2.5.3.

Hey there. Great package. Problem I am having right now is that It does not track updated URLs across sites that are connected via Courier. I'm on Umbraco v6.1.6 Any recommendations?

Scenario - change URL on dev and then courier the updated node to production. Result: the updated name on production will not be reflected in URL redirector even though it is changed on dev URL redirect.

Any help appreciated!

Thanks

Jamie

I know this is an old topic, but I'm running into this now on a current site (U 7.3.x) and thought I'd see if anybody ever figured out any solutions. Thanks!

I recently read that the URL tracker does not work with 7.3. It is supposed to work with 7.4 however.

I read this post in the wrong order so my post maybe a little off topic....

Nothing to be done with courier either unfortunately. While it probably is something that the package developer could investigate, I ended up not using Courier. 301 redirects were more important than back end process and really did not want to hand code redirects every time a node name was changed.

I love the idea of Courier and tried VERY hard to make it work for a few clients, but never 100% successfully despite excellent support from the Umbraco team. I always ran into road blocks in EVERY scenario and the support effort far outweighed the benefits.

My big issue is that dev and production are not true 1-1 versions of each other. In my opinion this is a major flaw in architecture. (If there is a way around this that anyone knows I would LOVE to know how to create a true 1-1) and have it persist past the intital set-up. All the node ID's are different, for example, when you promote a node from dev to production my belief is that it is not truly updated, but the destination node is somehow deleted and replaced with a new node - I think this is why 301 re-director does not get triggered as it would only record a new entry on update.

A lot has changed since I wrote this post and my assumptions could be wrong on how Courier actually works behind the scenes. It is a very very complicated beast and my hat goes off to the developers for even attempting that. Umbraco content, media, dictionary items, views, etc are scattered everywhere and the fact that they can somehow be assembled into a package and moved is pretty amazing.

Cheers and good luck!

Yeah I spent some time digging in the source and I'm pretty sure I'm going to wind up running a scheduled task that just writes a couple simple queries:

SELECT UT.[Id]
      ,[OldUrl]
      ,[OldUrlQueryString]
      ,[OldRegex]
      ,[RedirectRootNodeId]
      ,UN1.uniqueID RRNGuid
      ,[RedirectNodeId]
      ,UN2.uniqueID RNGuid
      ,[RedirectUrl]
      ,[RedirectHttpCode]
      ,[RedirectPassThroughQueryString]
      ,[ForceRedirect]
      ,[Notes]
      ,[Is404]
      ,[Referrer]
      ,[Inserted]
  FROM [dbo].[icUrlTracker] UT
  left join dbo.umbracoNode UN1 on  UT.RedirectRootNodeId = UN1.id
  left join dbo.umbracoNode UN2 on UT.RedirectNodeId = UN2.id

That will translate node IDs on the UrlTracker table to GUIDs, so then you just need to get that over to the other server and basically do the same thing in reverse. If you set things up correctly you could actually do it with one giant cross-server query, else you can use memory to store that query results, for example.

is working on a reply...