July 2007 - Development - lists.drupal.org

Help fix Actions API - test the patch!
by Jeff Eaton 31 Aug '07

31 Aug '07

The Actions API is now officially part of Drupal 6, and it's a tremendously powerful addition that (I think) will bear lots of fruit over the D6 life cycle. Things like custom workflow management solutions, streamlined application-specific user and content administration panels, and so on are all easy to build on top of the Actions API. However, the current implementation has a couple of subtle issues that cripple it for broad use. Our pattern for core constructs (menus and paths in particular) is to provide a foo.inc file that exposes a core API, and an optional foo.module that provides additional advanced customization options. Actions in D6 follows this pattern, but there appear to be a number of unintentional dependencies between the .inc file and the .module file. Specifically, action-related tables are never created, and action data is never initialized, until actions.module is installed. This means that actions.module -- which is only ONE possible application of the Actions API, and one that is unnecessary for many sites -- becomes an absolute requirement. Webchick and I have built a patch that fixes this, moving the truly core actions API functions into the .inc file, moving one setup screen into system.module, and keeping the advanced hook-to-action mapping UI in the optional actions.module. The patch also fixes a number of schema related issues and code style problems that chx has pointed out in the past. I'd encourage everyone who's interested in a powerful and flexible Actions infrastructure to check out http://drupal.org/node/155828 ;-) Thanks!

3 6

Drupal 5.2 and 4.7.7 released
by Neil Drumm 04 Aug '07

04 Aug '07

Killes and I have released Drupal 5.2 and 4.7.7. These are bugfix and security releases; upgrading is strongly recommended. Further details are at http://drupal.org/drupal-5.2 The CVS tags are DRUPAL-5-2 and DRUPAL-4-7-7 The direct downloads are http://ftp.drupal.org/files/projects/drupal-5.2.tar.gz http://ftp.drupal.org/files/projects/drupal-4.7.7.tar.gz Thanks goes to the security team, everyone who reported and reviewed security issues, and everyone who worked on bugs. -- Neil Drumm http://delocalizedham.com

8 16

#drupal / #drupal-dev split considered harmful
by Angela Byron 03 Aug '07

03 Aug '07

A couple weeks ago, a few developers started going into #drupal-dev instead of #drupal and started a campaign to get people to split off. I guess the reasoning for this was because they disagreed with newbies who didn't read the topic getting 'support?' in their face when they join our "official" channel. I personally think it is a feature, and not a bug, that our main channel is contribution-focused rather than support-focused, but that is largely irrelevant to the topic at hand. The problem is that the people who started this 'fork' have not been present in #drupal, actively taking part in support requests from newbies, thus changing the 'mood' of the channel by their own words in actions. Instead, the main channel's merely been abandoned by several very prominent contributors, a large portion of the development community doesn't even realize there's a separate channel, development discussion in general is now splintered between the channels, and newbies are still getting 'support?' in #drupal. The climate in the 'official' channel right now is more that of a ghost town of join/part messages, except for random musings about the infrastructure and, of course, 'support?'. This gives the exact opposite impression to new Drupal users than the channel did before the split -- a vibrant community of developers sharing issues or patches to review, talking about new modules they're developing, etc. So please, #drupal-dev goers, either finish what you started by actively working in #drupal to make it more newbie-friendly, or abandon the experiment. So far, this feels like a net loss for the community. -Angie

15 30

jQuery animation help?
by Morbus Iff 02 Aug '07

02 Aug '07

G'day. I'm using the wrong list. Woohoo! I have a DIV full of lots of items. Images, more DIVs, more images, words, sentences, whee, fun, fun. It is a large DIV. I'd like: * on page load, for the DIV to show at (smaller) px x px. * on mouseover/hover, the DIV to enlarge to (full) px x px. * on mouseout, the DIV goes back to its onload size. * everything in the DIV should resize - the images should get bigger, the fonts should get larger and smaller, blah blah. What is /really/ close is the Grow/Shrink/Puff of Interface: http://interface.eyecon.ro/demos/ifx.html However, I can't make it NOT disappear, and the interface.js can only be found in a packed state, not one I can look into the source about how to stop it from disappearing. (Note, also, that the Interface demo is onclick, but I'd be looking for over and out). 'elp? Morbus Iff morbus(a)disobey.com Not my normal computer

4 5

Changes to CVS tagging/branching conventions for contrib (MUST READ)
by Derek Wright 31 Jul '07

31 Jul '07

Hello world, ------- Summary ------- 1) Starting with Drupal 6.x, branches in the contributions CVS repository will always contain the --N part of the branch name, to remind people that each release series belongs in its own branch. You can now create a DRUPAL-6--1 branch for the 6.x-1.* release series for your contributions. There will never be a DRUPAL-6 branch in the contributions repository (the repository itself prevents it). If you're Jeff Eaton and you already have 2 versions of your D6 modules ready ;) the 6.x-2.* code belongs in HEAD or in the DRUPAL-6--2 branch (also now open), not in DRUPAL-6--1. This change is only for DRUPAL-6--1 and beyond, the DRUPAL-5 branches in contrib are unaffected. 2) If you make "beta" or "rc" releases, the "extra" part of your tag can only contain upper case letters and numbers (no lowercase, hyphens, underscores, etc). So, these are valid: DRUPAL-6--1-0-BETA DRUPAL-6--1-0-BETA1 DRUPAL-6--1-0-RC1 These are not: DRUPAL-6--1-0-beta DRUPAL-6--1-0-BETA-1 DRUPAL-6--1-0-Beta-1 DRUPAL-6--1-0-RC_1 DRUPAL-6--1-0-rc1 Old tags that don't follow these rules will continue to exist. However, new tags, even for DRUPAL-5--*, will be disallowed if they don't match the new convention. ---------- Background ---------- More info about why I made these changes are here: 1) http://drupal.org/node/147493 2) http://drupal.org/node/147494 Discussion is now closed, but these contain a lot of good wisdom and motivation. If you have any doubts, please read these issues carefully and your concerns will almost certainly be addressed and resolved. --------- Handbooks --------- The following handbook pages are updated to reflect the new reality: http://drupal.org/handbook/cvs/quickstart http://drupal.org/handbook/cvs/branches-and-tags/contributions http://drupal.org/node/17570 I also updated the Contributed modules status - version 6.x wiki on g.d.o: http://groups.drupal.org/node/5036 If you happen to find another CVS handbook that has stale info, please either fix it yourself if you can, or create a documentation issue about it if you can't. Otherwise... Reply-To: /dev/null ;) Happy D6 porting! Cheers, -Derek (dww) p.s. Did I mention that this email is about changes that already happened which are no longer up for debate? This is not an RFC or proposal soliciting feedback. If you reply to this thread with "why did you do that?" or "I liked it better the old way..." you'll make a certain CVS admin very unhappy... and bad things happen when you do that. ;) If you think you don't like either of these changes, read the issues I point to above very carefully. If you still think these changes are a mistake, please find someone else to complain to, since a) you're wrong and b) I don't want to have to tell you that again. ;)

1 0

Issue followups as comments
by Karoly Negyesi 30 Jul '07

30 Jul '07

Hi, If you have _ever_ followed up on an issue and found anything unsatifactory, now is the time to do something: review http://drupal.org/node/18920#comment-281277 (#28) Regards, NK

1 0

drupal down?
by Ashraf Amayreh 29 Jul '07

29 Jul '07

Is it me or is drupal.org currently down? It's showing the following error message:** "Host 'drupal2.drupal.org' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'." I read the email on downtimes and I don't believe this is one of them. AA

3 2

DAST - What tests would you like to see
by Allister Beharry 29 Jul '07

29 Jul '07

The 0.2 DAST release is going to feature automatic code testing using SimpleTest. The goal of this feature is to create a repeatable process for verifying code behaviour. A batch of unit tests can be run against against core HEAD, or core HEAD + module or core HEAD + module + patch or any Revision + module + patch...In addition to the 11 tests that ship with the simpletest module, I've been perusing the issue queue and picking out several patches, as well as some basic db tests for the current MSSQL and Oracle drivers. If you're an issue owner or a module maintainer, what tests would you like to see? Think of the tests you now do manually - what test do you wish could be automated? While you're at it, check out the project at http://www.drupal.org/project/DAST if you haven't yet - I'd love to get some feedback on it. Allister -- Muppet Show > Monty Python

3 2

Outages next week
by Gerhard Killesreiter 28 Jul '07

28 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, next week there will be two short outages of our infrastructure: CVS outage (rebooting drupal3 for RAM upgrade) Monday July 30th 0900 PDT / 1600 UTC / 1800 MEST (30 min) Site-wide PHP5 Upgrade Window Wednesday August 1st 0900 PDT / 1600 UTC / 1800 MEST (30 min) I'll announce the second one on the frontpage as well. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGqxhcfg6TFvELooQRAmWWAKCyz+dURRmE9IdP8n/sjXBFP+S1egCfZvyt Z0aQWApi/Ep4UiUmF27gyQs= =v81w -----END PGP SIGNATURE-----

2 1

What is gid in node_access table when realm = 'term_access'?
by Ron Parker 27 Jul '07

27 Jul '07

The Drupal site has been up and down periodically today as I try to work through this issue. I've got the case_tracker module installed. I created a case node, then went out to see what grants were written into the node_access table for the node. I only saw entries with realm = 'term_access', but don't recognize the gid numbers (they don't seem to logically relate to vocabulary term or group ids in my system). So, I began searching Drupal and the internet trying to find out the answer to this question: What is the "gid" value in the node_access table referring to when the realm = 'term_access'? Can anyone explain or point me to a resource that will explain it? Thanks! -ron -- Ron Parker Software Creations http://www.scbbs.com Self-Administration Web Site http://saw.scbbs.com SDSS Subscription Mgmt Service http://sdss.scbbs.com Central Ave Dance Ensemble http://www.centralavedance.com R & B Salsa http://www.randbsalsa.com

3 3