- Development - lists.drupal.org

shazamgallery: gallery on views for adoption
by Bèr Kessels 22 Jan '07

22 Jan '07

Hello, I just received a 5.x port for shazamgallery[1], eventhough I planned to let it rest. This shows that people are interested in that project. Therefore, I would like to hear if someone wants to take it over from me and keep it alive. What it is: A gallery featuring user-galleries, date-browsing, tag-brosing, random/latest Image blocks etc. It is actually not much more then a set of default-views tables. It depends on image.module for uplaods/nodehandling/thumbnail-generation. And on views, off course. What it can be used as: A development-quick-starter, a launchpad, or a ready-to go system for those who need advanced galleries, like user galleries, or galleries based on calendars, and so on. What it needs: Not much. Just keeping up with changes in views and image.module. And testing of contributed views tables. Anyone interested? please drop me a line, and give me your Drupal handle. Bèr [1] http://drupal.org/node/111623 -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl

1 0

Jaza's modules are up for adoption
by Jeremy Epstein 22 Jan '07

22 Jan '07

Hi all, As many of you know, I will soon (on 19th Feb, exactly 4 weeks from now) be embarking on a 12-month world trip. Once I leave, I will be on the move, and as far as Drupal stuff goes, I will be out of action. I am currently the primary (and the only) CVS maintainer of 4 contrib modules. 3 of them (the first 3 below) in particular are quite popular, and seriously need to be maintained in my absence. The 4th is not that popular (AFAIK), but if someone would like to continue maintaining it, I would be very grateful, and I doubt that it would be much work. Here are the 4 modules for which I am seeking a new maintainer: --- 1. Category <http://drupal.org/project/category> Status: upgraded to 5.x, and is reasonably stable, but has numerous outstanding bugs. Description: a very popular module. A very controversial module. Needs a lot of TLC. Needs a maintainer who is eager to get his/her feet wet. As well as bug fixing, has plenty of room for those willing to spend time developing new features, or improving existing features. Several people have been working the issue queue lately, and submitting a number of patches. You know who you are, and you're more than welcome to apply as the new module maintainer. 2. Active select <http://drupal.org/project/activeselect> Status: upgraded to 5.x (including porting of JS to jQuery), and is reasonably stable, but has some outstanding bugs. Description: provides a JS widget and an API that allows one select box to dynamically update other select boxes. The category module is the only module (AFAIK) that currently uses activeselect (category works better with activeselect, although it doesn't depend on it). Maintaining this module should be relatively easy, as it is a small and simple module, only needing occasional bug fixes. However, for those with big ideas, there is also some room for new features in this module. 3. Import / Export API <http://drupal.org/project/importexportapi> Status: 4.7 version only, is reasonably stable, and has some outstanding bugs. Description: this was my Summer of Code 2006 project. It's a massive module, and one that I managed to bring up to a stable and usable (and quite well-documented) level during SoC, but that I certainly wouldn't consider finished by any means. Needs a lot of TLC, and is seeking a maintainer who is prepared to give it all their love. In particular, needs to be upgraded to Drupal 5, needs serious UI improvement (the UI needs a lot more development, and ideally needs to be moved to a separate project), needs VERY serious performance improvement (currently the memory overhead makes dealing with large datasets quite hard - probably the underlying architecture needs serious improvement in order to fix this), and needs a number of new features (e.g. validation and error-reporting of import data, proper processing callbacks to handle special operations for various entities, etc). The amount of code is large, and the complexity is high. But it's all quite high-quality, and also quite well-documented, so this should make the module easier to grok. 4. DB Cron <http://drupal.org/project/dbcron> Status: 4.7 version only, is very stable, and has no outstanding issues. Description: a simple module that lets you run a set of SQL queries at regular intervals using cron. I wrote it for the category module demo site <http://category.greenash.net.au/demosite/>, to refresh the site's database every 2 hours. This is the module's main application, but I'm sure it has others. Apart from needing a Drupal 5 upgrade, this module requires very minimal maintenance (it currently has an empty issue queue). Anyone interested in having an easy little module under their belt, feel free to take it over. --- Anyone interested in taking over maintainership of any of the above 4 modules, please email me directly. If you can't see my email address (because you're reading this in the archives, rather than as an email, perhaps), then please use my contact form at <http://drupal.org/user/15277/contact>. Anyone interested in being a maintainer should have a Drupal contrib CVS account, and should have some experience with developing and/or maintaining Drupal modules (at minimum, should have submitted some patches to core or contrib). Experience with the above modules is not essential, but is desirable. I will be around, available, and active for the next 4 weeks. I am more than happy to get the new maintainers of my modules up to speed, as best I can in the short time that I have before I leave. I would also like to take this opportunity to thank everyone who has helped me with these modules over the past year, and to thank the whole Drupal community for just being awesome :P. I sincerely hope that this is NOT the end of my time as part of the Drupal community. In fact, I couldn't imagine my life without Drupal (the code, or the people). I am most definitely planning to return to Drupal development when I finish my world trip, although I understand that by appointing new maintainers, I am relinquishing primary control of my current modules forever. No doubt, by the time my trip is over, Drupal will be several versions ahead, and so much will have changed that I'll have to learn everything all over again. As long as Drupal hasn't switched to Java, I'm sure it will still be a codebase that I can love ;-). Also, for everyone who is going to DrupalCon SF in March, I'll be there (I've planned my trip around it), and I'm sure I'll see you there! Many thanks, Jeremy Epstein - GreenAsh www.greenash.net.au

4 3

Release critical bugs for January 21, 2007
by drupal-devel＠drupal.org 21 Jan '07

21 Jan '07

Article / bug reports 4.7 Beta/ CVS Errors assigned: msameer age: 43 weeks 2 days url: http://drupal.org/node/55533 CVS management/tracker / feature requests provide admin UI to set a release node's CVS tag to '' age: 5 weeks 2 days url: http://drupal.org/node/103427 enforce sequential release tags in xcvs-taginfo assigned: dww age: 12 weeks 5 days url: http://drupal.org/node/90968 Event / bug reports Event module needs to know about the new DST rules starting on March 11, 2007 age: 2 weeks 2 days url: http://drupal.org/node/107011 [php5, clone] end-start-ongoing attribute does not ripple through age: 16 weeks 5 days url: http://drupal.org/node/85972 Major timezone bug in event module age: 22 weeks 6 days url: http://drupal.org/node/78572 event_start not being set age: 34 weeks 2 days url: http://drupal.org/node/65609 Fatal Error After activating "Browse Scheduled Events" in modules age: 37 weeks 2 days url: http://drupal.org/node/61920 INSTALL.txt incorrect age: 39 weeks 6 days url: http://drupal.org/node/59019 event calendars off by day/not respecting timezones - fix? age: 42 weeks 5 days url: http://drupal.org/node/56189 Flexinode generates an error age: 43 weeks 4 days url: http://drupal.org/node/55135 Calendar subscribing not working age: 44 weeks 4 days url: http://drupal.org/node/54036 Problem Selecting Event by Type age: 45 weeks 4 days url: http://drupal.org/node/52883 Event start and end times not getting saved in database age: 1 year 5 weeks url: http://drupal.org/node/41300 Issues with list view for events age: 1 year 6 weeks url: http://drupal.org/node/39943 Database error keeps popping up age: 1 year 7 weeks url: http://drupal.org/node/39396 Date problem on calendar, off by GMT offset age: 1 year 7 weeks url: http://drupal.org/node/39193 Events module bugs adding and changeing events age: 1 year 7 weeks url: http://drupal.org/node/39016 gmdate() warnings on windows install assigned: Omar Abdel-Wahab age: 1 year 29 weeks url: http://drupal.org/node/26140 Event / support requests How to display small calendar on homepage? assigned: dada78 age: 5 days 17 hours url: http://drupal.org/node/109630 Help!!! Site Broken!! age: 2 weeks 1 day url: http://drupal.org/node/107239 Blank Page After Submit age: 40 weeks 20 hours url: http://drupal.org/node/58918 Can't Administer Event Module age: 1 year 2 weeks url: http://drupal.org/node/43509 displaying event start info in flexinode tabular view? age: 1 year 15 weeks url: http://drupal.org/node/33019 Event block missing content of many fields age: 1 year 17 weeks url: http://drupal.org/node/31532 Gallery / bug reports IE error using embed not error with none-embed... when navigation block on right age: 37 weeks 1 day url: http://drupal.org/node/62119 Gallery / support requests Gallery2 grants access without proper permission age: 3 weeks 4 days url: http://drupal.org/node/105418 import existing gallery2 user account age: 1 year 11 weeks url: http://drupal.org/node/35920 Glossary / feature requests po files and other language support age: 51 weeks 4 days url: http://drupal.org/node/46313 Goofy / feature requests Goofy Forum UI age: 1 year 16 weeks url: http://drupal.org/node/32294 Htmlarea / bug reports Module does not work age: 3 weeks 3 days url: http://drupal.org/node/105475 if Clean URLs is Enabled, upload_image in htmlarea not working age: 26 weeks 6 days url: http://drupal.org/node/74119 htmlArea/xinha firefox freezes (multiple textareas) age: 33 weeks 2 days url: http://drupal.org/node/66746 Layout is quirky age: 45 weeks 5 days url: http://drupal.org/node/52741 Toolbar won't display correct in IE 6 with Pushbutton Theme age: 1 year 19 weeks url: http://drupal.org/node/30696 Htmlarea / support requests Problem with size of button assigned: khayman age: 38 weeks 5 days url: http://drupal.org/node/60255 Listhandler / bug reports user lookup on name only assigned: zeroj age: 42 weeks 7 hours url: http://drupal.org/node/56936 Link to mailhandler does not use l() function age: 1 year 1 week url: http://drupal.org/node/44599 Listhandler caused error in "comment.module on line 996" ? age: 1 year 11 weeks url: http://drupal.org/node/36244 Listhandler 4.6.0 fails to send emails at all age: 1 year 26 weeks url: http://drupal.org/node/27095 Listhandler / tasks Correct/Complete Documentation age: 1 year 12 weeks url: http://drupal.org/node/34909 Mailhandler / bug reports The e-mail address 'info(a)example.com' may not create story items. assigned: maverickvarun age: 8 weeks 5 days url: http://drupal.org/node/98723 Mailhandler / support requests Creating a page using mailhandler age: 31 weeks 4 days url: http://drupal.org/node/68947 Mail Body not downloaded age: 1 year 2 weeks url: http://drupal.org/node/43374 Members / bug reports Update: beta5 and possible problem with php 4 age: 46 weeks 3 days url: http://drupal.org/node/52004 Patch for member.module to bring it up to 4.7 age: 50 weeks 1 day url: http://drupal.org/node/47829 foreach() assigned: neablo age: 1 year 3 weeks url: http://drupal.org/node/42350 Node (key)words / bug reports Not Working age: 1 week 5 days url: http://drupal.org/node/107749 Meta description does not use the teaser of the page age: 2 weeks 4 hours url: http://drupal.org/node/107486 Error on delete node age: 21 weeks 2 days url: http://drupal.org/node/80505 can't use php functions in body of nodes assigned: Robrecht Jacques age: 22 weeks 2 days url: http://drupal.org/node/79315 Node (key)words / feature requests Can't Put Keywords in Categories age: 13 weeks 2 days url: http://drupal.org/node/90199 Enable nodewords for node type? age: 49 weeks 1 day url: http://drupal.org/node/48869 Node Aggregator / bug reports nodes are being created with no body age: 1 year 6 weeks url: http://drupal.org/node/40373 missing promote column assigned: Bèr Kessels age: 1 year 8 weeks url: http://drupal.org/node/38836 Naming issues with files and DB tables age: 1 year 13 weeks url: http://drupal.org/node/34298 RSS "no element found at line 1" age: 1 year 29 weeks url: http://drupal.org/node/26185 Outdated help texts age: 2 years 24 weeks url: http://drupal.org/node/9692 Import doesn't like XML/RSS feeds with no Title element age: 2 years 33 weeks url: http://drupal.org/node/8128 Node Aggregator / tasks move XML-parser into an inclde file. age: 1 year 30 weeks url: http://drupal.org/node/25439 Path / bug reports Login as an alias gets cached age: 1 year 17 weeks url: http://drupal.org/node/31699 Path / feature requests Admin created list of URL's to ignore age: 22 hours 45 min url: http://drupal.org/node/111171 Pdfview / bug reports custom fields not displayed age: 6 hours 43 min url: http://drupal.org/node/111340 Poormanscron / bug reports cron somehow interrupts MySql connection age: 1 week 2 days url: http://drupal.org/node/108676 Privatemsg / bug reports Impossible to clean-up database after uninstalling privatemsg age: 1 week 9 hours url: http://drupal.org/node/109206 Cannot send any private message age: 1 week 9 hours url: http://drupal.org/node/109205 contacts not found age: 7 weeks 6 days url: http://drupal.org/node/99789 When enableing the module, Drupal tries to update instead of install age: 16 weeks 20 hours url: http://drupal.org/node/86830 privatemsg module: - database error - incompatibility with relationship module age: 49 weeks 1 day url: http://drupal.org/node/48866 Remindme / bug reports Argument #1 is not an array age: 31 weeks 2 days url: http://drupal.org/node/69286 Cron job creates SQL error age: 33 weeks 5 days url: http://drupal.org/node/66202 Subscriptions / bug reports Unpublished nodes and comments age: 5 days 11 hours url: http://drupal.org/node/109755 Subscribe/Unsubscribe does not work on node form update age: 1 week 5 days url: http://drupal.org/node/107907 Subscriptions remain active when access control maintain subscriptions is disabled age: 15 weeks 3 days url: http://drupal.org/node/87625 Taxonomy dhtml / bug reports IE 7 javascript errors on the page that display the categories age: 7 weeks 1 hour url: http://drupal.org/node/101100 Disabling Teasers (Trimmed Posts) Not working when set to Unlimited assigned: samdeskin age: 12 weeks 3 days url: http://drupal.org/node/91299 doesn't work with taxonomy_access? age: 17 weeks 2 days url: http://drupal.org/node/85355 Error on Page with Internet Explorer 6 age: 31 weeks 4 days url: http://drupal.org/node/68906 Taxonomy DHTML's cache ignores user privileges age: 35 weeks 1 day url: http://drupal.org/node/64532 Does not work correctly in Internet Explorer age: 1 year 15 weeks url: http://drupal.org/node/33354 javascrip downloads square.gif for every category age: 1 year 48 weeks url: http://drupal.org/node/17366 Taxonomy dhtml / feature requests A unique page for each category group? age: 1 year 13 weeks url: http://drupal.org/node/34610 Taxonomy navigation / bug reports Taxonomy links only work for the first line of links assigned: PierreFWalter age: 47 weeks 2 days url: http://drupal.org/node/51149 TrackBack / bug reports install script does not put curly braces around table name age: 7 weeks 3 days url: http://drupal.org/node/100634 Sends trackbacks for unpublished nodes assigned: ankur age: 1 year 51 weeks url: http://drupal.org/node/16239 User experience / bug reports page not found when creating content assigned: DL age: 1 week 1 day url: http://drupal.org/node/109034 Verification Active assigned: maverickvarun age: 6 weeks 5 days url: http://drupal.org/node/101384 Webserver Auth / bug reports Logging out error age: 42 weeks 2 days url: http://drupal.org/node/56663 Wiki / bug reports the wiki module can't work with HTML age: 50 weeks 5 days url: http://drupal.org/node/47124

1 0

Re: [development] object.module (was nodify.module idea: 'everything is a node')
by Peter Wolanin 21 Jan '07

21 Jan '07

A quick summary of my thoughts on this; I disagree with some of the recent posts that seem to suggest putting all dupal "'objects" into one table. This has the same drawbacks as making everything a node. I'd much rather see an effort to build a single consistent API for all core and contrib-defined objects. Each of these object types would still have their own primary table (and possibly a revisions table). For example, rather than doing node_load(), user_load(), comment_load, etc, I'd like to be able to do: $node = drupal_load('node', $node_id); $user = drupal_load('user', $user_id) ... Assume $class = 'node', then when loading a node drupal_load() would call something like: $object = db_fetch_object(db_query("SELECT * FROM {%s} WHERE %s_id = %d", $class, $class, $id")); $extra = module_invoke_all($class .'_load', $object); The node module would declare a function (e.g. node_class_define()) that would return a list of all the fields in the node table for saving/inserting. Modules could optionally also define type object for their objects (i.e. node_type objects). This would mean any contrib module could define this one function and install the table and automatically get all the load, save, hook, etc. code for free. Menu module could even automatically define a standard set of non-cached paths and tabs like $class/$id/edit $class/$id/view $class/$id/revisions for each module that defines a drupal object, making the devel's life even easier. Anyhow, obviously the devil's in the details, but this sort of unified API seems much more valuable to me rather than tying to deny the uniqueness of each type of data by throwing them all in one enormous object table. This would seem also to move towards getting more of the advantages of OO programming, without getting hung up on the different support for objects in different PHP versions. -Peter

1 0

Re: [development] adoption for 'abandoned' modules?
by Karen Stevenson 21 Jan '07

21 Jan '07

> Here we get into a perception thing again.... how would one define > someone's activity to downgrade them? I myself am a burst worker. Do > stuff, do other stuff, live life... go through issue queue in a rampage, > repeat ;) I operate the same way, I guess I was thinking more in terms of no activity on any issues for some extended period of time, whatever 'extended' is. Anyway, I'm sorry I said anything at all. I have the greatest respect for the other hard working maintainers who have turned off their contact forms and I was certainly not suggesting that anyone needed to take any kind of action against them. Mea Culpa. Karen

1 0

Refactor l() and url()
by Steven Wittens 21 Jan '07

21 Jan '07

I'd like to point your attention to the following patch: http://drupal.org/node/111347 :) Steven Wittens

1 0

Re: [development] adoption for 'abandoned' modules?
by Steven Peck 21 Jan '07

21 Jan '07

We do have access to the email addresses regardless of contact settings and often a private email is sent before transfer is done. > -----Original Message----- > From: development-bounces(a)drupal.org [mailto:development- > bounces(a)drupal.org] On Behalf Of Darren Oh > Sent: Saturday, January 20, 2007 9:52 PM > To: development(a)drupal.org > Subject: Re: [development] adoption for 'abandoned' modules? > > On Jan 20, 2007, at 10:31 PM, Angela Byron wrote: > > > We shouldn't be encouraging people to e-mail maintainers. We should > > be encouraging people to use issue queues, because that's where > > community development and support happens. I specifically disabled > > my contact form for this reason. I know other maintainers have as > > well. > > The point is for one person with an active interest in the module to > be able to check with developers to see why they are not responding > to the issue queue. I've been told several times to check with the > module maintainer when a module I was interested seemed to be > abandoned. Two modules have been turned over to me when I reported > that the maintainer's contact form was disabled. It would have been > nice to have been able to ask the former maintainers if they intended > to be actively involved in future development.

1 0

Re: [development] adoption for 'abandoned' modules?
by Steven Peck 21 Jan '07

21 Jan '07

> -----Original Message----- > From: development-bounces(a)drupal.org [mailto:development- > bounces(a)drupal.org] On Behalf Of Karen Stevenson > Sent: Saturday, January 20, 2007 4:12 AM > To: development(a)drupal.org > Subject: Re: [development] adoption for 'abandoned' modules? > > That comment was supposed to be a little tongue in cheek. Ah, missed that. > Yes I know some of the high profile developers have done that and I can > understand why. I think it has to be combined with other factors -- no way > to contact them directly + no response to open issues on the queue = a > developer whose modules need to get downgraded or adopted. Here we get into a perception thing again.... how would one define someone's activity to downgrade them? I myself am a burst worker. Do stuff, do other stuff, live life... go through issue queue in a rampage, repeat ;) > However I do think there is really no reason for new developers who are > not so high profile to make themselves unreachable. Personal privacy? Paranoia, anti-social :) > Anyway, I wasn't really proposing automatic action against anyone whose > contact form was disabled. > > Everyone reacted to my tongue in cheek comment and no one reacted to what > I thought was the important idea -- that we provide a place on the project > page where you can identify the co-maintainers. > > Karen Well, I can see who the other maintainers are :) and was aware of Derek's idea's on the subject and remember Dries mock up. I am sure many others do as well so it's a good reminder that not everyone tracks what was said 6 months ago vs. the decisions that were made to get the progress on the solid foundation done so that the fancy bits could actually have some hope of being accomplished. I believe that Derek replied on the issues already, I am merely commenting on the diversity of knowledge on the list.

1 0

Re: [development] adoption for 'abandoned' modules?
by Karen Stevenson 21 Jan '07

21 Jan '07

That comment was supposed to be a little tongue in cheek. Yes I know some of the high profile developers have done that and I can understand why. I think it has to be combined with other factors -- no way to contact them directly + no response to open issues on the queue = a developer whose modules need to get downgraded or adopted. However I do think there is really no reason for new developers who are not so high profile to make themselves unreachable. Anyway, I wasn't really proposing automatic action against anyone whose contact form was disabled. Everyone reacted to my tongue in cheek comment and no one reacted to what I thought was the important idea -- that we provide a place on the project page where you can identify the co-maintainers. Karen ----- Original Message ---- From: Steven Peck <speck(a)blkmtn.org> To: development(a)drupal.org Sent: Friday, January 19, 2007 9:31:18 PM Subject: Re: [development] adoption for 'abandoned' modules? > -----Original Message----- > From: development-bounces(a)drupal.org [mailto:development- > bounces(a)drupal.org] On Behalf Of Darren Oh > Subject: Re: [development] adoption for 'abandoned' modules? > > On Jan 19, 2007, at 11:41 AM, Karen Stevenson wrote: > > > Also, I would require that anyone listed as a maintainer must have > > their contact form enabled, otherwise they get de-listed and their > > project gets put up for adoption on a special adoption page. OK, > > maybe that last bit is a little strong :-) but whether or not there > > is a way to contact the maintainer should be another factor in our > > 'gold star' system. > > Not too strong at all. If a person wants to control a project but > doesn't want to be contacted, he should maintain the project on his > own computer, not on Drupal. Let people who disable their contact > forms have CVS access, but find someone who will actually maintain a > project to be the maintainer. > Um, and those that out of frustration with people using the contact forum to mail them directly for support instead of using the issue queue? Do we disable their contrib. modules? Site admins can use the contact form. We have the email information and can email directly. Not to put a fine point on it but I know several active module contributors who have disabled their contact modules because of this sort of abuse.

4 4

Personal battle plans for Drupal 6
by Dries Buytaert 20 Jan '07

20 Jan '07

Yes, it's time to share your personal battle plans for Drupal 6! It's a bit of a tradition, and I think it's a rather fun one, so go ahead and share your personal battle plans for Drupal 6 at http:// drupal.org/node/111140. Oh, and this time, stick to the guidelines please! -- Dries Buytaert :: http://www.buytaert.net/

1 0