What are the differences between Orchard Core source branch Release/1.0 and the available NuGet packages? #10208
Unanswered
kevinsmgov
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Your issue seems related with the OrchardCore.Sitemaps module. Try to disable it and see what happens. For changing Orchard Core to version 1.0 you just need to change it in each custom .csproj you made or use a .props file to set a PropertyGroup value that can be imported/reused in all your .csproj. The error here doesn't seem to be related with out of sync packages but more likely an issue in the ContentTypesSitemapUpdateHandler. Please report the issue with some repro steps (sample data) so that we can fix it. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I started diagnosing an error occurring when a content item that was imported from a deployment package was altered and saved (or attempted to save, the error blocked it).
The errors were all of the following format:
although the index provider sometimes was the TextIndexProvider
To diagnose the problem, I connected to the same database with the full Orchard Core source stack (branch Release/1.0) to debug through the error. However, the error didn't occur and the content items were correctly updated and saved.
This seems to indicate to me that the NuGet packages that my application has are out of sync with the release version of Orchard Core but they all have the 1.0.0 version number.
It should be noted that my application adds nothing to the edit process of content items, just display drivers and templates. The errors occur in standard Orchard Admin updating content items.
So my endgame question is, how to I get my NuGet packages (currently with some unfixed error) to match up with Release/1.0 (where the error has been corrected)?
Beta Was this translation helpful? Give feedback.
All reactions