I need as much help as possible as this one is increidbly tricky!
Few days ago we deleted from the database some orphan nodes from umbraco node because of this.
After this, Courier went mental.
I'm using Umbraco 4 latest version with Courier 2.7.8 nightly build v4
What happens now is
a) Courier packages hundreds of irrelevant files than the ones that we are couriering (even if couriering just one file)
b) On the target it randomly assigns different parent IDs to random nodes accross the site, completely unrelated to the ones we are couriering. As a result these nodes disappear from the content tree
Why would courier depend on orphan old deleted nodes and is there any way of fixing this mess ? If someone has an idea, please I want to hear it..
Thats sounds like a total disaster I only wish this product was part of the rest of the open source effort. There would probably be some initial gaffaws and then a lot of mucking in (and out) to clean up this mess!
Per is probably the only who can help, and you know how often he pops up!
If you've removed nodes directly in the database, and not using the APIs, then you need to clear out the /app_data/courier/cache folder, since courier and the generated revisions doesnt know your data has changed, so thats why all these id's appear, courier cant find them, but will try to complete data no matter what.
Courier completely irrational behaviour
Hi everyone
I need as much help as possible as this one is increidbly tricky!
Few days ago we deleted from the database some orphan nodes from umbraco node because of this.
After this, Courier went mental.
I'm using Umbraco 4 latest version with Courier 2.7.8 nightly build v4
What happens now is
a) Courier packages hundreds of irrelevant files than the ones that we are couriering (even if couriering just one file)
b) On the target it randomly assigns different parent IDs to random nodes accross the site, completely unrelated to the ones we are couriering. As a result these nodes disappear from the content tree
Why would courier depend on orphan old deleted nodes and is there any way of fixing this mess ?
If someone has an idea, please I want to hear it..
Hi Nick
Thats sounds like a total disaster I only wish this product was part of the rest of the open source effort. There would probably be some initial gaffaws and then a lot of mucking in (and out) to clean up this mess!
Per is probably the only who can help, and you know how often he pops up!
Sorry!
Martin.
If you've removed nodes directly in the database, and not using the APIs, then you need to clear out the /app_data/courier/cache folder, since courier and the generated revisions doesnt know your data has changed, so thats why all these id's appear, courier cant find them, but will try to complete data no matter what.
is working on a reply...