I've set one content type to be block-enabled, but my block listing shows many prior blocks (e.g. those created with a related module called nodeasblocks) now created as nodeblocks.

Comments

RJL-dupe’s picture

RJL-dupe commented
Category: bug » support
Priority: Major » Normal

Just to expand my post: I'm guessing both modules share a content-type setting "use as block", so this module made blocks of another content type used by the node-as-block module. This turned out to be a real time saver in my situation, but it might not be for someone else - so I've changed this issue's category status from bug to support request and priority from major to normal. Again, I have no problem with the current approach, but it might be worth a discussion. By the way, thanks very much for this great module - It works much better for me than node-as-block.

Johnny vd Laar’s picture

Johnny vd Laar commented
Status: Active » Closed (works as designed)

All blocks of a content type will become nodeblocks so that is how this module works.