Hello,

I created a new block type using bean and added fields to it and set the display to default. I saved everything, emptied the cache and then went to my 'blocks' area to allocate my newly created bean block to a specific region. However, my bean block is nowhere to be seen. I watched a tutorial online:

http://www.youtube.com/watch?v=Eu1YNy-BNG8&feature=youtu.be

and the guy simply created his new block under 'block type' and then activated its visibility and region in the 'block' area.

Does anyone have an idea why mine is not registering in the blocks area?

Thank in advance.

M

Comments

lilbebel’s picture

I also wanted to add that I tried activating it through the context module but, once again, the bean block doesn't show up anywhere in order for it to be selected.

indytechcook’s picture

Status: Active » Fixed

The block type just adds the bundle not the actually block. You have to go to block/add to add an instance of a block type.

lilbebel’s picture

Ahh, I see. Thank you.

lilbebel’s picture

Hello,

So I followed the instructions given on how to make a Bean:

"Once a block type has been defined, one can make a bean (block entity) through the admin UI
Visit: /admin/content/blocks then click "+ Add Block"
Choose the type of block that you would like to create and use the form to create a new bean.
Block placement and configuration can be handled through the Blocks system or contribs that deal with block placement (ie: context, display suite et al)."

However, I can't any option is to choose a block type. I seem to only be able to create a normal block. I've attached screenshots of my admin interface to illustrate. Sorry if I'm being thick and just not seeing the obvious.

M

indytechcook’s picture

/admin/content/blocks then click "+ Add Block"

This is incorrect instructions. There is a Add Block link on the navigation menu or you can create a link to /block/add.

https://skitch.com/e-indytechcook/8hnbp/welcome-to-drupal-drupal

lilbebel’s picture

Got it. Thank you.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.