Drupal

http://drupal.org/project/persistent_login

4.7 era answer:

Increase cookie lifetime in settings.php with an ini_set command or, recommended, use the persistent login module:

http://jaspan.com/persistent_login_module_1_1#comment-1348

Resolution

Agaric wanted and now has happily found a way to submit a node and get the create new content form immediately.

And there is a module to do that:
http://drupal.org/project/submit_more

(I recall I wanted it as a button to "save and add new" – I still think that would be a superior user interface.)

See also this more recent article: http://tiger-fish.com/blog/debugging-drupal-6-xdebug-ubuntu-104-and-eclipse-pdt-step-step

Drupal Eclipse
http://groups.drupal.org/node/8116

See in particular sdboyer's comments on that thread.

In response to (and crossposted from my comment on) Drupal Community Philosophies by Angie Byron:

One matter of terminology:

Kara:
this is what i'm workign on

http://simile.mit.edu/timeline/docs/create-timelines.html

benjamin melançon
There's a Drupal module for that (and it's sure to be better than poll module, which is getting voted out of core), but it's not up to date: http://drupal.org/project/timeline

location (API, module)
http://drupal.org/project/location

location.module supports proximity searches for content. Content (i.e., 'nodes') can be tagged with a physical snail mail location (whether full or partial). What number of location fields (e.g., 'street', 'city', 'postal code', 'country', 'province') are collected for each node type (and whether they are required or optional) is configurable in the default workflow for each node type.

Solution

(From rnreekez in the comments, syntax modified to conform to Drupal's more verbose coding standards.)

Technically you want your switch statement to process for all things TRUE.

I want to be able to have a link to http://example.com/big-ol-teaser-list-of-drupal-nodes#node-123 so I go to the right space on the page.

I would say what Drupal version I'm using, but I'm ashamed to say it's 4.7.

Wherein Ben discovers he doesn't know computer programming at all.

The community-managed taxonomy module needs to know all possible parent paths for an arbitrary-depth categorization structure. Even though taxonomy terms have a many-to-many relationship, when tracing back from one term to its parent(s), and that parent's parent(s), and so on to root level, it's one-to-many from that perspective. Barring illegal loops, there must be a finite number of possible ancestor paths, but all my attempts to walk through them have not quite resulted in predictable, correct results

Basically I want to display every possible one-to-one lineage for an item with ancestors.

CMT will not use relative thresholds, as I considered as an option at one point.

The idea of relative thresholds was that if ten percent of the actively involved community wanted something, that's when it could happen. OR 50% of users who have tagged or voted on a term's name, position, etc.

Instead, CMT will use just straight numerical thresholds (1, 4, X users voted for this change).

Reason? To avoid weird stuff that would happen unexpectedly with a dynamic threshold.