Closed (fixed)
Project:
Node As Block
Version:
5.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Dec 2006 at 02:49 UTC
Updated:
9 Jun 2008 at 16:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
eaton commentedAdded the ability to control which node types can be made into blocks, made block-deletion automatic when a node is deleted, and cleaned up some of the form altering to match core modules like upload.
Comment #2
eaton commentedBut this one includes the correct patch. No, really! ;-)
Comment #3
newdru commentedIs there any way i can convince you to add one extra text field to be used as block content/text as an alternate to the standard node teaser?
Blocks that link to a full node often do NOT want to use a teaser from the target text but alternate text which can be tailored to fit the dimensions of the block, be short and descriptive headlines, etc. At least that seems more useable in 99% of the cases i would use blocks like these for. Others would probably like that option as well as it was mentioned in a feature request for this module.
I would imagine if you leave the text field blank, then by default you just use the teaser. It's the best of both worlds.
I'd implement this myself but i'm not quite up to speed yet on the drupal internals. In fact i feel pretty cheesey even asking you to do this but i've been to your website, know you do good work and that you could probably knock this out pretty quickly. Especially while this patch is still fresh in your mind.
anyway, i thought it couldn't hurt to ask..
thanks either way.
Comment #4
newdru commentedregarding my last post..
someone in another post in this queue mentioned that you could use the exerpt module to gain the functionality i requested in post#3. i didn't overlook that. it probably is a viable option. i just thought it would be a cleaner implementation to have all of the functionality contained in one module versus spread across many.
thanks again
Comment #5
mfredrickson commented@newdru: As you noted, there is a ticket for your request: http://drupal.org/node/98784
Feel free to comment over there. Let's keep this thread focused on the UI around block management and not what is in the block.
Thanks for your interest in NaB.
@eaton: Thanks for the patch. I'll try to get to it soon. :-)
Comment #6
alex_b commentedGREAT patch. nodeasblock was literarilly screaming for that one.
Do you have plans to integrate visibility settings on the nodeasblock page?
Alex
Comment #7
alex_b commentedsorry, should be *nodeasblock form snippet instead of *nodeasblock page
Comment #8
mfredrickson commentedI checked in Eaton's patch, and I added a checkbox for visibility.
Also, I didn't add the new perm, but just reused "administer blocks".
This feature will be in the Drupal 5 -- 1.1 release.
Thanks to everyone!
-Mark
Comment #9
(not verified) commentedComment #10
BioALIEN commentedI had to reopen this issue.
mfredrickson, the reason extra permissions were added is so that you can control what to show the users who have access to this module. If you are giving them access to administrate blocks (which is what you've done) then it defeats the whole purpose of having this module.
Isn't the idea to try and give functionality to some users while limiting the damage that can be caused by just allowing a full core block administration?
Right now, without giving administer blocks permissions, users can only see "Create a block for this node?" but nothing else. Please include the additional permissions as per the Eaton's patch so an admin can delegate some of this functionality to the users.
Comment #11
alex_b commentedI just wanted to post a heads-up here: Jose Reyero is working on a patch to include specific visibility settings on the node edit form. The aim is to be able to control block settings entirely from the node edit form without having to go to the admin/blocks page.
A patch will be up on a seperate issue. We are very close :)
Comment #12
alex_b commentedJose and me tried to complete the approach started by the patch on this queue. Check it out here: http://drupal.org/node/133452
Comment #13
dropcube commentedComment #14
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.