Active
Project:
Node As Block
Version:
6.x-1.0-beta1
Component:
Documentation
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
15 Sep 2009 at 09:22 UTC
Updated:
27 Feb 2014 at 14:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
brad.bulger commentedi was having this problem as well, and then figured out that i had to go edit the content type - there is a "node as block settings" area there where you have to select all of the regions for your theme, in order to have any of them show up on the node edit form
Comment #2
webthingee commentedAny ideas if you are using an Admin Theme and the regions are not present when editing content?
Comment #3
brad.bulger commentedsomething like that is what was causing me trouble, but only because i was running my own scripts without setting up theme info properly. once i set the available regions in the content type, using Drupal normally does not mess with that, and the node editing form works fine.
Comment #4
arski commentedworks for me, I would mark it as a documentation issue.. also see #911090: Block 'Page specific visibility settings' wrapped in p-tags when node re-saved for possibly related issues as that started out as a duplicate.
Comment #5
esbenvb commentedThis patch fixes the problem. I think the roots of the issue is that the block module is broken in D6, it defines the BLOCK_REGION_NONE to -1 but only checks for empty() when checking the regions for the blocks.
Comment #6
esbenvb commentedComment #7
esbenvb commentedthis is the correct patch. sorry
Comment #8
esbenvb commentedSorry, i should go to sleep. This patch fixes it.