Opticon Stockholm is on Tuesday September 10th, hope to see you there!
Opticon Stockholm is on Tuesday September 10th, hope to see you there!
Hello Eric,
Are you versioning your DLLs? This can affect whether Optimizely CMS will update it's models.
e.g.
Lets say you have your DLLs versioned at 1.2.0 when the database is updated with the latest content models. If you then try to update the content models where your dll is versioned at 1.0.0, then Optimizely will prefer the 1.2.0 version of the content model.
You can read more about model synchronization and dll versions here: Synchronization (optimizely.com)
I have a related question. Would these settings stop the newly created content type models or changes to the content type from happening? The other new thing I noticed in CMS12 is that I now have a button on the Content Type page that allows me the create new content types and adds a GUID.
services.Configure<ContentModelOptions>(o =>
{
o.EnableModelSyncCommit = false; //https://docs.developers.optimizely.com/content-management-system/docs/synchronization
o.EnableSemanticVersioning = false; //https://docs.developers.optimizely.com/content-management-system/v1.7.0-content-definitions-api/docs/semantic-versioning
});
Yes, content types are not synchronized from code if this flag is false including creating new content type, updating content type, updating properties, adding properties, deleting content type or properties
o.EnableModelSyncCommit = false;
We have an issue where new pages (ContentTypes) are not found. This is in our DEV domain running IIS Express. My best guess is that maybe the assemblies are not getting scanned even though we have "forceBinFolderScan": true in appsetting.json.