February 2006 - Development - lists.drupal.org

Do you want early access to 4.6.6?
by Karoly Negyesi 23 Feb '06

23 Feb '06

You don't even need time to test the patch! You just apply it on your production site, the bigger, the better and sit back. If it breaks stuff, you undo the patch. If it works, you report back success after a day of testing. In other words, we are pretty confident it's release worthy. On the other hand, we do not want to release something bad. So please help us in testing. Thanks Karoly Negyesi Ps. Yes last time we should have done the same. It's never late to correct yourself though :) .

5 5

"I'm disappointed by the freeze"
by Dries Buytaert 23 Feb '06

23 Feb '06

On 20 Feb 2006, at 10:29, Bèr Kessels wrote: > Updated by: Bèr Kessels > > Personally I am getting more and more dissapointed by the actual > "frozenness" of HEAD. So if nothing changes in the current behaviour, > why should this issue wait? Ber, you can stop sprinkling "I'm disappointed by the freeze"- messages all over drupal.org. There is no need to attach them to each issue you update. Let's use the issues for technical discussions rather than for spreading FUD. Thanks. We can continue to discuss this in a central place (this mailing list, this thread) if you wish. -- Dries Buytaert :: http://www.buytaert.net/

8 17

Re: [bug] fix locale and admin/node search form goto bugs
by Karoly Negyesi 23 Feb '06

23 Feb '06

> (Beh, more form attributes.) Oh and I want one more for 4.7 ... see the form caching patch which I think is mandatory because of performance. Moshe volunteered to bench it. drupal.org/node/38798

1 0

Re: [development] Refresh Drupaldocs.org?
by Vince Do 23 Feb '06

23 Feb '06

OK, great! Thanks for the replies and resources. Vincent

1 0

Re: [development] google just pwned the brochureware site industry
by Theodore Serbinski 23 Feb '06

23 Feb '06

"Don't worry about saving" Google Page Creator saves your changes automatically as you type, so no more nervous breakdowns from losing all your work. I posted this one a while back: http://drupal.org/node/25463 It's hot. It certainly is. > On 2/23/06, Adrian Rossouw <adrian(a)bryght.com> wrote: > > http://pages.google.com > > > > Go play with the site editor, that's how our themes should work damnit.

1 0

Refresh Drupaldocs.org?
by Vince Do 23 Feb '06

23 Feb '06

Hello, That's my first message here, so I seize the opportunity to congratulate all of you on the great work with Drupal. The more I use it, the more I like it!! I'm currently developing against the HEAD version and I've noticed the documentation at http://drupaldocs.org/api/head is not in sync with the files from CVS. Would that be complicated to re-generate it (once in a while)? I know you're all very busy, I'm only asking because I believe this documentation is generated automatically. So maybe it's just a matter of pressing a button somewhere? That'd be very helpful for newbie Drupal developers (like me) who otherwise get confused by believing the pages are current and end up asking stupid questions (like me) in the forums. At the end of day, I'm sure you'd have less of these questions and therefore more time! :-) Thank you, Vincent

4 3

disable contribs on updates. or not: chicken egg;
by Bèr Kessels 23 Feb '06

23 Feb '06

Hi, http://drupal.org/upgrade/ speaks about updates that *exclude* any contribs or custiom modules and themes. A general consensus is to upgrade without your custom code. Makes sense. Made sense, its getting hairy. With the new .install files and with the menu-a-primary links upgrades (requires to read the the prim/sec links, see http://drupal.org/node/49501) we have a problem, Houston. If I upgrade my site without my custom modules and themes: the proper code (par example the proper theme settings) are not read. Resulting in dataloss (redoing seven primary links is not /that/ much work, but still). If I upgrade my site with my custom modules and themes enabled and installed: the update will most probably fail because of PHP issues (like function not found: some_removed_core_function) If I cannot upgrade my site, I cannot upgrade my modules, because my (development) site needs to be upgraded before it can be a test-bed for my upgraded module. So, what to do? How to properly document this *before* the 4.7 release? I think this is purely a docs issue, its too late to fix this with code. My shot would be to say in the manuals: * For Developers and maintainers of modules: please use a clean database, and use the generate modules to create data to update and test your module with/for 4.7 * For Joe Schmoe: move all your stuff to a backup. Then put a new 4.7 in place. Then put the released 4.7 modules you had in 4.6 in your /modules. Then do the same for themes. Then run the upgrade. * For Consultants and hosts: find some fancy way with symlinks, secondary IPS, database hotcopies, and dev/test subdomains. If you cannot, you shouldn't be running such a host :) Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]

2 1

Module Builder Module 1.0
by Angie Byron 22 Feb '06

22 Feb '06

At DrupalCon, a few of us had talked about how handy it would be to have a module that automatically generated "scaffolding" for modules, both to help new developers as well as to speed up the process of creating custom modules for Drupal veterans. As a result of a major bout of insomnia, I am pleased to announce that Module Builder Module 1.0 has been committed to CVS, and even pretty much works! ;) You can check it out at: http://cvs.drupal.org/viewcvs/drupal/contributions/modules/module_builder/ WARNING: This module was a lot of 3am++ code and regular expressions, which as we all know is a deadly combination, so please be kind. ;) There's obviously a lot more that can be done with this than what's there now, but I figured I would post this anyway so people can see how it works so far. Jeff Robbins also created a wireframe (which I tried to use as inspiration to the extent that I could) of how he envisions this working in later revisions, which you can see in my sandbox here (warning: PDF): http://cvs.drupal.org/viewcvs/*checkout*/drupal/contributions/sandbox/webch… Anyway, enjoy! -Angie

15 26

define critical bug
by qomo 22 Feb '06

22 Feb '06

I suggest we define what a critical bug is, so that we don't have too many reported. Yesterday I saw a thread where a developer downgraded a critical bug to normal, and the user said it seems critical to her. (something like drupal wouldn't process dates for an event before 1970.) chx and dries' exhortations have really brought down the number of bugs, which is great. however, to get down to zero, we need to clear them out faster than they are being reported. Ann

1 0

MySQL performance tuning snippet
by Kieran Lal 22 Feb '06

22 Feb '06

Hi, we are looking for some feedback on developing more performance tuning snippets. Please try this out: http://drupal.org/node/50291 This should work in a MySQL 4.0 and 4.1 environment. I got a chance to spend some time with Brian Aker, the head of architecture for MySQL, again today. He suggested we use InnoDB for large sites and that we investigate using Archive table types which are designed specifically for tables like accesslog in Drupal. Apparently they had some significant performance improvements at Yahoo, LiveJournal, and Slashdot. Cheers, Kieran

3 2