Hi there... i really love your module!!!
are you going to port it drupal 6?
would be extremly cool!
greetings
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | nodeasblock.6x.patch | 11.73 KB | jhedstrom |
| #1 | nodeasblock.6x.patch | 4.28 KB | jhedstrom |
Hi there... i really love your module!!!
are you going to port it drupal 6?
would be extremly cool!
greetings
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | nodeasblock.6x.patch | 11.73 KB | jhedstrom |
| #1 | nodeasblock.6x.patch | 4.28 KB | jhedstrom |
Comments
Comment #1
jhedstromI was curious to try this module in a D6 install, as it seemed to mostly meet out needs. Attached is a patch against the 5.x dev branch (as this branch seemed to be more up to date than CVS head) to port the module to 6.x.
Comment #2
dropcube commented@mokkashock: Yes, I am fixing some minor points in the 5.x branch and then will merge with HEAD to start a port to 6.x compatibility.
@jhedstrom: I am working on the migration and will consider your patch... please, stay around for testing ;) Thank you.
Comment #3
dropcube commentedAlso note, for Drupal 6.x, the theme function that returns an array with the block subject and content is not a good solution. With the 6.x theme system, I suggest to use a separated template file for theming the block, instead of a theme function.
Comment #4
dropcube commentedI have merged back to cvs HEAD the most up to date development in preparation to the 6.x porting and will be using HEAD for the 6.x branch.
Comment #5
dropcube commented@jhedstrom: You should do the diff from within the module's root directory, when trying to apply your patch I get: files does not exists (nodeasblock/nodeasblock.info). Please re-roll the patch against HEAD.
Comment #6
jhedstromI've rerolled the patch against cvs HEAD, and done it from within the directory as requested.
Comment #7
jorditr commentedAny news on that port? I've just discovered that little module and it's fantastic to solve so many things on big sites. It could be a core feature in fact ;-)
Comment #8
jhedstromI'm using this (with the patch above) on several sites in 6.x and it works fine.
Comment #9
Renee S commentedThis works a treat for me, too.
And to theme this sucker, just create a block-nodeasblock.tpl.php as usual. Providing custom variables I'm not so sure about, because the _preprocess function doesn't work in 6.x, but I didn't need it anyway... :)
Comment #10
andygoneawol commentedI'm a newcomer to Drupal patching. I have been attempting to patch the module for 6.x, as it sounds as if it is just what I'm looking for. However, patch is failing.
I place the patch file in a directory containing the unzipped downloaded module files and then (under Cygwin on Windows XP) issue the command:
patch < nodeasblock.6x_0.patchResult is a bunch of errors like this:
patching file README.txt
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 18.
(etc ... all apparently fail)
I also tried the -p0 option (not sure if it's required) and checked that it wasn't a CRLF issue.
Am I doing something obviously wrong?
Comment #11
dropcube commentedI have committed a patch that ports the module to 6.x. and have created a nightly development snapshot so that you guys can test. Please, test and report bugs etc. in follow up issues. There are still some work to do and some other issues still pending I would like to include before an official release. The code for the 6.x-1.x serie is in the DRUPAL-6--1 branch.
Comment #12
dropcube commentedOk, the Development snapshots are published on the project page, you guys can download the 6.x-1.x-dev.tar.gz and report bugs/improvements in follow up issues.
Comment #13
rmassamiri commentedAny idea of why Webforms do not show up in this latest 6.x-1.x-dev release? Thanks.
Comment #14
Renee S commentedIt works great for me, dropcube.
Comment #15
rmassamiri commentedWhen I set the language to Language Neutral it worked. When it was on English it wasn't showing up. I'm not sure what's going on, but I was able to get it to work by doing this.
Comment #16
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.