Hello everyone! I'm currently in the process of setting up several test pages in Silverstripe and seem to have encountered a problem where the CMS itself is picking up a style that's intended for a particular page on my site. My _config.php is as follows (I think this is pretty well the default):
$project = 'mysite';
$databaseConfig = array(
"type" => "MySQLDatabase",
"server" => "xxx.xxx.xxx.xxx",
"username" => "xxxxxxxxx",
"password" => "xxxxxxxxx",
"database" => "xxxxxxxxx",
// Sites running on the following servers will be
// run in development mode. See
// for a description of what dev mode does.
// This line set's the current theme. More themes can be
// downloaded from http://www.silverstripe.com/themes/
When I just had a blackcandy subfolder in the themes folder then everything worked well. However, I created a page called (rather unimaginatively) test and created a subfolder called blackcandy_test in the themes folder so that I could specialise the theme specifically for the test page.
Unfortunately, when I logged out of Silverstripe and went back to its login page, the CMS itself seemed to be using the blackcandy_test theme rather than the original blackcandy. If I delete the blackcandy_test subfolder then the CMS reverts to the blackcandy theme. I've tried clearing my browser cache and the Silverstripe cache so I don't think it's caching confusion.
Have I misunderstood how theme specialisation works or have I just made a silly mistake somewhere? Any help would be greatly appreciated! Thanks!