March 2006 - Development - lists.drupal.org

Drupal & automated testing
by Tao Starbow 07 Mar '06

07 Mar '06

I know I do not yet have much credibility in the Drupal community, so I apologize in advance for making sweeping statements. I think the Drupal process could really benefit from a culture of obsessive automated testing. I have been programming for over 15 years, and one of the most valuable mottoes I have heard is "If a feature is not covered by an automated test, it does not exist". Practically, if something like Simpletest was in core, then the requirement for submitting a patch could be increased to also submitting a test that exposes the original bug & shows that it has been fixed. Skilled users could submit tests that expose the bug as part of the original issue submission. And submitting original tests could be a great way for new users to contribute. As the coverage of the submitted tests grows, developers will be able to have more and more confidence that the patch they are submitting does not cause regressions. Programming on complex systems is just so much more fun, when you know you are not breaking someone else's hard work. A comprehensive test framework can become a safety net, supporting Drupal's rapid evolution. Right now it seems like Drupal succeeds because it has such a robust community, which is willing to act as a test system, but that approach runs the risk of exhausting everyone involved. I know everyone has way too much on there plates right now to really consider culture change, but I wanted to try and get this idea out there. If there is one gift I can give to the Drupal community, out of half a lifetime of experience with many programming languages and cultures, this is it. Thanks for listening. -- Tao Starbow Web Architect, CITRIS

7 8

Update Notifications
by Dan Ziemecki 07 Mar '06

07 Mar '06

Today while I was updating my Firefox extensions, it occurred to me that this would be some really nice functionality to have in a CMS. What if every time an admin logged in or ran a "Check For Updates" module, he'd get a list of his active modules with lower version numbers that what's currently available in CVS? Maybe the list has a link to each module's project page for immediate review and download. The module itself sounds like it would be relatively simple: parse the version number out of each of the module files and compare them against a master list of current versions. The trick would be that master list. I'm imagining something like an XML file hosted on cvs.drupal.org that generates on call (or maybe once a day). Does this sound interesting to anyone but me? Is there any way we could extract latest version numbers from CVS? -- Dan Ziemecki Philosopher. Curmudgeon. Nerd.

3 4

Re: [support] flexinode + i18n module
by VJ 07 Mar '06

07 Mar '06

Actually, does anyone know how to print attachment module attachments using phptemplate ? I figured out how to print upload module attachments, but most of my nodes use attachment module. I am not doing print $content or print $node->body for reasons explained in earlier posts but some how $content and $node->body are able to get the attachments -v > Thanks for the pointer. > > I created a node-flexinode-1.tpl.php . > > I can pull a label (say label number 21), using flexinode_load_field(21); > How do I print its spanish counterpart (using localization module), in the > template? > > Also, if I want to print the whole node manually (without using print > $content; I am hitting a roadblock when I try to print attachments (using > upload module or attachment module). How do I do that? > > This is probably more complex than it needs to be, we need native support > for i18n in flexinode module. > > -v > > > > > >> Hi, >> >> A flexinode is like a node, and it's translation is much like the same. >> The >> question here, is that while in normal nodes the "labels" are static, in >> flexinode they are "dynamic". >> Like I said, I will take a look at it because I will need that >> functionality >> too :) >> >> You can create a node-flexinode.x.tpl.php (refer to drupal themes >> developer >> handbook for more info) and there you can define your labels and also >> use >> translation functions. >> >> As you can see in the "bugs/features list" both in flexinode and i18n, >> all >> the work I'm doing is sent as patches for version 4.6. Now, I hope that >> someone at least verify those patches and if they like it apply them to >> main >> tree. Of course, that would be nice that they could check and upgrade >> them >> to version 4.7! >> I can do that when I update my version to 4.7, but for know I'm being >> carefull enough to describe all my patches to apply them to my tree... >> >> Regards, >> Fernando Silva >> >> On 2/26/06, VJ <vrao(a)misteam.net> wrote: >>> >>> >>> >>> Thanks. I was curious if there is a more correct way to translate >>> flexinode content. The module usually comes with some .po files. Is >>> there >>> a scoop on that? >>> >>> Or atleast, is there a way I can change content in node.tpl.php ? >>> >>> Im not keen on hacking the module itself, since I want to upgrade to >>> 4.7 >>> and I can see potential problems with updating a hacked module >>> >>> >>> -v >>> >>> p.s Ive noticed that the localization interface sometimes has >>> duplicates >>> , >>> is this a known bug? >>> >>> >>> > Hi, >>> > >>> > I am in this precise moment implementing a site with 3 languages so I >>> will >>> > have to check that, and try to create a patch. I'm not maintainer >>> neether >>> > of >>> > flexinode or i18n, so meanwhile, it makes more sense go to the bug >>> report >>> > of >>> > i18n (it seems to me that this is a i18n problem) I try to get some >>> help. >>> > >>> > Regards, >>> > Fernando Silva >>> > >>> > On 2/23/06, VJ <vrao(a)misteam.net> wrote: >>> >> >>> >> >>> >> >>> >> field labels : i.e 'label' column from the flexinode_field table >>> >> >>> >> For ex: I have a flexinode called project. I have a field label >>> called >>> >> Project Abstract. I translated it to Resumen del Proyecto using the >>> >> localization interface. >>> >> >>> >> Now if I go to website.com/es/add/node/flexinode-1 it shows up the >>> >> spanish >>> >> labels but once the node is submitted all the labels are displayed >>> in >>> >> english. >>> >> >>> >> It looks like flexinode creates the node body by calling the field >>> label >>> >> followed by field data and doesnt pay any attention to translated >>> >> labels. >>> >> I will have to hack the module and make it call the translated >>> labels >>> >> right? or is there a more correct solution? >>> >> >>> >> Thanks, >>> >> >>> >> VJ >>> >> >>> >> >>> >> > Can you be more specific? Are you talking about fields data, or >>> fields >>> >> > labels? >>> >> > >>> >> > Regards, >>> >> > Fernando Silva >>> >> > >>> >> > On 2/22/06, VJ <vrao(a)misteam.net> wrote: >>> >> >> >>> >> >> >>> >> >> Hi, >>> >> >> >>> >> >> When I translate all the flexinode fields through localization, >>> it >>> >> shows >>> >> >> up under add->content. For example : Author name shows up under >>> >> >> /en/add/node/flexinode-1 and the corresponding spanish >>> translation >>> >> shows >>> >> >> up under /es/add/node/flexinode-1 >>> >> >> >>> >> >> However, the node display always shows the fields in >>> english..even >>> if >>> >> it >>> >> >> was created through the spanish interface. >>> >> >> >>> >> >> Has anyone been able to come up with a solution where flexinodes >>> are >>> >> >> translated correctly? >>> >> >> >>> >> >> Thanks, >>> >> >> >>> >> >> VJ >>> >> >> >>> >> >> >>> >> >> -- >>> >> >> [ Drupal support list | http://lists.drupal.org/ ] >>> >> >> >>> >> > -- >>> >> > [ Drupal support list | http://lists.drupal.org/ ] >>> >> >>> >> >>> >> >>> >> -- >>> >> [ Drupal support list | http://lists.drupal.org/ ] >>> >> >>> > -- >>> > [ Drupal support list | http://lists.drupal.org/ ] >>> >>> >>> >>> -- >>> [ Drupal support list | http://lists.drupal.org/ ] >>> >> -- >> [ Drupal support list | http://lists.drupal.org/ ] > > > > -- > [ Drupal support list | http://lists.drupal.org/ ] >

1 1

Image Support in the upcoming drupal release
by Drupalista 06 Mar '06

06 Mar '06

Hi, I am testiung drupal extensively. great ideas, really, you made a fine job there. *BUT* I need to admit, that the image handling is absolutely not acceptable at the moment. I read about I think 4 or 5 different ways to get inline images into articles. That is all "hidden" in the forums and users have to fight thru several modules to get something working that people are used to get as an out-of-the-box feature. inline, upload, img. img_assist, then complications with different other modules, inline tags showing up in taxonomy blocks, editors not working because of patches... totally unusable for "the normal user" I really like drupal. PLEASE make the image uploading thing an important issue - please tidy up that image module jungle and provide ONE working and good integrated image tool that comes with drupal core. please do not release any new drupal without that image functionality beeing at least as good and usable as in other systems around. THANKS! Drupalista

14 17

Re: [development] Re-Thinking Events in Drupal (and time zones too)
by Chad Phillips -- Apartment Lines 06 Mar '06

06 Mar '06

>>The solution for us, I think, is to turn these binary lookup tables into PHP objects with the same information. isn't this pretty much what event_timezones.inc in the event module does already? i've done some lobbying to get that approach into core , but to no avail...

2 2

Re: Re-Thinking Events in Drupal (and time zones too)
by Chad Phillips -- Apartment Lines 06 Mar '06

06 Mar '06

>>Am I the only person who thinks that timezones and especially daylight savings time are completely >>moronic >>inventions. >>It would just be so much simpler if everyone operated on GMT. do you know how many times i thought this while developing event repeat??? it would have saved me 50-100 hours of development time! let's start a worldwide campaign to switch :)

1 0

no 4-7-0 branch for core yet?
by Moshe Weitzman 06 Mar '06

06 Mar '06

i am trying to checkout a 4-7-0 branch from core for a client. I want him to get all updates to this branch just by cvs up. But that branch does not exist yet AFAICT. Is there some better way to do this. Should we ask Dries and team to create one? I suppose it doesn't exist yet because we haven't opened up HEAD for features. -moshe

28 59

Re: [bug] Allow embedded images in project description
by David Reed 06 Mar '06

06 Mar '06

Thanks for the feedback Dries. I'd be happy to take another crack at this patch later this week. I have a business trip that will keep me tied up until probably Friday at least. On 3/6/06, Dries <drupal-devel(a)drupal.org> wrote: > > Issue status update for > http://drupal.org/node/49575 > Post a follow up: > http://drupal.org/project/comments/add/49575 > > Project: Project > Version: cvs > Component: User interface > Category: bug reports > Priority: normal > Assigned to: Anonymous > Reported by: der > Updated by: Dries > Status: patch (code needs review) > > Code comment: we should wrap a check_url() around the screenshot URL > (depending on the format). We should add an alt-attribute for level 1 > accessibility. > > > What happens with projects who configured a screenshot link? The > Drupal project's screenshot link, for example, points to a gallery (see > http://drupal.org/project/drupal) Maybe we need to add a second URL so > we can do stuff like they do at the Firefox plugin directory (see > > https://addons.mozilla.org/extensions/moreinfo.php?id=220&application=firef… > and note the 'more previews' link below the screenshot). > > > Would you be able to work on this some more, so we can implement this > properly? I'd be happy to help test/review such functionality and roll > it out on drupal.org. > > > > > Dries > > > > Previous comments: > ------------------------------------------------------------------------ > > Wed, 15 Feb 2006 21:09:41 +0000 : der > > Per the related discussion [1] on the infrastructure mailing list, there > needs to be a way to embed an image in the description of a project. > This is particularly useful for showing theme screenshots. > [1] > http://lists.drupal.org/archives/infrastructure/2006-02/msg00154.html > > > > > ------------------------------------------------------------------------ > > Sat, 04 Mar 2006 05:35:47 +0000 : der > > Attachment: http://drupal.org/files/issues/project.module_1.patch (1.69KB) > > Here's a patch that uses the existing screenshots db field for the img > tag source. > > > > > ------------------------------------------------------------------------ > > Mon, 06 Mar 2006 15:09:14 +0000 : der > > Just a comment on this patch. The intent of this feature request was to > allow screenshot images to be displayed for "theme" projects. But the > patch doesn't limit it to any particular project type. My assumption > is that it could be controlled in the stylesheet. > > > > >

1 0

Re: [development] Drupal and i18n, the holy grail?
by Jakub Suchy 06 Mar '06

06 Mar '06

> On example: using single storage, we can store also information about > languages, so for a single menu item it should look similar as this: > <en>about us</en><de>ueber uns</de><hr>o nama</hr> > When drupal builds up the page, after it loads the node, proper > translation should be processed (if user is on EN part of the site, then > should be always English content processed from the node. > If there is no content (and menu is there), we can put some default info > message. > > Of course this approach than needs changes in GUI so that we can edit > each language content separately (combo box with language selection, > some _javascript_, some text processing/tagging in background). > > Advantage is that we don't need to change table structure. This is nice, but what about speed? It will require parsing each and every node content for every page display (or caching). Second approach, with <?php tags is very user unfriendly too... Jakub MeBa Suchy -- Jakub Suchý <jakub.suchy(a)logios.cz> GSM: +420 - 777 817 949 LOGIOS s.r.o, V Podhájí 776/30, 400 01 Ústí nad Labem tel.: +420 - 474 745 159, fax: +420 - 474 745 160 e-mail: info(a)logios.cz, web: http://www.logios.cz

2 1

enterprise needs
by qomo 06 Mar '06

06 Mar '06

Ben, Dries and chx are really nice people when you talk with them in person. I agree with you that Drupal's lack of backwards compatibility makes it difficult for enterprise users. One of the biggest enterprise users told me he plans to never upgrade. Other enterprise users I spoke with about this have reached the same conclusion. I've heard it said that if Drupal were forced to choose between the little 'guy', and corporate users, Drupal will choose the little person every single time. For Dries this is a labor of love. An example of what (one of) motivates him is that someone with a terminal/serious disease can reach out and find help through Drupal. Helping some big corporation save money is not what motivates him to give so much of his time to Drupal. Many people working with Drupal/civicspace are motivated by the idea of empowering the individual/"masses." (of course large non-profits also are enterprise users.) I would guess there's a 25% probability that an enterprise fork will develop that is backwards compatible. I do think that will be necessary for Drupal to become accepted in the corporate world. At the conference we talked about having an enterprise user group and/or an enterprise mailing list. Perhaps that can happen Enterprise users do have a lot to offer the community in terms of putting modules back in and donations. I think it's great you've written so much code. Thank you. I hope you can find a way to make Drupal fit your needs. Ann

15 29