This came up as (sort of) an issue in the recently solved #2056143: Nodeblock title not updated when node title is changed.. And let me explain what I mean by "sort of":

While troubleshooting that issue (before it got fixed), I have tried setting the "Overrides per node: Block title" feature for the effected nodeblock-enabled content types to be overridable (just to try if that possibly solved things). I then completely forgot about that. When I initially went ahead to test the issue in order to confirm if it was actually fixed:

- downloaded and installed latest dev that included the fix for #2056143: Nodeblock title not updated when node title is changed.,
- edited one of the effected nodes and changed its title,
- hit the save button (and prayed)...
- WTF?!? The block title was still not updated. "Oh no!" I thought for a second...
- "Hang on..." ...edit the node again,
- "Aaah!" ...there's the "Provide a block title" checkbox (disabled by default). Lets try that then...
- MAGIC!!!

So, my point is this: for my use cases, I find the default being unchecked a really bad UX experience because then I either:

- need to not expose this setting to the users at all
- have to teach my content editors to always remember to also check this checkbox if they want to also change the block title.

Now, we all know that content editors will probably never remember that or they'll forget about it at some point. The next thing will be getting complaints about the block title not being updated. Besides, I personally find it simply silly to edit a nodeblock-enabled node, change its title and not wanting to also reflect that change to the actual block itself. If one wished to achieve such behavior, then they could as well set the block title to something "static" in the block settings. The point of this module after all is to enable end users to edit "blocks" (actually nodeblock-enabled nodes) without actually having any block edit related permission and when doing so, they need to be able to also change the "block" title.

Anyways, unless there exist perfectly valid use cases that have not yet crossed my mind where one would indeed require this kind of behavior, then I believe that this checkbox should default to checked instead of unchecked. I'm merely suggesting that it simply makes sense that if one edits a "block" title, then they must want to see that change actually happen. If they did not mean to change the title in the first place, then they might as well leave it alone when editing the node. Right?

Anyways, the feature is inconsistent as it is now:

- If the feature is not set to be overridable, then the changes in the node title are reflected to the block title as well (defaults to on)
- if the feature is set to be overridable, then any change in the node title does not update the block title unless the user explicitly selects to "Provide a block title" (defaults to off)

...we should choose one and stick to it: either on or off for both cases (setting exposed to the users or not). I personally favor to default to on for all the reasons I mentioned above.

Comments

Johnny vd Laar’s picture

Category: bug » feature

I don't consider this to be a bug. If you do not use the block title option then it uses the node title. If you do use the block title option then it gives you a checkbox. If you leave it disabled then it uses the node title, if you enable it then you can override.

I think most users just want to use the node title so I think this is a sensible default.

I think that giving a setting where you can set it to enabled, disabled or "enabled and checked as default" can be possible. But this is a feature request.

klonos’s picture

I would really appreciate it if there was a setting to define the default expected behavior. So, a feature request it is then ;)