Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
9 May 2011 at 14:21 UTC
Updated:
23 Jun 2011 at 16:33 UTC
Editable blocks allows site editors to update content published in a block without exposing access to block administration.
This module is similar to the core Block module but with a set of permissions that only allow users to control the content of the block rather than the full control that the 'administer blocks' permission gives.
Previously the only way to achieve this was to create a node and load this into a block. This had undesirable consequences like adding the extra node to search engines.
Project page: http://drupal.org/sandbox/ltl/1151544
The code is in 6.x-1.x branch: git clone --branch 6.x-1.x http://git.drupal.org/sandbox/ltl/1151544.git editable_blocks
Comments
Comment #1
davidhernandezJust to be clear, this module provides a way for content editors to access custom blocks and change the content, without giving them access to the full block administration? This way they can't control the block, but can change its contents.
Comment #2
joachim commentedIf that's the case, a better name might be 'block access'?
Comment #3
joachim commentedHow does this module work? I've just taken a quick look at the code and it seems to be doing its own storage.
Does that mean you can't change a previously created block to an editable one? Is there a problem with using core's built-in custom blocks?
Comment #4
joachim commentedBTW, at first glance code looks clean and well formatted. Nice job :)
Comment #5
Jonathan Peterson commentedAs part of a discussion about http://drupal.org/node/1121112, the applicant wrote:
Closing as won't fix on his behalf.