using uSync for a while now without problems, but on our latest project we are facing with the following issue.
We have 3 environments:
DEV
STAGE
PROD
Using a VS Template we create a new project with some default content like Home, Contact and 404 page. We then publish this to all the environments. So first Umbraco gets installed and then uSync imports all the data without problems.
Then the next fase is to create the website on the DEV environment. We then take a full export of the data and include this into source control to be deployed to the STAG environment. We then launch the STAGE website and we see everything is going well in the logs with uSync, no errors. But when we lookup the result, we see the following:
Existing nodes ( home, contact, ... ) from the first run are updated correctly
All datatypes and etcetera are included in the backoffice
But no new content or media is insert
When we look in the database, indeed nothing is included.
Again no errors in the log. If you like I can sent you the log which contain also all debug output of uSync where you can see the mapping results.
About the languages in another thread, in the first run I already include a second language so won't think thats the issue.
Is there any way you can help me out or have a look at our project?
In the mean time, I will try to publish a new website with all data from the last export to see if that works. Keep you posted.
Edit webconfig appsettings umbracoversion in comments to reinstall umbraco
Edit uSyncbackoffice config and set import to false so first umbraco and all other tools gets installed nicely
Run the website
Verify the umbraco installation
Run the import manually
Result: Again all backoffice datatypes, doctypes, ... are imported nicely. Only content and media is missing, again the logs refer to no errors. Also the uSync log and details refer to importing everything, but no content in the database.
it all seems a little odd, if you want to send me a copy of hte uSync folder, and maybe the last log in app_data\logs, i will take a look, and see if there is anything i can spot.
there is, in fact, an existing issue for this, but due to the nature of it, it has been really hard to tie down, the stuff you sent has helped get more. so I will still track it all there. https://github.com/KevinJump/uSync/issues/236
When looking in the backoffice I now see all the content and other data. In your github you mentioned an issue with Macros. Indeed at our project the macros where also not imported, only the partial macro views. Now after the downgrade, these are also now in the backoffice.
Will keep this version for now untill further notice on your github issue tracker.
When you visit Belgium, I will sure be buying you a beer! Have a nice sunday afternoon.
I've just released an update (uSync.ContentEdition 4.1.9) which fixes this - really it's just a single update in the core around macros - updated everything to make sure all packages get the fix.
uSync Content Edition second run not working, no errors in log
Hi Kevin,
using uSync for a while now without problems, but on our latest project we are facing with the following issue.
We have 3 environments:
Using a VS Template we create a new project with some default content like Home, Contact and 404 page. We then publish this to all the environments. So first Umbraco gets installed and then uSync imports all the data without problems.
Then the next fase is to create the website on the DEV environment. We then take a full export of the data and include this into source control to be deployed to the STAG environment. We then launch the STAGE website and we see everything is going well in the logs with uSync, no errors. But when we lookup the result, we see the following:
When we look in the database, indeed nothing is included.
Again no errors in the log. If you like I can sent you the log which contain also all debug output of uSync where you can see the mapping results.
About the languages in another thread, in the first run I already include a second language so won't think thats the issue.
Is there any way you can help me out or have a look at our project?
In the mean time, I will try to publish a new website with all data from the last export to see if that works. Keep you posted.
Have a nice day
/Michaël
Hi Kevin,
here's what I also tried:
Result: Again all backoffice datatypes, doctypes, ... are imported nicely. Only content and media is missing, again the logs refer to no errors. Also the uSync log and details refer to importing everything, but no content in the database.
Can you help in this?
Thanks in advance!
/Michaël
Details about the installation:
uSync log details:
Hi Michaël,
it all seems a little odd, if you want to send me a copy of hte uSync folder, and maybe the last log in app_data\logs, i will take a look, and see if there is anything i can spot.
Hi Kevin,
I have sent this with Wetransfer to your [email protected] account.
/Michaël
OK, after a good 7 hours of tail chasing, I can't tell you what broke (yet) but I can tell you how to fix it (for now).
Downgrading to uSync.Content 4.1.5 seems to fix it : (but it might be the version of back-office or core that has the issue).
(uSync.BackOffice 4.0.8.0) (uSync.Core 6.0.9.0) [uSync.Content: 4.1.5.0]
there is, in fact, an existing issue for this, but due to the nature of it, it has been really hard to tie down, the stuff you sent has helped get more. so I will still track it all there. https://github.com/KevinJump/uSync/issues/236
Hi Kevin,
thanks for all the effort!
Here is what I did:
When looking in the backoffice I now see all the content and other data. In your github you mentioned an issue with Macros. Indeed at our project the macros where also not imported, only the partial macro views. Now after the downgrade, these are also now in the backoffice.
Will keep this version for now untill further notice on your github issue tracker.
When you visit Belgium, I will sure be buying you a beer! Have a nice sunday afternoon.
/Michaël
Hi Michaël,
Glad that works.
I've just released an update (uSync.ContentEdition 4.1.9) which fixes this - really it's just a single update in the core around macros - updated everything to make sure all packages get the fix.
Kevin
is working on a reply...