April 2007 - Development - lists.drupal.org

Cannot create 6.x release of module (was Re: watchdog -> dblog + syslog)
by Khalid Baheyeldin 10 Apr '07

10 Apr '07

On 4/10/07, Derek Wright <drupal(a)dwwright.net> wrote: > > > > compatible with HEAD (no nightly builds, because there is > > no 6 tag yet, but get it through CVS or the Browse CVS link. > > FYI: you don't need a DRUPAL-6 branch to make a development snapshot > release that's compatible with 6.x core. just make a release node > and use "HEAD" as the CVS branch, set it to "6.x" core compatibility, This is where the problem is. I don't have 6.x listed. I only see None, 5.x, 4.7.x, and 4.6.x only in the select box. So, I can't select 6.x. and give it a major number of "1", a patch level of "x", and an extra > identifier as "dev". viola, a 6.x-1.x-dev development snapshot from > HEAD. then, whenever you make the DRUPAL-6 branch, you can just edit > this release node and you'll now have the option to move the CVS > branch from HEAD to DRUPAL-6. no, you don't need any special > permissions on d.o for this -- anyone who can edit the release node > can move it from HEAD if there's now a CVS branch that doesn't have a > release node but that specifies the same version information. after > that "HEAD" will again be an available choice when creating new > release nodes, e.g. for the initial 7.x port, or as a 6.x-2.* new > feature series. > > so long as you give the HEAD release node a version number that > *could* someday be its own branch (i.e. major number >= 1), you can > always move a HEAD release node to the appropriate branch once that > exists. see http://drupal.org/node/89699 for more. > > someone should really update http://drupal.org/node/17570#HEAD with > this wisdom. any volunteers? ;)\ > -- 2bits.com http://2bits.com Drupal development, customization and consulting.

2 1

Re: [development] Multilanguage
by Fernando Cosso 10 Apr '07

10 Apr '07

On 09/04/07, Chris Bryant <chris(a)aliandesign.com> wrote: > > > > On Mon, 2007-04-09 at 18:37 -0300, Fernando Cosso wrote: > > Hi > > I am planning to migrate to Drupal and I wanted to know if the system > > supports multilanguages pages. > > Best Regards > > I'm not sure that the development list is the right place to ask this > question, maybe the support mailing list, forums, or IRC would be > better: > http://lists.drupal.org/listinfo/support > http://drupal.org/forum/18 > http://drupal.org/node/108355 > > The quick answer to you question is to look here: > http://drupal.org/project/i18n > > Good luck, > Chris > > I will check it out thanks -- yo(a)fernandocosso.com.ar http://www.fernandocosso.com.ar

2 1

List Etiquette Question
by Doug Green 10 Apr '07

10 Apr '07

When responding to questions on this list that reference issues, is it better to: (a) comment against issue only (even when it is marked as closed or fixed) (b) send email to the author only (c) send email to the entire list I just sent two such questions to this list, and am questioning whether that was the correct list etiquette. Doug Green 904-583-3342 www.douggreenconsulting.com Bringing Ideas to Life with Software Artistry and Invention... Providing open source software political solutions

1 0

Question regarding the edit array
by Richard Morse 10 Apr '07

10 Apr '07

Hi! In Drupal 4.7.x, form items were placed into an 'edit' array, so that if you wanted to get at items, you could do $_REQUEST['edit'] ['field_name']. In 5.x this has changed. Was there discussion about this somewhere? I can't find anything in the mailing list archives, or in the forums. (This might be because searches about 'edit', 'array', and '$_REQUEST' are pretty much worthless...). I ask because it seems like it could be a problem -- suppose your form redefines 'q', (or 'sort', or 'order', or 'destination') for its own purposes; if I'm using GET queries, this could become a huge issue... Thanks, Ricky The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.

3 2

Re: [development] PDO and database limitations
by Gabriele Turchi 10 Apr '07

10 Apr '07

Currently I'm doing an experimental Oracle port, and for that need I've done a quick travel in the drupal code... Frankly, I don't think PDO could be a solution for a better database portability, at least in drupal. From what I've seen, the database usage is pretty plain (some "create" in ".install" and mostly simple (only some table involved) "select", "insert" and "update" - or, better, "upsert" in the code). My first feeling was to create a very light db persistence layer, based on php dynamic object creation (__get and __set): define a class with an array on info like: name, type (number, text, large text and blob), is (part of) primary key, is indexable. Do a mapping into a "create table" should be easy. The actual common usage of "db_fetch_object" may be left more or less unchanged, simply creating queries asking what fields from what table with what filters. The "join" case can be simplifyed using views. About the db_num_rows question: there are more than a good reason to avoid it. As an example, the default behavior for the postgresql driver is to fetch in memory _all_ the results before returning the first one to the caller: with big tables this is simply devastating (and can be removed from future releases). And Oracle simply doesn't support it. My 2cents... Best Regards, Gabriele Turchi P.S.: I'm sorry, my english il alpha version...

3 3

A Survey on Defect Management Practices in Free/Open Source Software
by Anu Gupta DCSA 10 Apr '07

10 Apr '07

Dear Drupal Contributors, I seek help from designers, developers, testers,defect fixers,project managers or playing any other key role in Free/Open Source software development or maintenence in carrying out a study on practices and problems of defect management in various Free/Open Source Software projects. The insights gained from the study can further help us to extract publicly accessible defect data and determine impact of defect management practices on software quality. Please spend a few minutes of your precious time to fill up the Questionnaire. The most of the questions follow multiple choice formats and are quite easy to answer. To have the Online Questionnaire, please visit: http://anu.puchd.ac.in/phpESP/public/survey.php?name=FOSS_Defect_Survey (You can also copy and paste this link into your browser, and hit the 'Return' key.) I hope you will find all the questions interesting and thought-provoking. Your answers will be kept anonymous.The data thus collected will only be used for research purpose.It would be nice if you may further refer this mail to others actively engaged with Free/Open Source Software development. If you have any query or suggestions then feel free to contact. Thank You With regards, Anu Gupta Senior Lecturer Department of Computer Science and Applications, Panjab University, Chandigarh. INDIA In case of any problem in accessing/using the above mentioned link please contact: E-mail: anugupta(a)pu.ac.in anugupta98(a)gmail.com

1 0

Oracle porting & db_num_rows patches
by Gabriele Turchi 10 Apr '07

10 Apr '07

Hi all. I'm doing a drupal 5.1 Oracle db experimental port. I have a first core installation more or less working. Next target will be cck and views. One problem was the need to remove the db_num_rows calls (unavailable in Oracle). I've seen here and there an inappropriate use of this function ("select *" and db_num_rows in place of "select count(*)"), and I think my patches can be useful also for performance under other databases. I'll be glad to submit my patches. In case, tell me the best way to do so, I'm new to the drupal project. Best regards, Gabriele Turchi P.S.: I'm sorry, my english il alpha version...

4 4

Expanded menu items
by Karoly Negyesi 10 Apr '07

10 Apr '07

Hi, I do not see myself reimplementing them. If this is a feature you need, well, now is the time to join the menu coding -- it's plain Drupal PHP code, commented, documented and in case you have questions, I am here. If noone stands up, well, that's a problem. Unlike my last mail which contained critical issues, and at the end, I did two out of three (thanks for helping on the localization folks) this is just a feature. Regards, NK

1 0

Multilanguage
by Fernando Cosso 09 Apr '07

09 Apr '07

Hi I am planning to migrate to Drupal and I wanted to know if the system supports multilanguages pages. Best Regards -- yo(a)fernandocosso.com.ar http://www.fernandocosso.com.ar

1 0

form API -- call for feature requests
by Karoly Negyesi 09 Apr '07

09 Apr '07

Hi, Your dreams coming true: I am asking for feature requests regarding form API in private mail. Please only apply if you have tried coding something and it was awkward and hard. I guess multistep will be high on the list :) I am flying to Chicago on April 21 and I will stay there until May 1. The sole reason for this detour to Illinois is to get together after work with Eaton and work on form API. Sorry Adrian, you are way too far to make a short detour on the way home :) Regards, NK

2 1