D7 port causing issues while creating new content

Same for me.

I think I manage to fix this issue.

Sorry for not displaying a patch but I'm not used to work with GIT for the moment so I will only explain the changes I've made.

In node_level_blocks.admin.inc around line 100, replace this :

// If a node is submitted with the 'preview' button,
// the data can be collected using the form state.
// Othewise the stored nodes, or default values can be used.
if ($form_state['submitted']) {
    $node_blocks = array();
    $settings = $form_state['values']['node_level_blocks']['blocks']['settings'];
    unset($form_state['values']['node_level_blocks']['blocks']['settings']);
    foreach ($form_state['values']['node_level_blocks']['blocks'] as $node_block) {
      $node_blocks[$node_block['bid']] = (object) $node_block;
    }
}
else {
    if(isset($form['#node']->node_level_blocks['settings'])) {
		$settings = $form['#node']->node_level_blocks['settings'];
		$node_blocks = $form['#node']->node_level_blocks['blocks'];
    }
}

By this :

// If a node is submitted with the 'preview' button,
// the data can be collected using the form state.
// Othewise the stored nodes, or default values can be used.
if ($form_state['submitted']) {
   $node_blocks = array();
	if(isset($form_state['values']['node_level_blocks']['blocks']['settings'])) {
		$settings = $form_state['values']['node_level_blocks']['blocks']['settings'];
		unset($form_state['values']['node_level_blocks']['blocks']['settings']);
	}
	else {
		$settings = node_level_blocks_node_type_settings($form['#node']->type);
	}
	
	foreach ($form_state['values']['node_level_blocks']['blocks'] as $node_block) {
	  $node_blocks[$node_block['bid']] = (object) $node_block;
	}
}
else {
	  if(isset($form['#node']->node_level_blocks['settings'])) {
		$settings = $form['#node']->node_level_blocks['settings'];
		$node_blocks = $form['#node']->node_level_blocks['blocks'];
	  }
	  else {
		  $settings = node_level_blocks_node_type_settings($form['#node']->type);
	  }
}

Seems to works for me. If anyone can confirm...

Hi Dexter0015, thanks for your help, ran into the same problem.

I have rewritten your code to eliminate some else statements and I have attached a patch for this issue, maybe the maintainers could review it?

  // set default settings
  $settings = isset($form['#node']->node_level_blocks['settings']) ? $form['#node']->node_level_blocks['settings'] : node_level_blocks_node_type_settings($form['#node']->type);
  $node_blocks = isset($form['#node']->node_level_blocks['blocks']) ? $form['#node']->node_level_blocks['blocks'] : array();
  
  // If a node is submitted with the 'preview' button,
  // the data can be collected using the form state.
  // Othewise the stored nodes, or default values can be used.
  if ($form_state['submitted']) {
    $node_blocks = array();
    $settings = $form_state['values']['node_level_blocks']['blocks']['settings'];
    unset($form_state['values']['node_level_blocks']['blocks']['settings']);
    foreach ($form_state['values']['node_level_blocks']['blocks'] as $node_block) {
      $node_blocks[$node_block['bid']] = (object) $node_block;
    }
  }

Thanks.

Unfortunatly I wasn't able to apply your patch, git returns me the following error:

error: while searching for:
    // set default theme for retrieving regions and blocks
    $theme_key = variable_get('theme_default', 'garland');

    // If a node is submitted with the 'preview' button,
    // the data can be collected using the form state.
    // Othewise the stored nodes, or default values can be used.

error: pathc_failed: node_level_block.admin.inc:89
error: node_level_blocks.admin.inc patch does not apply

I guess where is a difference between our line numbering, don't know why.

So I apply your change myself and make a new patch (just in case).
I finally tried git ;)

Weird, I made the patch with the git repo, as the Drupal guide for creating patching describes.

Have you also tried?
patch -p1 < node_level_blocks-1747994-2.patch

Thanks.

You're right !

with :
patch -p1 < [patchname.patch]

your patch is correctly applied.

I was using :
git apply -v [patchname.patch]

as described in the drupal guide, and get the error previously mentionned.

Sorry, but I didn't know "patch -p" command (as I'm just starting using git...).

Could you tell me what is the difference between this 2 commands?

Hi, the difference (http://drupal.org/node/60108)

Note: git apply will fail to do anything when used within a local checkout of a git repository (other than the one for the project the patch is made for), such as if you are patching a module that is within a site that is in Git version control. Use patch -p1 < path/file.patch instead. You can find more info about applying patches with Git in the Git handbook

Thanks !

These changes are committed

Thanks !

Unfortunately, I still have some error messages when I save a node without blocks affected.

In edit form only, creation form seems to be ok for me.

Can you provide me the error messages?

Sorry,

This one appears on the top of the list :

Notice : Undefined index: settings dans node_level_blocks_block_list_alter() (ligne 140 dans /.../modules/node_level_blocks/node_level_blocks.module).

Then, this one appears several times :

Notice : Trying to get property of non-object dans overlay_block_list_alter() (ligne 440 dans /.../modules/overlay/overlay.module).

It seems to be related to the overlay (I guess) because if I edit a node without using overlay, I don't get any error...

okay that makes sense as I never use overlay ;-)

I will investigate.

I have committed a fix for this problem. Please review and reopen if needed.

I've updated my files from your last commit, but still have the same error messages.

Plus Drupal.org added this to the .info where Module's version is wrong :

; Information added by drupal.org packaging script on 2011-08-11
version = "6.x-1.4"
core = 7.x

Hmm worked for me. I'll investigate again.

The info file still contained old code. I'll fix that too.

Committed a fix for the info file but I can't seem to find any bugs in the node save now, using overlay. Can you verify if the bug still exists with the latest dev version?

Ok, I've updated from the last dev version and installed it on a new drupal installation (7.19).
And...

I can't reproduce the bug. (so i apologize)

Maybe it's a conflict with on of the other modules I have on the website where I have the bug.

Anyway, thank you so much for taking the time to look for, and sorry for wasting of your time...

And I really thinking about stopping using the overlay as it seems to be really heavy and slow sometimes.

I found another bug in nlb with overlay that I just patched that added blocks to region -1.

I think you found the solution because I've just test your last commit and I don't have anymore error.

Thank you!