Part bug report, part support request.
I found no matter what block I made an instance for, I would get the not multiblock enabled red icon, even testing simple modules for which it worked. What does that status mean? It makes it hard to determine if a block will work or debug one that doesn't.

I wanted to use it on a block created with nodesinblock

From what I understood of the docs, is it true that another contributed module that is incompatible would need to be made "multiblock enabled" within that module's code. I want to know if I am missing something before giving up on being able to use multiblock with nodesinblock created blocks.

Comments

andrewlevine’s picture

andrewlevine commented
Status: Active » Closed (fixed)

The red icon does look too scary for what it means. It means there is no code written for the block in question to support multiblock.

This is fine most of the time, except when the block has custom (non-core) settings that you want to be different for each multiblock instance. If this is the case (it looks like it is with nodesinblock) then the block will need code written to be multiblock-enabled.

You might be better off with nodeblock+multiblock because nodeblock is written in a way that it doesn't have to be multiblock enabled (it creates an extra block per node).

echoz’s picture

echoz commented

Thanks for the clarification on the icon. I did see that I could use nodeblock but have been so happy with nodesinblock because it doesn't create a separate block for each node.