April 18th, 2002

Support patch v3

This patch contains all of the previous support area changes, plus it modifies the behavior of touching requests. With this patch, whenever the owner of a support request "touches" (requests to keep it open longer) the request they've filed, it'll prompt them for a comment as to why they've touched it. Also, this patch adds a checkbox on see_request.bml that allows volunteers with supporthelp to touch the request as well (provided they've left an internal comment as to why).

My MySQLd daemon on goathack is being flaky, so its hard to link to an example that stays up for more than 5 minutes.
  • mart

PATCH: Make random.bml completely different

I only have one user in my randomuserset, so you'll never get anything other than 'mart'. I know it works properly because I had another account in there for a while before I actually generated my randomuserset properly.

Also, the link to view the journal associated with an account won't work on my goathack site because I don't have the users process running. That's quite deliberate, and it will work on LiveJournal.com.

The text at the top is included from an include file, which someone will need to be given privs to edit in order to set a decent message for LiveJournal.com. When doing this, make sure to include a question mark at the end of the URL to random.bml since this seems to get around browsers caching the old output and not loading a new user.

I didn't do community-only random because I'm not sure that the journaltype field is indexed and thus it would probably be a shitty query. In fact, it's probably already a shitty query, and may need to be broken down into two queries so that it doesn't have to go through thousands of user records. Someone who knows about this stuff should tell me if it sucks, or something.

  • miruku

(no subject)

what about a patch that gives info on a communities info page about who owns the community..? or is there a reason there isint..?sorry if this is the wrong place to be asking this ;)