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

Migration from K12 to XPbK 29.6.0 is causing error #279

Closed
stefanie27 opened this issue Oct 29, 2024 · 3 comments
Closed

Migration from K12 to XPbK 29.6.0 is causing error #279

stefanie27 opened this issue Oct 29, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@stefanie27
Copy link

Brief bug description

We recently migrated a K12 DB (v 12.0.101) to XPbK 29.3.3 and need to do the same for the live DB. We got latest version of the Migration Tool (1.9.0 for v29.6.0) and created a new Xperience project with updated code and database to v29.6.0. After we migrated the DB, we encountered multiple errors. When running the site following error appears "InvalidOperationException: No content type has been configured."

image

I then followed a forum entry to recreate the PageContentType classes via dotnet run --kxp-codegen --no-build --type "PageContentTypes" . I receive following error when doing that "An error occurred during the code file generating process. fail: Kentico.Web.Mvc.IStartupConfigureAction[0]  Startup action 'Kentico.Web.Mvc.CodeGenService'. System.ArgumentNullException: Value cannot be null. (Parameter 'json')"

image

@ArjanvHugten
Copy link

ArjanvHugten commented Oct 29, 2024

I had the same thing with the code generation command, in my case it seems to be related to the 'AllowedContentItemTypeIdentifiers' missing for the fields with the 'Kentico.Administration.ContentItemSelector' control.

@tkrch tkrch self-assigned this Oct 29, 2024
@tkrch tkrch added the bug Something isn't working label Oct 29, 2024
@tkrch
Copy link
Collaborator

tkrch commented Oct 29, 2024

Hi @stefanie27, a fix has been merged into master in past 9 hours (#280). Can You try if issue still persists with latest version from master branch?

@stefanie27
Copy link
Author

Thanks @tkrch . I will check it out.

@tkrch tkrch closed this as completed Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants