Hello world,
just to let you know that we branched Drupal core. There is now a
DRUPAL-5 branch that will be maintained by Neil Drumm, with help from
Steven and me. (http://buytaert.net/neil-drumm)
This also means that CVS HEAD is open for development again, and that
- after a long code freeze - we can finally start working on Drupal
6. Yay! (I'm going to create a new thread to discuss Drupal 6 later
this week.)
I haven't assigned a Drupal 6 core maintainer yet. A new core
maintainer is not a requirement, but I'll probably assign one in a
couple of weeks, once we're a little bit further down the road.
Rock on,
--
Dries Buytaert :: http://www.buytaert.net/
Reference this issue, although I did not create the issue:
http://drupal.org/node/87074
Greetings all :) Nice work on Version 5!
I recently had to make a Drupal 4.6 site connect to a MySQL and a
PostgreSQL database at the same time. Of course, this isn't possible
with the current implementation of database*.inc since the same
functions are redefined in each inc file.
I'd like to update my patch for HEAD and hopefully get this feature
accepted for the next release.
What I actually implemented was two separate features that can be
split into different patches for consideration.
1. Allow connections to multiple different types of database servers.
2. Allow different table prefixes for each database connection.
Hopefully others think this is a useful feature? :)
Again, the issue I'm referring to on Drupal.org is http://drupal.org/node/87074
Thanks,
-Rowan
Hi everyone,
I took over the development of the invite module a while back because I
needed to work on it and it seemed abandoned. Unfortuately I no longer
have time to even answer the issues let alone code for them so the
module really needs a new owner.
If none come forward, I would appreciate the nodes ownership being
changed anyway.
Many thanks, and apologies that I cannot help further on this module!
--
Nick Wilson
Bio/Blog: http://communicontent.com/user/nick-wilson
LinkedIn: http://www.linkedin.com/in/nickwilson
Hi there - I'm working on a system to change the appearance of comments
based on how people rate them. So highly rated comments would appear
bigger and brighter than badly-rated comments.
The voting API abstracts away the rating mechanism nicely (so in theory
you could pick any voting module to drive the ratings system).
But I'm not 100% sure of the best way to apply different looks to
differently rated comments.
My current thinking is that it'll have to be pretty tied to a theme -
I'd pass some sort of rating metric into comment.tpl.php as an extra
parameter and the template applies an appropriate style (probably one of
a range of styles defined in a stylesheet).
Does this sound like a sane way to do it?
Does anyone have any suggestions of approaches I could take to
generalise it a little? It'd be nice to decouple it from the theming as
much as possible so others can take advantage of it.
Thanks!
Ben.
Hello,
Congratulations to those who worked very hard towards the release of Drupal 5!
I would like to propose that this patch becomes one of the very first to be
committed during the Drupal 6 development cycle:
http://drupal.org/node/109765
yours,
Augustin.
--
http://www.wechange.org/
Because we and the world need to change.
http://www.reuniting.info/
Intimate Relationships, peace and harmony in the couple.
Hi,
i would like to propose a patch to 6-x which will add an option to store
IP address of comment author to the comment. I am looking for this
feature quite some time now and i think that due to spam, IP address is
very valuable resource when fighting it.
The only option how to accomplish this now is finding that IP in
watchdog log, but it is deleted every X days...
Is it worth developing? (Is there a chance to be accepted?)
Thanks,
Jakub
http://www.drupal.cz
Hello,
congratulations for releasing 5.0. It is really a revolutionary release. :)
I'll get to the point.
CHX told me it's time to remind you that there's a SQLite database
interface sitting in the issue queue (http://drupal.org/node/67349)
The patch hasn't been updated yet due to lack of time (I am in the
middle of end term exams), but it will be in a matter of weeks. I will
also send a reminder on this list at that time.
I also wanted to point out that if this gets into core, I am willing
to be the maintainer of the port.
Regards
Tadej
Derek and all.
Would there be an easy way to track module releases?
Perhaps an RSS feed on drupal.org only for release nodes only?
That should do the trick.
Any better ideas?
---------- Forwarded message ----------
From: Khalid B
Date: Jan 15, 2007 1:17 PM
Subject: Re: [consulting] casetracker 5.x-1.1 released
To: A list for Drupal consultants and Drupal service/hosting providers <
consulting(a)drupal.org>
On 1/15/07, Morbus Iff wrote:
>
>
> Are these sorts of updates important to consulting folk? I'm only
> continuing because I know a lot of folk here expressed interest in CT.
Yes, they are.
Which brings up the point of whether we should have a central place where
module releases are announced. Maybe a forum on Drupal.org just for
module releases (RSS goodness), or a dedicated mailing list?
