Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Installing SilverStripe /

Getting SilverStripe up and running on your computer and on your web server.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Configurable requireDefaultRecords

Go to End

2 Posts   2664 Views


Community Member, 11 Posts

3 December 2009 at 11:58pm

We have developed a couple of sites on the SilverStripe CMS and have developed quite a few modules where we need to populate the database with default records.

Most of the sites we are setting up are migrations of existing sites, where we don't want to create the default SiteTree and error page records defined in SiteTree::requireDefaultRecords and ErrorPage::requireDefaultRecords. We can specify dont_populate=1 either in sake or through the web dev/build?dont_populate=1, but that suppresses all default record creation.

Is there any way to configure the population, or does anyone have an idea on how to solve this problem?

Can I for example do a dev/build?target=<DataObjectName> in order to build a specific table?

I made an effort to solve this through decorators ( ), but that was not well perceived, and I agree with ajshort that it might be overkill.


Community Member, 541 Posts

9 December 2009 at 11:24pm

I would love to know an answer to this too. I would really like to suppress the default records for SiteTree so I create my own site structure, either under Page::requireDefaultRecords or possibly as a build task (although these might not support this, haven't tried yet).