The Blog module now uses Lumberjack. I extended Blog and BlogHolder to create a News section, but I also still have an actual blog, so I'm using both classes.

On the News page, I have a nice green "Add News Item" button, but on the Blog page, I have a dropdown for BlogPost and NewsItem, and then a "Create new" button. I understand why this happens; it's showing all possible children types; but I only want 'basic' BlogPosts there, not its extensions.

Is there a way to (easily) force this? At least, the following does not help (does not seem to be picked up, whether I make it empty or ['BlogPost']):

<?php
class BlogExtension extends DataExtension {
    private static $allowed_children = [];
}

One way to solve it is to create another new class that extends Blog and set its own allowed_children (MyBlog or something); that is the only solution I have found so far. I feel like it would make sense if this was possible with an Extension though, so I created an issue on github.

I eventually got a real solution thanks to the comments on the Github issue:
* use Config::inst()->remove and ->update in php
* write "*BlogPost" (including the asterisk) to indicate that only BlogPost and not classes extending it should be allowed

This is my effective result:

Config::inst()->remove('Blog', 'allowed_children');
Config::inst()->update('Blog', 'allowed_children', ['cwsFolderGalleryPage', '*BlogPost']);