Block installs itself in 'other'Browser Info Environment
I have a testsite where I've created a block and I set it to be part of the 'Basic' block type set.
But on the live version of this site (which is a SVN checkout of the same repository) the block installed itself as part of the 'Other' block type.
Why is that?
How can we set this block to be part of the 'Basic' set?
NB: Our testsite has Blockdesigner as a package, but our Live site doesn't, because we don't want customers to be able to change blocks.
Under the "Interface" tab upon creating a block within Block Designer, you see a "Default block type set" field. In there, you can enter the handle of the set it should install into. By default, everything will go into "Other" if you don't enter anything in there. If you want to have them in "basics", you enter that in there. Because other Add-Ons can make block type sets and you can do too, it's not a "simple select".
You can also open up your controller.php file of the Block Type and look for this:
protected $btDefaultSet = 'your_set';
If the variable ($btDefaultSet) does not exist, you can add it (and change 'your_set' to whatever handle your set has - 'basics' in your example).
but this may be a bug?: I made numerous multiple blocks in the testsite, and they all installed perfectly in the correct interface categories, no problem there.
The Live site has all those initial blocks in 'basic' just like I picked originally from within Blockdesigner.
But Now that I've added a new block, aftyer SVN version update, this one doesn't seem to get into the right place - perhaps because the Live site doesn't have Blockdesigner as a package?
There we added entries in the BlockTypeSetBlockTypes - and set their ID's to Basic (1) id.