The attached patch allows users to control the region and weight of the block, and automatically enables the block when the nodeasblock record is created. Advanced visibility options must are still controlled on the blocks page.

The patch also adds a new access permission to control block spacing and visiblity.

Comments

eaton’s picture

StatusFileSize
new3.83 KB

Added 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.

eaton’s picture

StatusFileSize
new4.73 KB

But this one includes the correct patch. No, really! ;-)

newdru’s picture

Is 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.

newdru’s picture

regarding 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

mfredrickson’s picture

@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. :-)

alex_b’s picture

GREAT patch. nodeasblock was literarilly screaming for that one.

Do you have plans to integrate visibility settings on the nodeasblock page?

Alex

alex_b’s picture

sorry, should be *nodeasblock form snippet instead of *nodeasblock page

mfredrickson’s picture

Status: Needs review » Fixed

I 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

Anonymous’s picture

Status: Fixed » Closed (fixed)
BioALIEN’s picture

Status: Closed (fixed) » Needs work

I 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.

alex_b’s picture

I 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 :)

alex_b’s picture

Jose and me tried to complete the approach started by the patch on this queue. Check it out here: http://drupal.org/node/133452

dropcube’s picture

Version: master » 5.x-1.1
Status: Needs work » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.