November 2009 - Development - lists.drupal.org

Content Specific Modules for Small Constituencies, Are they Kosher?
by Shai Gluskin 19 Nov '09

19 Nov '09

I'm thinking of creating a very simple module. All it would do is install a particular vocabulary on your site which has about 50 terms (I'll give the specific example further below). So I went to the modules directory and looked through the taxonomy category... looked at all 228 modules, and didn't find one which installed terms from a specific knowledge realm. I expected there to be some taxonomies from the realms of biology or other sciences; nothing. Thinking outside of "taxonomy" I remembered the weather module, which has 500K of data listing standard weather stations worldwide. And then the location module which has about 2mb of specific data on places. Now to my example... Jews study portions of the Torah (the first five books of the Bible) on a set calendar. The Torah is broken into 54 set portions; each of those portions has a name. It's traditional for clergy and lay leaders to give sermons or teachings related to the current portion of the week. For sites that post material relevant to the Torah portion, being able to easily install such a vocabulary populated with all the terms would be a nice convenience for them. My rough estimate is that there are about 50 synagogues currently using Drupal and probably another 150 Jewish organizations. The number is growing quickly, yet this is still a small number. So my question is... does the Drupal modules repository welcome such a targeted module with a small potential user-group with content that is specific and contains no generalizable functionality? My assumption had "yes." But seeing that others haven't created similar modules for specific vocabularies... makes me wonder. What say you? > > Shai

6 6

fitter, healthier, more productive
by As If Productions 19 Nov '09

19 Nov '09

Can we trim our replies please? Thanks. LVX TF --- As If Productions http://www.asifproductions.com Interactive Worlds and Immersive Obsessions

1 0

Re: [development] problems with permissions on node
by Svein-Tore With 19 Nov '09

19 Nov '09

I think you need to add a "$" sign in line 7 Cheers, Svein-Tore With (username falcon) > function nodetype_access($op, $node, $account) { > $is_author = $account->uid == $node->uid; > switch ($op) { > case 'create': > return user_access('create nodetype', $account); > case 'update': > $output = user_access('edit own nodetype', $account) && [HERE]is_author || > user_access('edit any nodetype', $account); > if ($output) return TRUE; > case 'delete': > return user_access('delete own nodetype', $account) && $is_author || > user_access('delete any nodetype', $account); > } > }

4 4

can any one help me views
by vishnu vardhan 19 Nov '09

19 Nov '09

Hi All , I am currently assigned with a project in drupal to work with views. Can anyone guide me how should i go about it???? I am referring http://drupal.org/node/109604 but since there are no examples i am unable to grasp much. I want to work with views2 . Is it necessary to have CCK module enabled to work with views2. What if I want to add an option in the default list of fields,arguments,filter how should i go about it ??? Vishnu On Thu, Nov 19, 2009 at 2:33 PM, <development-request(a)drupal.org> wrote: > Send development mailing list submissions to > development(a)drupal.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.drupal.org/mailman/listinfo/development > or, via email, send a message with subject or body 'help' to > development-request(a)drupal.org > > You can reach the person managing the list at > development-owner(a)drupal.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of development digest..." > > > Today's Topics: > > 1. Re: CVS Approval Policy: was Re: new features in D6 core? > (David Metzler) > 2. Re: Content Specific Modules for Small Constituencies, Are > they Kosher? (Larry Garfield) > 3. Re: Content Specific Modules for Small Constituencies, Are > they Kosher? (Shai Gluskin) > 4. Re: PHP Standards Group (Larry Garfield) > 5. Re: PHP Standards Group (David Metzler) > 6. Re: Content Specific Modules for Small Constituencies, Are > they Kosher? (info(a)marcvangend.nl) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 18 Nov 2009 20:53:22 -0800 > From: David Metzler <metzlerd(a)metzlerd.com> > Subject: Re: [development] CVS Approval Policy: was Re: new features > in D6 core? > To: development(a)drupal.org > Message-ID: <4167D2ED-EDD7-4662-8218-5D622DD9D862(a)metzlerd.com> > Content-Type: text/plain; charset="us-ascii" > > Before one tries to solve a problem, it would be interesting to prove > or provide evidence that it exists. As a module maintainer, I think > REALLY HARD before considering creating a new module on CVS, because > I know what maintaining a module entails, and I've already worked > hard to try and get others involved in my own issue queue. I lean > towards looking for duplicate modules cause I want to pair up with > people to lessen my own workload. If I post a module, I've already > tried to find another module that does something similar, and when > possible have tried to float patches against that module to get it to > do what I want it to do. Because I KNOW my time is limited. I don't > think that I'm alone here. > > Anecdotes don't count here. If we've got 5000+ modules, how many of > these are duplicates posted by maintainers of other modules. My bet > is the number is really low, and not worth investing a ton of time in. > > Show me da numbers.... :) > > On Nov 18, 2009, at 4:08 AM, Ashraf Amayreh wrote: > > > I suddenly got this (perhaps silly) idea of only allowing a CVS > > owner to create one project and require approval by posting to the > > DEV list when wishing to create another project rather than making > > this open for all CVS owners. This would definitely help with the > > repetition problem and module boom. > > > > Posting to the DEV list should at least give other module > > developers and people interested the opportunity to object to, > > agree or suggest alternatives to the proposed module rather than > > suddenly finding a useless/repetitive module springing up here and > > there because the developer didn't know another one existed. > > > > Suggestions? Flames? Thoughts? > > > > AA > > > > On Sat, Oct 24, 2009 at 4:35 AM, Jeff Greenberg > > <jeff(a)ayendesigns.com> wrote: > > Dave Reid wrote: > > > > Again, how can one person know that one line is useful to the > > entire community if other people don't speak up about it? It > > requires the community to be involved in the process and not > > reacting to just when there are problems. > > > > Right, then if one person isn't qualified to know whether it would > > be useful to the community, let the community decide by downloading > > it or not. > > > > > > > > -- > > Ashraf Amayreh > > http://aamayreh.org > >

2 1

new dev q: are mysql queries possible within drupal?
by spartaguy spartaguy 19 Nov '09

19 Nov '09

Hi, How can add an item to the Primary links Menu that will do a basic select query within drupal? ie Lets say I have a mysql database "database1" and a table "table1" with the following fields (name, address, email etc) How can I add a menu item to the Primary Links menu that will do a select * from table1 and then print it out in the right hand panel? Is this possible? Does it have to be the same database drupal uses or can I query a different db? Paul ps. The result would be something like: Joe Blow | 123 abc avenue | joeblow(a)applecart.org Joe Blow1 | 12323 abc avenue | joeblow1(a)applecart.org Joe Blow2 | 12323 abc avenue | joeblow2(a)applecart.org

8 12

PHP Standards Group
by larry＠garfieldtech.com 19 Nov '09

19 Nov '09

Back in the spring, a group of PHP developers from several popular "pure frameworks" got together and started a PHP standards working group. Their goal was to standardize certain OO coding standards, in particular the use of namespaces, across PHP projects, even if such standards necessitated some changes in the participating projects' existing code bases. There was some fallout about the group being self-declared and trying to establish project standards by fiat, with a number of people, myself included, objecting to either the fait accomplis presentation, the details of the proposed standards, or both. Eventually the core team moved off to an invite-only list, and I largely lost track of them. Yesterday, they decided they should invite in representatives from a few other frameworks and projects, including Drupal. I discovered this when I suddenly found myself on the list and getting messages, as I'd been sitting in the pending membership queue for months. :-) So apparently I'm now the "Drupal representative". Goodie... So before I open my big mouth, to what degree are we interested in being involved, and to what degree are we willing to play by the standards this group develops? Personally, I think we should try to do so where possible. It's good for inter-operability, reduces the learning curve for PHP-knowledgeable developers coming into Drupal, and frankly a lot of these people have been working with OO PHP a lot longer than we have so there's much to be learned from them. It also means that we can begin to shift ourselves in the "right" direction for whenever we're able to drop PHP 5.2 and rely on PHP 5.3 namespaces, which will open up all sorts of new and exciting power and weirdness. However, I'm not sure that we should commit to following the developed standards, period. As of the last draft I saw, some of them would not, I think, even be compatible with a modular full-stack framework like Drupal to begin with, mostly regarding a universally-applicable autoload pattern. So I would like to go into the process with a statement of "we'll be involved in developing such standards and will adopt them wherever feasible, but we do not commit to following all standards if they are incompatible with Drupal's basic architecture." +1, -1, feedback, flames, recriminations, encouragements, death threats...? --Larry Garfield

12 13

Move Dev List to groups.drupal.org
by Shai Gluskin 18 Nov '09

18 Nov '09

I'm pulling this out as a separate thread... Jenniver wrote, Shai Gluskin wrote: > 3. *Move dev list to g.d.o.* [...] > I can sympathize with your desire to have a more searchable output for this list, on-line forums such as g.d.o are a huge barrier to participation compared to email lists. So if this list is moved to g.d.o and we want it to still be a useful list with immediate feedback and lots of participants, we would also need to provide a way for people to participate fully via email (i.e. make it so it looks and acts just like an email list). In which case, the threads will look/act/search like email, and I don't think we will have solved anything. --Jennifer My issue with the search results at http://lists.drupal.org/pipermail/development is not the formatting; it's the content. Searching on terms like "module development" the top results are from March. I mean, there really is something wrong. Given the delays in upgrading to the new d.o. design, I'm not sure where things stand. But I know there were definitely discussions about tweaking the notifications system and also adding Mail Comment (formerly Mail2Web): http://drupal.org/node/634074. Mail Comment would allow for replicating list serve functionality for folks who don't want to go to g.d.o. And again... I don't care about the formatting; I want the transparency, the integration with d.o. web sites, it running on Drupal, and also the much more personal and community feel you get at g.d.o with user pics/profiles etc. With Mail Comment we can have the push of the list serve but the better functionality of g.d.o. Shai

11 12

New maintainer for mail2og?
by arthur 18 Nov '09

18 Nov '09

While we are on the subject of mail and OG, if somebody wants to take over and fix mail2og (http://drupal.org/project/mail2og) I'd gladly hand it over. I've got to much going on right now to maintain it. Mail2Og takes arbitrary to addresses and maps them to drupal group titles. It needs some love. a. On Nov 18, 2009, at 2:54 PM, Kieran Lal wrote: > On Wed, Nov 18, 2009 at 2:49 PM, Jamie Holly <hovercrafter(a)earthlink.net > > wrote: >> Yeah I got an email from a GDO group yesterday for a message that >> was posted >> 4 days earlier. >> >> But what would be really cool, though require some custom module >> work, is a >> way to make G.D.O operate more like Google Groups. People could >> choose to >> use the web site and/or email - ala listserv style. Of course that >> would >> require pumping emails through a script handler, which can be done >> in PHP. >> It would also be a rather sweet contrib module to allow other sites >> to do a >> similar type system. > > Great idea! > > We started in 2005 an released it in 2006. http://drupal.org/project/og2list > > Everybody wants it but nobody wants to fund it. > > Kieran > >> >> Jamie Holly >> http://www.intoxination.net http://www.hollyit.net >> >> >> >> Earl Miles wrote: >>> >>> Until g.d.o gets actually useful email notifications, I am against >>> this. >>> >>> Right now, g.d.o is useless to me, because the notifications >>> system has >>> regressed. >>> >>> (All we really need is good titling and threaded support, for my >>> purposes. >>> it doesn't need to *respond* to email, I'm perfectly ok with >>> clicking a link >>> to reply). >>> >>> Shai Gluskin wrote: >>>> I'm pulling this out as a separate thread... >>>>> Jenniver wrote, >>>>> Shai Gluskin wrote: >>>>> 3. *Move dev list to g.d.o.* [...] >>>>>> I can sympathize with your desire to have a more searchable >>>>>> output >>>>>> for > this list, on-line forums such as g.d.o are a huge >>>>>> barrier to > >>>>>> participation compared to email lists. >>>>> So if this list is moved to g.d.o and we want it to still be a >>>>> useful >>>>>> list with immediate feedback and lots of participants, we would >>>>>> also > >>>>> need to provide a way for people to participate fully via email >>>>> (i.e. > make >>>>> it so it looks and acts just like an email list). In which case, >>>>> > the >>>>> threads will look/act/search like email, and I don't think we >>>>> will > have >>>>> solved anything. >>>>> --Jennifer >>>>> My issue with the search results at > >>>>> http://lists.drupal.org/pipermail/development is not the >>>>> formatting; > it's >>>>> the content. Searching on terms like "module development" the >>>>> top > results >>>>> are from March. I mean, there really is something wrong. >>>>> Given the delays in upgrading to the new d.o. design, I'm not sure >>>>> where > things stand. But I know there were definitely >>>>> discussions about > >>>>> tweaking the notifications system and also adding Mail Comment >>>>> (formerly > >>>>> Mail2Web): http://drupal.org/node/634074. Mail Comment would >>>>> allow for > >>>>> replicating list serve functionality for folks who don't want to >>>>> go to > >>>>> g.d.o. And again... I don't care about the formatting; I want >>>>> the > >>>>> transparency, the integration with d.o. web sites, it running on >>>>> Drupal, > >>>>> and also the much more personal and community feel you get at >>>>> g.d.o with > >>>>> user pics/profiles etc. With Mail Comment we can have the push >>>>> of the > list >>>>> serve but the better functionality of g.d.o. >>>>> Shai >>> >>> >>> >> > --------------------------------------------------- arthur(a)24b6.net

1 0

Re: [development] development Digest, Vol 83, Issue 34
by David Burns 18 Nov '09

18 Nov '09

Just speaking from personal experience. I don't think I would be as active with Drupal had I not been allowed to submit my modules to get feedback from the community. However, I do think some (alot, okay most) modules, including a couple of my own, are not worthy to be listed on Drupal.org. Instead of taking away the ability to contribute, I do think there should be a minor approval process. I know this adds a layer of complexity but I think most solutions will. I think the following would be a good workflow: 1. Open CVS Repo for anyone to contribute. "Drupal Alpha Repository" 2. Once an Alpha module gains popularity and is approved as unique to existing modules it would then be ported to cvs.drupal.org repo 2a. alternatively, if the code is similar to or heading in the same direction as another module it could then be suggested that the new module developer assist with development on existing module. This may have possibly been suggested before. I apologize if it has, I just re-enabled myself to this mailing list. > From: development-request(a)drupal.org > Subject: development Digest, Vol 83, Issue 34 > To: development(a)drupal.org > Date: Wed, 18 Nov 2009 13:59:41 +0000 > > Send development mailing list submissions to > development(a)drupal.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.drupal.org/mailman/listinfo/development > or, via email, send a message with subject or body 'help' to > development-request(a)drupal.org > > You can reach the person managing the list at > development-owner(a)drupal.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of development digest..." > > > Today's Topics: > > 1. Re: CVS Approval Policy: was Re: new features in D6 core? > (Ashraf Amayreh) > 2. Re: CVS Approval Policy: was Re: new features in D6 core? > (Pierre Rineau) > 3. Re: CVS Approval Policy: was Re: new features in D6 core? > (Randy Fay) > 4. Re: CVS Approval Policy: was Re: new features in D6 core? > (Daniel F. Kudwien) > 5. Re: CVS Approval Policy: was Re: new features in D6 core? > (Ashraf Amayreh) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 18 Nov 2009 15:30:15 +0200 > From: Ashraf Amayreh <mistknight(a)gmail.com> > Subject: Re: [development] CVS Approval Policy: was Re: new features > in D6 core? > To: development(a)drupal.org, pierre.rineau(a)makina-corpus.com > Message-ID: > <a53d1b3b0911180530k57fab7c3h8cfc34ca382f02fb(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > It seems you misunderstood my reasoning. I'm simply suggesting this to make > it compulsory for any CVS owner to talk about a possible module on the dev > list BEFORE being able to create the project node. If the module is new it > will get a thumbs up and he would get the go, if it's repetitive, the CVS > owner will need to give good reasoning and then could be allowed to post it, > and if he can't persuade anyone it would get rejected. Other module > developers could suggest teaming up or perhaps point him to modules with > similar functionality that he was unaware of as long as he has to post to > the dev list before being able to create a new project node (kind of reminds > me of the node limit module). > > I'm simply suggesting this to make sure modules don't spring up in the dark > without anyone's knowledge rather than trying to oppose repetitive modules. > Currently, CVS owners are free to add as many project nodes as they want > when they get their CVS access. Which sounds wrong given that he got his > access for creating one module. > > Suggestions? Flames? Thoughts? > > AA > > On Wed, Nov 18, 2009 at 2:23 PM, Pierre Rineau < > pierre.rineau(a)makina-corpus.com> wrote: > > > On Wed, 2009-11-18 at 14:08 +0200, Ashraf Amayreh wrote: > > > I suddenly got this (perhaps silly) idea of only allowing a CVS owner > > > to create one project and require approval by posting to the DEV list > > > when wishing to create another project rather than making this open > > > for all CVS owners. This would definitely help with the repetition > > > problem and module boom. > > > > > > Posting to the DEV list should at least give other module developers > > > and people interested the opportunity to object to, agree or suggest > > > alternatives to the proposed module rather than suddenly finding a > > > useless/repetitive module springing up here and there because the > > > developer didn't know another one existed. > > > > > > Suggestions? Flames? Thoughts? > > > > FLAAAAAAAAAAAAAAAAAAAAME! Repetitive modules are good, they always have > > subtile differences! > > > > Please, project owners, do describe why your module is unique on your > > project page! > > > > Pierre. > > > > > > > -- > Ashraf Amayreh > http://aamayreh.org >

2 1

problems with permissions on node
by Lluís 18 Nov '09

18 Nov '09

I have created a custom permission node; I should be able to edit that node, but I am unable. How should my nodetype_access function be to allow read/write/delete access? function nodetype_access($op, $node, $account) { $is_author = $account->uid == $node->uid; switch ($op) { case 'create': return user_access('create nodetype', $account); case 'update': $output = user_access('edit own nodetype', $account) && is_author || user_access('edit any nodetype', $account); if ($output) return TRUE; case 'delete': return user_access('delete own nodetype', $account) && $is_author || user_access('delete any nodetype', $account); } } -- *Les normes hi són perquè hi pensis abans de saltar-te-les *La vida és com una taronja, què esperes a exprimir-la? *Si creus que l'educació és cara, prova la ignorància. *La vida és com una moneda, la pots gastar en el que vulguis però només una vegada. *Abans d'imprimir aquest missatge, pensa en el medi ambient.

2 1