February 2009 - Development - lists.drupal.org

FYI: "Assigned to: foo" is now opt-in for [#12345] issue link filter
by Derek Wright 03 Feb '09

03 Feb '09

Hello world, As most of you hopefully already know, if you type: [#367423] into any page on drupal.org, it will automagically be replaced with: #367423: Make "assigned to" on issue links opt-in (by appending '@') where the whole thing is a link to http://drupal.org/node/367423 If you want to reference comment 15 in the issue, you do this: [#367423-15] and you get a link to: http://drupal.org/node/367423#comment-1233127 Recently, there was a change to the theme on d.o to color the whole thing by the issue status (yay) and to append "Assigned to: foo" afterwards (occasionally yay, mostly boo). This was causing lots of clutter, and some people have either stopped using the filter, or stopped assigning issues, just to avoid the extra noise. This behavior is now opt-in when you write the issue reference. If you want "Assigned to:" to display, you include an '@' after the issue or comment number, like so: [#367423@] Which would yield: #367423: Make "assigned to" on issue links opt-in (by appending '@') Assigned to: dww Otherwise, you get the old behavior (plus the new per-status coloring). Oh, and if you leave off the '@', if the issue is assigned to someone, that's visible in the title attribute if you mouse over the link. Enjoy, -Derek (dww)

3 2

Virtual Code Sprint on Internationalization in Drupal core (starting today)
by Jose A. Reyero 03 Feb '09

03 Feb '09

Hi all, Just in case you don't know yet, we'll be having a Virtual Code Sprint on Internationalization in Drupal core. We are going to focus our efforts for a short period of time on trying to move on with a lot of critical issues and features to get better multilingual support in Drupal 7. It starts today (Tuesday) at 16:00 UTM. It will take place on Feb. 3 - 4 and Feb 10 - 11. The list of issues we'll be focusing on (tagged with 'i18n sprint') is here, http://drupal.org/project/issues/3060/term/301 So if you are interested on multilingual Drupal and want to participate, please sign up for http://groups.drupal.org/node/18443 ============= Sprint logistics ============= The sprint will be held in IRC in #drupal-i18n. We'll also move at times into #drupal-devel when we need to find other developers to get tips on particular problems. The sprint will begin at 16:00 UTM on both Tuesday Feb. 3. This timing is to enable the organizers, located in Europe and North America, to get things going. We'll continue past midnight UTM, partly to enable Angie Byron (the D7 core maintainer) to check in when she's available. You're welcome to participate for as much or as little of the sprint as you can fit in. During the sprint we'll agree on a time to start on Feb. 4 and post this to the event post. It may be earlier than 16:00 UTM to make it easier for participants in Europe, with North American participants joining in later. If you're new to IRC, see this page: http://drupal.org/irc Cheers, Jose

1 0

Join me on Bebo
by Daniel Zhou 03 Feb '09

03 Feb '09

I think you will like it. Click to find out why You also have the following outstanding friend requests: Jason Nunnelley <jason(a)jasonn.com> You can accept or reject all of these invitations at once by clicking below: http://www.bebo.com/in/5390459004a252527358b135 ...................................................................... This email was sent to you at the direct request of Daniel Zhou <danithaca(a)gmail.com>. You have not been added to a mailing list. If you would prefer not to receive invitations from ANY Bebo members please click here - http://www.bebo.com/unsub/5390459004a252527358 Bebo, Inc., 795 Folsom St, 6th Floor, San Francisco, CA 94107, USA.

2 1

Remove top-level admin menu items
by Daniel F. Kudwien 02 Feb '09

02 Feb '09

This goes out to some maintainers, specifically related to - Notifications / Messaging - Organic Groups - Panels Those and related/dependent modules are implementing top-level menu items, e.g. - admin/messaging - admin/og - admin/panels in the style of Drupal 4.7, instead of using the new administrative categories and structure we have since Drupal 5.x. This is not only confusing, but also clutters the administrative interface - especially, if Administration menu module is installed. I see no reason why it needs to be this way. Clearly, for example, Organic Groups and Panels are both tools to build a Drupal site -- the proper location would thus be below "Site building". In the special case of Notifications/Messaging, the situation gets even worse: It mixes administrative items for different purposes into one top-level item, meaning that permanent site configuration settings and continuously required administrative functions are located in one, bloated container with no clear distinction. Furthermore, granting administrative users the permission to administer user subscriptions will expose a new top-level menu item "Notifications & Messaging" to them -- the proper location for managing user subscriptions would be below "User management". Unfortunately, my request for changing this in Notifications was immediately won't fixed [1], which is why I see the need for a broader community consensus. I know that a change like this could probably only done in upcoming major versions of all affected modules. If the only thing that prevents this from changing are patches, then I'll happily submit some. Thanks, Daniel [1] http://drupal.org/node/366489

13 17

Weird D5-D6 upgrade accident - need for taxonomy ninja feedback
by Tomáš Fülöpp (vacilando.org) 01 Feb '09

01 Feb '09

Hi, I'd hate to bump an issue via this list but I am stuck in what was to be a straightforward upgrade and my critical issue at http://drupal.org/node/365664 * has not received any reply for a number of days * might point to a generic problem people encounter when upgrading from D5 to D6 * does not seem to be answered by any post in the upgrade or other forums (or I haven't found one) Basically, after upgrade the ID of the Forum's vocabulary has, for mysterious reasons, changed... and the new ID has no terms in it, which means the Forum is empty and all issues that were posted in the D5 version are stranded in limbo. Why did this happen in the first place? / Can it happen to others? And how to fix it? It probably won't take more than 3 minutes of attention for a Drupal taxonomy (or upgrade?) ninja. Thanks! Tomáš PS: For your convenience, here's a copy of what I posted in the above issue, but please answer via the above post (http://drupal.org/node/365664) (if your answer does not benefit the development thread). *I've upgraded from 5.15 to 6.9 but there is nothing in my forum. I've found out that the vocabulary containing forum categories is there, but it is NOT ATTACHED to the vocabulary of the upgraded D6 forum! Practically, my D5 vocabulary had name 'Forum' and ID 1 and it is still there in D6, but in D6 the forum is using newly created vocabulary (also called 'Forum') with ID 15! As result the /forum shows nothing and all our old forum messages are still there, but because they are tagged in the old forum, they do not show anywhere. Why did this happen - anybody knows? And how to rectify it... I guess all that could help would be a way to assign vocabulary 1 to the forum in D6 -- but how to do this? Please help... *

1 0

Fields in core patch
by Dries Buytaert 01 Feb '09

01 Feb '09

Hello all, I will commit the initial Fields in Core patch for D7 (http://drupal.org/node/361683) on Tuesday at 5pm CET (11am EST). Read: two days left, act now ... -- Dries Buytaert :: http://buytaert.net/

1 0