London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
Why dont you get a fresh database backup from production and restore it to your development db. Then you start define pagetypes. You are correct that you use the GUID property on the ContentType attribute. Ex;
[ContentType(DisplayName = "Startpage",
GUID = "9a269a35-e044-448a-9dbb-0e7085087489"
)]
[AvailablePageTypes(Include = new Type[] { typeof(StandardPageType) })]
public class StartPageType : BasePageData
{
}
Take a look at http://talk.alfnilsson.se/2013/03/08/creating-page-type-classes-from-page-types-in-episerver-cms-7/ that will make creating classes for existing page types
I just migrated from CMS 6 R2 to 7.1 and want to define the page types in code. Currently all page types are defined in the database only.
When I define a page type I need to connect it to the already defined page type in the database. I assume this is done by using the attribute ContentType.GUID. This would work well on our development site. But in test and production the GUID will differ. Any suggestions on the best approach for this problem?