programatic migrations and cached backoffice views...
# package-development
m
Having an issue with a programmatic contentType update as part of a packageMigration.. simply using
_contentTypeService.Save(generalSettingsContentType);
to update a description/validation on a property. However, if you visit a node of that contentType it's showing the old information, visiting the
settings/generalSettingsContentType
the doctype description are all correct.. and hitting save in the backoffice for the doctype then gives the correct render for the nodes in question.. Has anyone come across this and knows of a cache that can be cleared, or other workaround?
Seems like re-actioning the contentType save in a
MigrationPlansExecutedNotification
does the trick.