Posted by Alan D. on October 15, 2009 at 4:24am
Jump to:
| Project: | Node As Block |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I just tried the dev version and I got way too many errors to consider this for a live site that I was developing. So I stripped this down to its bare bones and extended the functionality slightly. I thought that I would share as it may guide you away from trying to mimic the block.module within the nodeapi hook.
I'm a real believer if the KISS principle!
| Attachment | Size |
|---|---|
| snb.zip | 3.71 KB |
Comments
#1
PS: I renamed it to snb or "Simple node block" to keep a clean namespace. I have no intentions of maintaining / releasing this as a seperate module as it is a 90% overlap with this project!!
#2
I installed the dev version a while ago and it works like a charm
perhaps an other installed module was at fault ??
#3
No, the issues were simply due to the module trying to mimic the block functinality inside the node form. There were at least 3 different issues, all stacked one on top of each other, all related to the direct integration of the module with the block system. It was that latest dev version :)
Anyway, all of I was looking for was a node for a block, with minimal configuration options at the node level. This was one of the three node block modules that provided that, but a stripped down version was all that I needed. I guess that was what the early module provided, and was probably bug-free c/f the dev version. This was a push to say that less is more sometimes!
#4
Love to get the maintainers opinion on this before closing. But it is probably a bad to ask. Hoping the storm didn't effect you or your family too much.
#5
It'd also be helpful if you could identify the bugs you ran into independently so we could try to address them as well.
#6
About half of the issue queue issues that were related to block settings. :)
I'm a big fan of KISS, so duplicating this functionality in my book is a big no-no!
#7
PS: Remember that this was a year ago, so I do not know what the current status is like at the moment. I'm just trying to clean up my old open issues, either bumping them or closing when possible.
#8
I agree with you about keeping things simple, but the reason I came back to this module was because a few projects we were working on have some needs that include being able to set some of the block table values from the node form.
I've done some work to clean up some of these bugs, some of which I've posted to patches here and some of which I haven't had the time to contribute as patches just yet. Dropcube is currently working with the d.o. webmasters to get the project ownership changed to himself so he can add additional maintainers and some of these issues can be cleaned up.
If each of these bugs can be provided with solid reproducible steps, perhaps we can address them without throwing the baby out with the bathwater?
#9
Sounds great. Closing then :)