The "block settings" link for microcontents blocks redirects the user to the node edit form.
This stops the ability to configure the block's visibility settings, which makes this a bug IMO
(for instance, show mission only on front page)
The "block settings" link for microcontents blocks redirects the user to the node edit form.
This stops the ability to configure the block's visibility settings, which makes this a bug IMO
(for instance, show mission only on front page)
Comments
Comment #1
Bèr Kessels commentedCorrect.
We need to distinguish the following very clear:
* permissions. a main aim of MCC (microcontent) is to allow users without full admin perms to still edit texts
* configuration (administration, php for visibility, changing of filter formats etc), moderation (on/off/placement), editing (change contents).
The redirect is done intentionally: hook_block did (not sure if that changed) have a hook to catch updates, hence we could not update the node, if the block was edited. This needs to be checked first.
Comment #2
Bèr Kessels commentedFixed in HEAD.
Comment #3
Bèr Kessels commentedComment #4
(not verified) commented