Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Umbraco 13 and uSyncMigrations #265

Open
filefontaine opened this issue Apr 15, 2024 · 6 comments
Open

Umbraco 13 and uSyncMigrations #265

filefontaine opened this issue Apr 15, 2024 · 6 comments

Comments

@filefontaine
Copy link

filefontaine commented Apr 15, 2024

Hello,
i want to know if this package will be updated to U13.
Or if the best approach is to do U8 to U10 to U13 ?
Best,
Antoine

@KevinJump
Copy link
Member

Hi,

It should run on v13, (but i haven't tested it in a while)

there is no real differences in format between v10 and v13, so you should be be able to go v8 to v13.

@madsoulswe
Copy link

Migrated a smaler site v7 -> 13 and everything was smooth no issues!

@thomashdk
Copy link

Migrated a smaler site v7 -> 13 and everything was smooth no issues!

Hi I'm trying to convert Nested content in a Umbraco 13.
All datatype convertet, but it hasn't convertet the content.

It shows it has convertet it, but it's not.

Is that something you expericented ?

I can see in the migration file the content look correct ?
#269

@splab
Copy link

splab commented Aug 16, 2024

@thomashdk

You probably aren't doing it correct (and it's not really in the documentation yet):

  • You might not have enabled uSync Content export, make sure "UIEnabledGroups" isn't set to settings, do not try and use the linked usync.packer from "Getting started"
  • When you have made sure uSync content is enabled, you need to do a full export of your site using regular uSync, which will take settings and content
  • When converting, you need to use the exported zip file from above
  • Before converting (and for the love of god make sure you aren't doing this in production), if you are trying to convert an existing site and not migrate to a new, you must delete the content root and empty the recycle bin, else the GUIDs are going to be duplicate and no change will be done.

I will do a PR with updated howto for V13 and migrating on existing site soonish, but still trying to get member export to actually work.

@thomashdk
Copy link

thomashdk commented Oct 16, 2024

I'm getting stuck on these two issues.

image

The first is if there is a field that has been may mandatory after the node is created and no data i filled in. Then the node of course can't be saved and published. But I would be possible to just save the node.

The second is if the parent node is unpublished, then it also fails.

I have digged throw the code and can't find where it publish a convertet node.

Anyone that can point me in a direction ? :)
#269

@thomashdk
Copy link

I'm getting stuck on these two issues.

image

The first is if there is a field that has been may mandatory after the node is created and no data i filled in. Then the node of course can't be saved and published. But I would be possible to just save the node.

The second is if the parent node is unpublished, then it also fails.

I have digged throw the code and can't find where it publish a convertet node.

Anyone that can point me in a direction ? :) #269

@KevinJump can you point me in a direction of where the Published of a migrated node are done ? Then I will dig in to this issue :) !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants