Allow Default region: None

Where does it say "Select allowed regions for these blocks" ... ?

When editing a node, under "Provide a block" i get in "Region:" only "".

Then, when visiting a blocks admin page, i get the message:

"The block . was assigned to the invalid region -1 and has been disabled."

And I can't get it to display anywhere...

Help!

I have got the same issue 2 years later yikes

I have the same problem too....Under Provide as Block is says 'assign to region' and the only available option is 'none' ..... it seems the regions of my theme are not being recognized...at first i ignored it and set the region on the blocks page instead but whenever i revisit the blocks page the nodeasblock blocks get bumped out of their regions with the error message "The block . was assigned to the invalid region -1 and has been disabled."

Exact same problem here - none of the regions show up under 'Provide as Block' and every time the node is edited, it disables the block.

After creating a new Node As Block there will be displayed an error message, that block is deactivated.
You can set a valid Region at admin/build/block manually. After every editing of node you will have to repeat this again, because node cannot read out and store the chosen valid region.

Do you have the regions set in the content type? each content type with node as block needs the regions selected to make them available when you create and edit the content of that type

Having exactly the same issue with this module.

I first added a new region in the info-file, made the necessary modifications in page.tpl.php and then made a new content type, with "Create blocks from this content type" set on "Always".

The first time I created content with this fresh made content type, it displays the new node with no remarks. I had to put the new block in its proper region through Admin > Build > Block, I didn't make a deal of it. But when editing the node it says "The block (name) was assigned to the invalid region, and has been disabled." indeed.

Eventually I decided to start making this content type from scratch again, with the same Node as Block-settings, with no result! Eventhough this doesn't happen with other (node as block-) content types having the same settings. I really don't get it. The alarming thing about this is that it disables àll the nodes of this content type after you just edited only one of them. At least: it gives that as a notice, but when I check my frontpage, where they are applied, they're still there. This region is on a custom page.tpl.php (page-front.tpl.php). Eitherway, it doesn't bother me, but I can imagine it can really alarm customers.

Is this module vulnerable to changes in the info-file from the moment it's being installed?

I am also having these warning messages. Is there any way to fix this?

Please check #478376: Save to Default Theme rather than Currently Active Theme, I have committed a fix for that issue that is related to this one. Thansk.

Tried last version, still not working for me.

My theme is a subtheme based on zen. I had about 10 blocks created by nodeasblock and the warning message was huge. Only solutions is going to blocks configuration choose Garland and simple "save" the configuration. Once Garland reassigns all modules to disabled then back to my working theme the warning is gone. But the patch has made no difference.

Thanks.