June 2007 - Development - lists.drupal.org

GPLv3 is announced
by Erdem Köse 09 Jul '07

09 Jul '07

Are there any thoughts about releasing Drupal 6 with GPLv3[1]? [1] http://gplv3.fsf.org/

5 6

Code freeze reminder
by Dries Buytaert 05 Jul '07

05 Jul '07

Hello world, this is just a friendly note to let you know that it is less than 2 weeks until the code freeze (for real). I'm currently traveling, but I'll compile a detailed list of what I believe are important patches somewhere next week. In the mean time, the list mentioned in the last status update on drupal.org will do. At the top of my head are (no internet connection): 1. Various patches that improve performance and/or scalability. I'm specifically interested in (i) splitting SQL reads and writes and (ii) merging the node and node_comment_statistics tables. There are pending issues for both, spear-headed by David. There are other performance related patches too. 2. Various menu module fixes -- it's time to get these taken care of and to unleash teh chx and polowadin. ;) 3. Actions module patch that John is working on. I spent quite a bit of time reviewing this patch, as did Gabor and it is nearing completion. There is a couple of things we need to figure out still, but overall, it looks well on its way to get committed this week. 4. The module notification module that Derek and Earl are working on. 5. The node render patch that Eaton started work on a while ago. I don't think that is been committed yet, but Eaton recently reminded me about how important this is to further unify and clean-up the CCK and core. That should get us started! ;-) -- Dries Buytaert :: http://www.buytaert.net/

22 55

Re: [development] Go PHP 5, Go!
by Karen Stevenson 05 Jul '07

05 Jul '07

One more thought on this subject, why not add 'minimum php version' to the .info file, and show modules that require php5 as disabled on the modules list if php5 isn't available. This would be a fairly simple thing that could still be slipped into 6.x that would allow us to start creating contrib modules that require php5 and get users thinking about the advantages of php5 so they start putting pressure on hosts to upgrade. Native timezone support didn't start working until 5.2, for instance, so the version check should test both major and minor version numbers. And add php version info to the module download page, too. Karen

9 9

seeking helper and tester for drupal-6.x-dev oracle driver
by Edison Wong 04 Jul '07

04 Jul '07

Dear all, My team is now developing the oracle driver for drupal-6.x-dev, please refer to http://drupal.org/node/39260 for detail information. We face a great problem: without tester, we can't prove the correctness of our product. I wrote a mini-HOWTO about how to let Debian etch, Oracle Database 10g Release 2, Apache2.2, Zend Core for Oracle v.2 and drupal-6.x-dev all works together. Hope this can decrease the difficulty so volunteer may find easier to help the successful of this project. Please refer to the following links for more information :D latest drupal-6.x-dev oracle driver: http://drupal.org/node/39260 drupal-6.x-dev + Oracle Database 10g Release 2 mini-HOWTO: http://edin.no-ip.com/html/?q=drupal_6_x_dev_oracle_database_10g_release_2_… Oracle Database 10g Release 2 + Apache2.2 + Zend Core for Oracle v.2, on Debian etch HOWTO http://edin.no-ip.com/html/?q=oracle_database_10g_release_2_apache2_2_zend_… Regards, Edison Wong

2 1

Go PHP 5, Go!
by Larry Garfield 02 Jul '07

02 Jul '07

This is a follow-up to the PHP 5 thread from a week or two ago. It looks like some momentum is building. Ken Rickard, Robert Douglas, and I have been talking with some of the Jooma folks, and have a working draft of the "core statement and justification". That is, what the goal is and why it is. Joomla's development team is discussing the matter and is leaning yes. Based on the earlier thread here I am hoping that there isn't much objection to Drupal participating in the "Go PHP5" effort. :-) So far Joomla is leaning yes, CakePHP is interested, and I had a positive first response from Typo3. Robert Douglas has volunteered himself to setup a web site for it. I'm not sure how Dries wants to handle the question of Drupal's participation (by vote, by consensus, or by fiat). Dries? Anyway, here's the working statement. Consider this an official recommendation that Drupal commit to participating in this effort. ------------------------------------ PHP 4 has served the web developer community for seven years now, and served it well. However, it also shows its age. Most of PHP 4's shortcomings have been addressed by PHP 5, released three years ago, but the transition from PHP 4 to PHP 5 has been slow for a number of reasons. PHP developers cannot leverage PHP 5's full potential without dropping support for PHP 4, but PHP 4 is still installed on a majority of shared web hosts and users would then be forced to switch to a different application. Web hosts cannot upgrade their servers to PHP 5 without making it impossible for their users to run PHP 4-targeted web apps, and have no incentive to go to the effort of testing and deploying PHP 5 while most web apps are still compatible with PHP 4 and the PHP development team still provides maintenance support for PHP 4. The PHP development team, of course, can't drop maintenance support for PHP 4 while most web hosts still run PHP 4. It is a dangerous cycle, and one that needs to be broken. The open source PHP developer community has decided that it is indeed now time to move forward, together. Therefore, the listed open source PHP projects have all agreed that effective 5 February 2008, any new feature release will have a minimum required PHP version no older than PHP 5.2.0. It is our believe that this will allow web hosts a reason to upgrade and the PHP development team the ability to retire PHP 4 and focus efforts on PHP 5 and the forthcoming PHP 6, all without penalizing any existing project for being "first out of the gate". ------------------------------------ Notes: - I chose the date because I figure that will be 7-8 months after we officially announce this thing, which I believe should be sufficient time for web hosts. It also comes out to 5/2/2008 (using European convention), and I just like inside references like that. :-) - This does not preclude any project from moving before the deadline date, or from supporting older versions for however long they wish to. That's up to each project. - PHP 5.2 is already the most widely installed version of PHP 5, based on the latest published stats. I know at least two web hosts I work with that either have jumped or are in the process of jumping from PHP 4 straight to PHP 5.2. By the target date it will have been out for nearly a year and a half. It also adds a number of new and useful core features (filter_input, json, a stable PDO, etc.). It's a good version to target. Thoughts? Comments? Support? Rotten tomatoes? -- Larry Garfield AIM: LOLG42 larry(a)garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson

41 122

taking a break
by Karoly Negyesi 02 Jul '07

02 Jul '07

When some patches are more equal than others, I just can't continue. If one of my patches had only tenth the code style errors actions patch had (and I am not talking of the critical bug it has, it's not easy to see albeit module_implements had a five line long comment over the same bug) there would have been no chance that patch got commited. I complained long and hard in the issue queue over the years for helding up this or that important feature over a space or two. Neither the book patch nor the menu fixes are in despite they are tested and supported. I guess my life is so entwined with Drupal that I won't be able to stay away for long. Anyways, I will take a few days break. Regards, NK

6 12

very simple D6 feature patches
by Peter Wolanin 30 Jun '07

30 Jun '07

Here's a quick compilation of very simple feature requests for D6. They have no more than 10 lines of code changed (excluding comments) and are already marked as RTBC. If you have time, do a review and offer your support (or criticisms) before the code freeze hits. Add more or cross them off as needed: http://groups.drupal.org/node/4943 -Peter

1 0

Patch: path.module performance improvement
by Wim Leers 30 Jun '07

30 Jun '07

Hi, yup, yet another desperate call for review. I just need another small review to get this patch (hopefully) marked as RTBC. It has been tested thoroughly already! What does it do? - how: provide the ability to use no optimization at all, a blacklist or a whitelist of Drupal paths, to reduce the number of queries drupal_lookup_path() has to perform - default: a very safe blacklist - UI: none, to avoid confusion for the average user. The UI will be provided by a contrib module. - performance improvement: from 55.07 reqs/sec to 61.46 reqs/sec, which is 11.6% more (using the default). These numbers come from benchmarks that you can see in follow-up #72. The total number of queries per page dropped about 20% (absolute numbers: between 10 and 100 less queries). Of course this all depends on your setup. Conclusion: - this patch gives a "free" performance boost to all path.module users, the difference will be larger for more complex sites - if you're knowledgeable enough to use the UI for this module, you can increase that performance gain even further Link: http://drupal.org/node/106559 Wim Leers

1 0

Book module: should it get in?
by dmitri 30 Jun '07

30 Jun '07

The book module patch does not turn book module into anything it is not ATM. It simply brings it back up to date with what we now have at our disposal (node api and menu api). The book module as it stands now is lacking updates for several years, and so it is based on old code that can be done much more simply now. http://drupal.org/node/146425

1 0

Multilingual Drupal?
by Jose A. Reyero 30 Jun '07

30 Jun '07

Hi, Yes, this is one more of the last-minute -desperate- calls for help about patches in queue for Drupal 6 ... So far, we've made a lot of progress with multilingual features for next version. But there are still a lot of elements that cannot be localized or translated, too many for us to say yet "Drupal is multilingual". This is a very minimum set of -small- patches we'd need, most of them not to have it fully implemented in Drupal core, but to allow contributed modules to hook in and do the job. Then we'll be able to pick the best solutions and fully implement the features, maybe in Drupal 7... - Minimum support for multilingual variables, http://drupal.org/node/155381 Just a few lines of code in variable_get() - Object translation wrapper, http://drupal.org/node/155047 Wrapper for content types, aggregator categories... to allow translation before displaying them - Send e-mail to users in their language, **http://drupal.org/node/82499 Simple mail callbacks to send email in the users language. This is the biggest one on this list. - Adding db_rewrite_sql to blocks query, http://drupal.org/node/155282 One line patch to allow blocks per language And if you have the time, here's the full list with some other features that would be nice to have: http://groups.drupal.org/node/3714 Thank you, Jose A. Reyero

1 0