Block edit mode

Permalink
Version: latest (5.7.5.6)
Scenario: If I enter Edit mode, go to a block, do a left-click and then mistakenly choose for example Edit layout design instead of Edit container layout -- after I click either Cancel or Save, that block will cease to be editable, ie. no green lines around it and option to edit while other blocks remain editable.

This may be related to blocks within a layout only and may also be true in situations when one edits the block and saves the changes, but at some later point (for example, after editing another block) decides to go back to that initial block to edit it again.

I think a block should be editable at any time, instead of having to Publish changes first, then re-enter edit mode.

 
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi developer10,

I was unable to recreate your issue following the steps you listed.

What version of concrete5 are you using?

Do you have any errors in your browser console when a block is not editable?

Are you using a custom theme and/or custom blocks?
java9 replied on at Permalink Reply
Hi,

Concrete version is 5.7.5.6
In console, there's nothing except this (and it has yellow icon, not red: Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, checkhttp://xhr.spec.whatwg.org/.)

Now, try to recreate by following these additional details:

In my particular case, it's homepage of the Elemental theme (it's moved under application so you can consider it custom, I guess).

So the bottom part of the homepage there's a row (3 column layout) where the right column has a heading (We specialize in making your concepts a reality.).
Now go ahead and empty the first two columns (image and text) then publish.
Go back to edit mode, click on any of the two empty columns and go for Edit layout design, then simply Cancel. You should not be able to enter that block's edit mode because it now appears completely static (no green outline).
MrKDilkington replied on at Permalink Reply
MrKDilkington
@developer10

Your second situation also works correctly.

Can you take a few screenshots of what it looks like when it doesn't work, please.