Bug with content pickers in Courier's latest version
Hi,
I've been using the latest nightly build Courier_2.7.8.15.v6.zip and it seems to have a bug in it.
When publishing a node with content pickers, it assigns on the target server the content using Id's instead of folder structure so if the Id's aren't the same all the content gets messed up.
For example if we have
Node1 (Id 1) Node2 (Id 5) Node3 (Id 2) → Node 3.1 (Id 3) → Node 3.2 (Id 4)
and on ther server we have the same thing but:
Node1 (Id 3) Node2 (Id 5) Node3 (Id 4) → Node 3.1 (Id 2) → Node 3.2 (Id 1)
Then if on the first server Node 3 has two content pickers for 3.1 and 3.2, then after publishing what will happen is, Node 3 on the target server will have Node 1 and Node 3 in the place of the selected content instead of Node 3.1 and Node 3.2
Is that a known problem and is there a way to circumvent it? Is there a way to force courier to assign content using structure/page title instead of Ids?
Furthermore is there a way to seek a more advanced solution, perhaps write a custom resolver that might fix this?
Any suggestion and help is very much appreciated. Many thanks
Are you saying that as a consequence of Courier picking different node Id's on the target, content is getting mixed up/damaged? Does the content look ok on the target, despite the Id's changing?
Bug with content pickers in Courier's latest version
Hi,
I've been using the latest nightly build Courier_2.7.8.15.v6.zip and it seems to have a bug in it.
When publishing a node with content pickers, it assigns on the target server the content using Id's instead of folder structure so if the Id's aren't the same all the content gets messed up.
For example if we have
Node1 (Id 1)
Node2 (Id 5)
Node3 (Id 2)
→ Node 3.1 (Id 3)
→ Node 3.2 (Id 4)
and on ther server we have the same thing but:
Node1 (Id 3)
Node2 (Id 5)
Node3 (Id 4)
→ Node 3.1 (Id 2)
→ Node 3.2 (Id 1)
Then if on the first server Node 3 has two content pickers for 3.1 and 3.2, then after publishing what will happen is, Node 3 on the target server will have Node 1 and Node 3 in the place of the selected content instead of Node 3.1 and Node 3.2
Is that a known problem and is there a way to circumvent it?
Is there a way to force courier to assign content using structure/page title instead of Ids?
Furthermore is there a way to seek a more advanced solution, perhaps write a custom resolver that might fix this?
Any suggestion and help is very much appreciated.
Many thanks
Hi Nick
You've posted this in the contour section rather than courier
That awkward moment...
haha sorry about that :)
Please delete if you can. I can't...
Nick
I'm not entirely with you on your problem..
Are you saying that as a consequence of Courier picking different node Id's on the target, content is getting mixed up/damaged? Does the content look ok on the target, despite the Id's changing?
M.
is working on a reply...