Running umbraco 4.11.7 and Courier 2.7.5.1.90 we purchased express license. When attempting to courier just content node it connects but then says no changes found even though i have just created a new node on master. I have also tried to push the other way get same issue.
Its due to the way the older version of Courier sees content changes, in the past it didnt always make a link between a change on a property and connected that with a change on the document, so just skipped the document no matter what, 2.7.8.15 has that fixed so it always examines child items and document properties for changes
I upgraded to 2.7.8.15 still the same issue. I then upgraded to .16 and still the same issue. One thing to note if you create a new node then publish it will courier fine. If you then unpublish and courier it will sync fine. It just seems to be when you create a new node then courier without publishing. Really weird.
Sorry to just reply with another "me too" but I've also had trouble with this and would like to know of any solutions. The only thing I tried was deleting things in the App_Data/courier folder.
Ismail said Courier is working fine for him in the other thread so perhaps he's since found a solution?
Just tested and yes i still have this issue. Although for my setup its not really an issue as we have the following, staging,dev and live. All content edits are done on staging, marketing then publish on staging, view the page if happy they courier to live. NO EDITS ARE DONE LIVE. Any dev stuff we do on dev the test then courier to staging then test then courier to live. The site as it stands for last couple months has been content only.
Courier express No changes found.
Guys,
Running umbraco 4.11.7 and Courier 2.7.5.1.90 we purchased express license. When attempting to courier just content node it connects but then says no changes found even though i have just created a new node on master. I have also tried to push the other way get same issue.
Any ideas
regards
Ismail
Just an update on this css/js and media works fine just seems to be content that is not synching
Regards
Ismail
Ok so if the item on master is published then it couriers across? Is that right behaviour? I thought unpublished would go over as well?
Regards
Ismail
Hi Ismail
Its due to the way the older version of Courier sees content changes, in the past it didnt always make a link between a change on a property and connected that with a change on the document, so just skipped the document no matter what, 2.7.8.15 has that fixed so it always examines child items and document properties for changes
/Per
Per,
I upgraded to 2.7.8.15 still the same issue. I then upgraded to .16 and still the same issue. One thing to note if you create a new node then publish it will courier fine. If you then unpublish and courier it will sync fine. It just seems to be when you create a new node then courier without publishing. Really weird.
Regards
Ismail
Did you get anywhere with this?
I'm seeing this "No changes found", on a pretty minimal site.
But I've made the changes!
Sorry to just reply with another "me too" but I've also had trouble with this and would like to know of any solutions. The only thing I tried was deleting things in the App_Data/courier folder.
Ismail said Courier is working fine for him in the other thread so perhaps he's since found a solution?
Guys,
Just tested and yes i still have this issue. Although for my setup its not really an issue as we have the following, staging,dev and live. All content edits are done on staging, marketing then publish on staging, view the page if happy they courier to live. NO EDITS ARE DONE LIVE. Any dev stuff we do on dev the test then courier to staging then test then courier to live. The site as it stands for last couple months has been content only.
Regards
Ismail
So are you able to Courier pages from STAGING to live?
What ever I do, it says no changes found, (new nodes or old nodes).
I've seen this problem with:
2.7.5
2.7.8.11
2.7.8.15
If I look at the cache files, the file does contain the change.
I have fixed this problem.
The LIVE instance was not being accessed via domain that the license covered.
-
Updated the config file to point at the licensed domain. FIXED.
If no changes are found, check the instance you are pushing too is on a licensed domain. (in the config file)
is working on a reply...