Drupal Development

Combined with an anti-spam service or CAPTCHA, it's much preferable to allow anonymous visitors to access registered users' personal contact forms than to have e-mail addresses posted publicly on the site.

This issue has patches for 4.7, 5.x, 6.x, and will hopefully get into 7.x core:

Allow anonymous users access to a members personal contact form
http://drupal.org/node/58224

Resolution

Eric:
all these people focusing on fixing a bug

this is my heretic speech.

Project module doesn't support threaded discussions.

Nat: Fairly common that issue trackers are flat.

What are people using?
Unfuddle.
Interpulse - time tracking, create issues and assign them.

Eric: I won't use something I don't control. Can't even put HIPAA stuff on a server, it has to be my own server.

Long-term dedication

Steven W. Merrill gave it and it was very good. That's all you need to know, plus this:

Notes and the module he developed in front of us, greatly extending the page_example module available from Drupal's API, are available here:

To everyone who visited the module building session, here are the the two files that we built:

Why click on forums every time?

Why create a user every time to make sure it isn't

Me: And I thought it was just so

• Functional tests - what users do
• Unit tests - (not doing so much)
• Security tests - insert javascript, cross-site scripting, SQL injection, penetration testing on every form field: if it sees the form it

Assertions are the base of any testing framework.

Views 2 Relationships: Let's you get information that's one step away.

For instance, you can get content based on when users joined or something.

Add a relationship for Queue.
Add the Questionable Content queue.

Now we can use the in-queue filter: it has to be in that queue to show up in the view.

pretty slick.

And then you can sort for nodequeue.

Generally if you're thinking of writing an SQL filter do do what a views does, you can figure it out yourself.

Presented by Nat

References

Notes for Intro to jQuery in Drupal session, NYC Drupal Camp 5
http://groups.drupal.org/node/14858

Notes

Javascript used to be adding elements to web pages that if the browser didn't have javascript, they just weren't there.

Graceful degredation now losing favor to Drupal enhancement.

HTML is semantic markup.

webchick talking to Michelle in IRC #drupal:

I name all my patches as {module_name}-{description-of-changes}-{issue_node_id}-{issue_comment_id}.patch

Personally, I think issue_comment_id might be hard to do (even interpreted as the big #5 etc project module places in the comment title, rather than the internal Drupal ID!) since people can add comments while you are making the patch, but I'm on board with the ideal.

Getting into that habit also really forces you to keep to a one-issue-one-change thing.

Note: This note is not to my usual audience (ok, well it's still to myself...). Usually notes on Agaric are about working with Drupal, extending it, making modules or themes. This note is about developing and improving Drupal core itself. Although if you happen to be building any module for Drupal 7 right now, say because for instance you are insane, you would run into this issue also.

To those in IRC last night, I really wasn't crazy.

Nothing I could do through the user interface would touch the menu_router table.

Testing a patch and adding a simpletest with Catch as my guide.

Steps taken, starting with checking out Drupal 7 dev (or head, until the code freeze).

(I got the link to the patch for the wget below from the issue, in this case http://drupal.org/node/305740 )

http://drupal.org/project/cmt

the better taxonomy is under the hood, the better it will be for crazy community-empowering stuff like that

Resolution