menu blocks is gone after saving an existing context

I was not able to reproduce this. Are you still having this problem?

same problem, using patched zen/zen 960 gs with D6

So just trying to really understand, are you saying that you:

1) Create context
2) Add a block reaction
3) Add a menu block from the system module (like Main Menu) to a region
4) Save the context
5) When you go to edit it again the menu block is not there

Is that how to reproduce this?

This seems to be a browser issue, upgrade to firefox 3.6 and all is OK? reports of IE woes too

Thanks.

Still having trouble reproducing this one in the latest dev codebase. I've tried the steps listed in #7 using both the main menu block provided by the system module and with a block provided by creating a test menu. Tested using FF 4.0

I'm having a similar issue, but I believe the cause is something about the block_menu module, not regular menu blocks provided by drupal.

I've been trying to resolve it myself, and here's what I've come up with:
When you edit the context with the inline editor and expand 'blocks', then select 'menu block', the menu blocks (again, this is just blocks provided by the menu_block module) that should be a part of the context are shown in that list - normally blocks that are already active on the page don't show up there, I think. The menu_blocks in the context are shown grayed out on the page, as if they were provided by a different context on the same page. If you drag a menu_block to the page, you can have two of the same block - the grayed out one, and the one you just added. Then when you save, the grayed out one goes away when the page reloads. This also affects blocks in other contexts. For example, we use a menu_block as a footer sitemap in a "global" context, and we have a menu_block subnavigation in a "node" context. On any page where node and global both trigger, editing either context with the inline editor causes the footer and subnavigation to vanish (unless you use the inline editor to pre-emptively re-add the blocks).

I'll post more information as I'm able, or a patch if I find a solution.

I had the same problem. I've just submitted a patch to fix it:
http://drupal.org/node/996426#comment-5144338

I have exactly the same problem. If you need more info, please react.
Using 7.x-3.0-beta2+12-dev
With
Context inline editor 7.x-1.0-beta1
And
Menu Block 7.x-2.3

I've had the same exact problem with nodeblocks and haven't been able to solve it. It appeared shortly after a recent update. Here's what I'm running:
--Drupal is 7.14
--Context module is 7.x-3.0-beta3 for Context, Context Layouts and Context UI.
--It's 7.x-3.1-beta2 for Context: Menu Block.
Also, server has PHP 5.2.5. Anyone think that could be the problem?
I would be ecstatic if someone solved this. I have searched for a solution for over a month, and been unsuccessful. If no one can provide assistance here, I'll have do a rebuild to get things working. Of course, I'd rather not have to reinvent the wheel so any and all help is GREATLY appreciated.

After some digging I believe the problem is in the generation of the editable block. Context UI uses an anchor tag with a particular ID to help the interface know which blocks belong to which contexts. For menu blocks this anchor tag was not being added because the editable block code felt that the block was empty.

Attached is a patch that resolves that issue and adds a warning should another block come along that is likely to be dropped from the context when using the inline editor. Please give it a try and let me know if it resolves the issues for you.

Adding tag for tracking

Haven't been able to try this yet but appreciate your help. Will let you know if it works. Tx!

It works!!

Patch committed: 49310cb02202455106f5ae948d18263c14f6d2a8 will be in the next dev build and version after beta4