One of our client runs a new website based on
"umbraco v 4.5.2 (Assembly version: 1.0.3891.20719)" this install needs to have
updates done across two Umbraco instances. The site implementation was extended
with Courier v. 1.2.
We experience some issues in the overall interchange of
site content via Courier, therefore the most pressing issue and potential
solution, might be quite simple. When can we expect the new release of Courier
2.0? -magicially solve the sync issues ;)
We experience two major issues in the overall interchange
of site content and maintenance:
- Updates between the two instances can only be done, as
"admin"
- Content updates fails to maintain consistency between
instances.
We have attempted updating to Courier 1.3, this gives us
other issues in the implementation resulting in failed updates. Courier version
1.2 when logged in as the default "admin" user seems to be the
solution closest to the solution wanted.
What is the potential cause of not being able to add
valid Courier users in our set-up?
In updating content between the site instances we are
able to update "raw" content assets, images, media and new pages.
Some content of existing and new pages are dependant of
other nodes. When updating via Courier these dependencies is all screwed up and
the "production" instance fails to reflect updates done via Courier
on the staging instance.
One of the symptoms, perhaps the cause of failed updates.
When inspecting node ID's of subnodes between the two instances these are not
consistent.
For instance, one of the recent sub-nodes at the
"authoring" instance;
- 1col_Play_ss11 Id 1446, created 05/01/2011 15:14:48
When transferring this to the "deployment"
instance lists properties as;
- 1col_Play_ss11, Id 1440, Created 05/01/2011 15:14:48
I suspect when certain topnodes use subnodes the topnodes
are internally dependant af subnode ID's? -is there any way to ensure node ID's
are kept consistant across instances.
Any known solutions and best practices to maintaining the
two instances synchronized is greatly appreciated...
Courier update fails
One of our client runs a new website based on "umbraco v 4.5.2 (Assembly version: 1.0.3891.20719)" this install needs to have updates done across two Umbraco instances. The site implementation was extended with Courier v. 1.2.
We experience some issues in the overall interchange of site content via Courier, therefore the most pressing issue and potential solution, might be quite simple. When can we expect the new release of Courier 2.0? -magicially solve the sync issues ;)
We experience two major issues in the overall interchange of site content and maintenance:
- Updates between the two instances can only be done, as "admin"
- Content updates fails to maintain consistency between instances.
We have attempted updating to Courier 1.3, this gives us other issues in the implementation resulting in failed updates. Courier version 1.2 when logged in as the default "admin" user seems to be the solution closest to the solution wanted.
What is the potential cause of not being able to add valid Courier users in our set-up?
In updating content between the site instances we are able to update "raw" content assets, images, media and new pages.
Some content of existing and new pages are dependant of other nodes. When updating via Courier these dependencies is all screwed up and the "production" instance fails to reflect updates done via Courier on the staging instance.
One of the symptoms, perhaps the cause of failed updates. When inspecting node ID's of subnodes between the two instances these are not consistent.
For instance, one of the recent sub-nodes at the "authoring" instance;
- 1col_Play_ss11 Id 1446, created 05/01/2011 15:14:48
When transferring this to the "deployment" instance lists properties as;
- 1col_Play_ss11, Id 1440, Created 05/01/2011 15:14:48
I suspect when certain topnodes use subnodes the topnodes are internally dependant af subnode ID's? -is there any way to ensure node ID's are kept consistant across instances.
Any known solutions and best practices to maintaining the two instances synchronized is greatly appreciated...
Best,
Nikolaj
is working on a reply...