Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I'm not quite sure how this feature is supposed to work, but it appears to be broken. If I configure a context to include "add custom box" in some region as part of the blocks reaction, it adds an "Add custom box" form to that region in that context, as expected. If I edit the block and submit the form, the custom box appears--but only for the duration of that page load. If I reload the page, or navigate to a different page in the same context, the block disappears and instead I see the "Add custom box" form again.
Furthermore, even anonymous users see the "Add custom box" form. There do not seem to be any configurable permissions.
Comments
Comment #1
xjmOh. It seems that the boxes are created, but not added to the context. (So I now have a zillion "test" boxes...)
Is this the intended behavior?
In any case, the form being visible to unprivileged users is certainly not desirable.
Comment #2
jmiccolis commentedYou're not using this as it was intended, so no this isn't the intended behavior. ...the fact that you can do it is something of a bug, that I think we should address.
The "Add custom box" block is only intended to be used from the "inline" editor (Which you see if you've got Admin & jQuery Ui modules enabled). To add a box which you can then use in the context editor you'll want to got to 'admin/build/blocks' and there should be a tab that says 'add box'. That will create a box you can use in the standard editor.
Of course if you create blocks using the inline method you can manipulate them in the normal editor, but really why would you?
Comment #3
xjmAh! I see how it's supposed to work now. When I use the feature with the inline interface, the block is properly added. Thanks for your prompt followup.