- Development - lists.drupal.org

Finding logic flaw in wishlist module
by Tony Yarusso 12 Dec '08

12 Dec '08

As background, I'm attempting to modify the wishlist module (http://drupal.org/project/wishlist) to allow anonymous users to claim gifts for purchase. While I have most of it figured out, I think I found a bug lurking somewhere else (which may be why this was disabled originally). Here's what happens: When an anonymous user views the wishlist in list view, they will see the "Get this gift" link regardless of its purchase status. Authenticated users will properly get either "Get this gift" or "none left to purchase". For either type of user, on the full node view of the gift in question they will see the correct numbers for "number requested" and "number purchased", and other things on that page will properly reflect its status. I think I've narrowed down which section of code is responsible for the generation of that link in the "action" column of the list, and have provided it along with the working code from the node view for comparison at http://drupalbin.com/4455. However, my PHP skills are terribly lacking, so when things get nested that far I just get totally lost, so what I'm hoping is that someone else can look at what's going on there and spot the problem. -- Tony Yarusso http://tonyyarusso.com/

3 3

Old module update functions
by Eric-Alexander Schaefer 09 Dec '08

09 Dec '08

Hi List, is it save to remove old update functions from module.install. E.g. is it safe to remove D5-based update functions in D6 versions? Thanks, Eric

6 5

about webfm module
by Aldo Martinez Selleras 09 Dec '08

09 Dec '08

somebody know how may i call de webfm_main() function, and give the root directory where i want he read? thks a lot! -- ---------------------- Aldo Martinez Selleras Administrador del Nodo CITMATEL GND Camaguey Tel: 32-291661 E-mail: aldo(a)caonao.cu Linux User #364356

2 1

Re: [development] A streamlined way to develop core patches
by David Timothy Strauss 08 Dec '08

08 Dec '08

I've done this now. All revisions 7 and later have CVS updates with pruned directories. ----- "Konstantin Käfer" <kkaefer(a)gmail.com> wrote: > Thanks! > > Is it possible to remove the empty directories that are unused in CVS > > (like /database or /themes/goofy). > > Konstantin > > On 07.12.2008, at 05:27, David Timothy Strauss wrote: > > > I've made a post on the Four Kitchens blog about a new repository > > we're hosting to support streamlined core development. > > > > The post is here: > > > > > http://www.fourkitchens.com/blog/2008/12/07/using-bazaar-work-drupal-core-p… > > > > And here it is in plain text: > > > > As anyone who's developed core patches knows, it's not the writing > > > of initial patch that takes the work, it's the combination of > > revising the patch and keeping up to date with HEAD. With > > Drupal.org's CVS, this is difficult because you cannot commit your > > > core changes to checkpoint your work. CVS's merge algorithms are > > also relatively poor for maintaining large divergence from CVS > HEAD. > > > > One option -- which several community members used to create the > > huge DB-TNG patch -- was to create a Subversion repository. This is > > > far too much overhead for smaller core patches, and it still > > required person-by-person approval to commit to the Subversion > > repository. > > > > Four Kitchens is now hosting a much more flexible system for users > > > of Bazaar. Every hour, we synchronize core changes from CVS HEAD > > into our Drupal 7 branch, which is available for anonymous branching > > > by anyone. > > > > Simply download and install Bazaar, which has packages or installers > > > for Linux, Windows, Mac OS X, and BSD. We're using a repository > > format that should work with Bazaar 1.0 and newer, at a minimum. > > > > Then, where you're ready to develop, run this: > > > > bzr branch bzr://vcs.fourkitchens.com/drupal/7 [optional-working- > > copy-directory] > > > > You'll have a fresh working copy with a number of benefits over a > > CVS checkout: > > > > You can commit to your local branch to checkpoint your work: bzr > > commit > > You can integrate in changes to HEAD using Bazaar's superior merge > > > algorithms: bzr merge > > You can branch from your own branch: bzr branch [existing] [new] > > If you're working with others and they have Bazaar branches, too, > > you can merge from their branches to collaborate. > > And when you're ready to post a patch, run bzr diff --old bzr:// > > vcs.fourkitchens.com/drupal/7 to create a patch reflecting all of > > your changes relative to CVS HEAD. > > > > It will be a while before Drupal.org moves to anything other than > > CVS. Until then, we can foster decentralized development quite > > effectively using something like the Four Kitchens repository. -- David Strauss | david(a)fourkitchens.com | +1 512 577 5827 [mobile] Four Kitchens | http://fourkitchens.com | +1 512 454 6659 [office] | +1 512 870 8453 [direct]

1 0

create book via drupal_execute
by David Cohen 07 Dec '08

07 Dec '08

I'm trying to import content from a number of files into Drupal book nodes. I'm importing a large outline into a D6 site. node_import module does not work for D6 so I've written my own code. I'm able to create the book nodes via drupal_execute, but for the life of me I cannot figure out how to make one page the child of another page. The best I can do is create siblings within a single book. Does anyone have the know-how of the book module or drupal_execute to tell me how to do this? If so please reply to http://drupal.org/node/344040 Thanks, -Dave

1 0

Perms vs Settings
by DragonWize 06 Dec '08

06 Dec '08

Hi, I have a module that I has some display settings and I would like to make these settings per role. The easy way it seems to be to use the core perm system, however, I am not entirely sure that they really belong there. Is there and consensus or thoughts on what should be a perm vs a module setting. Thanks, Alan

3 3

Drupal 7 HEAD is broken!
by noreply＠drupal.org 06 Dec '08

06 Dec '08

Dev list, ALERT! HEAD was broken in commit #154495 (http://drupal.org/cvs?commit=154495) by webchick. ..-^~~~^-.. .~ ~. (;: :;) (: :) ':._ _.:' | | (=====) | | | | | | ((/ \)) I have decided to take my leave at this opportune time, thus testing will be disabled until this issue is fixed. Once HEAD has been fixed testing will automatically resume. Thanks, The humble test bot http://drupal.org/user/180064

6 6

Multi-instance Drupal Deployment
by Steven Surowiec 06 Dec '08

06 Dec '08

Hello all, I've using Drupal at lot at work lately and have some pretty big Drupal projects coming up and have been facing the same problem with all of the previous projects that I would like to get worked out before these new ones get going. And that is handling Drupal deployment in a multi-instance environment (multiple developers with local installs, a singular development server, a staging server and the production server). I can, and currently am, setting up Phing to do most of the work for me of handling SVN during the deploys and running any custom scripts. But the big hurdle is the database. Particularly the fact that there's a lot of admin-editable settings that are stored in various database tables. I was wondering if anyone else has had to deal with this before and any insight into the problem would help.

3 2

Re: [development] Drupal 7 HEAD is broken!
by Chad Phillips -- Apartment Lines 05 Dec '08

05 Dec '08

On Dec 5, 2008, at 12:28 PM, webchick wrote: > Um. > > a) I'm not sure how that is possible. Look at the diff. :P > b) That commit was back in November. About 500 commits and 800 > testing passes have been made since then, so obviously HEAD wasn't > broken after this patch. > > Can we please turn off the "ping of shame" functionality until we > get the bugs sorted out of testing bot? it _is_ off. it's been off. i have no idea where this came from, unless it was stuck somewhere two weeks ago and finally released from whatever cage it was in... :|

4 3

New maintainer sought for Comment Upload, Elements, Flatcomments, Taxonomy Defaults and User Badges
by Heine Deelstra 25 Nov '08

25 Nov '08

I seek a new maintainer for the following modules: http://drupal.org/project/comment_upload http://drupal.org/project/elements http://drupal.org/project/flatcomments http://drupal.org/project/taxonomy_defaults http://drupal.org/project/user_badges (others aren't worth continuing imo). If you are interested, please reply on the issue queue for the relevant project and I'll assign the projects. Kind regards, Heine Deelstra

1 0