The site we are working with has several scenarios when we require someone to become a registered user on the site. The two main ones are during an Ubercart transaction or to register to volunteer at an event. Right now the registration form is too long so we want to have the questions asked be variable depending on what link you use to get to the form. Our thought is that the questions are all there we just either collapse or expand field groups so that if someone buying something wants to tell about their volunteer interests they can they just won't be required too or shown those fields by default. I hope this makes more sense.

Thanks,

Steve

Steve Kessler

Denver DataMan

303-587-4428

Sign up http://www.denverdataman.com/denver-dataman-e-newsletter-signup for the Denver DataMan Free eNewslettter

From: Metzler, David [mailto:metzlerd@evergreen.edu] Sent: Tuesday, February 23, 2010 9:19 AM To: support@drupal.org Subject: Re: [support] Collapsible Field Groups Based on Entry Point

Not quite sure I understand what you're use case is form this. Could you elaborate a little more?

Dave

_____

From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Steve Kessler Sent: Monday, February 22, 2010 6:33 PM To: support@drupal.org Cc: 'Andy Lubansky'; 'Terese Tarantino' Subject: [support] Collapsible Field Groups Based on Entry Point

Hey Drupal Community,

We are looking to create a module that will based on configurable entry points (e.g. node/20 or /node) than you get a form with different field groups collapsed or expanded. Our use case is for user creations coupled with node profile module and we are prepared to consider writing a custom module but we want to see if there is a module out there that we are missing as this is a relatively significant undertaking.

Thanks,

Steve

Steve Kessler

Denver DataMan

303-587-4428

Sign up http://www.denverdataman.com/denver-dataman-e-newsletter-signup for the Denver DataMan Free eNewslettter

http://clusty.com/search?input-form=clusty-advanced&query=permit&sit...

It shouldn't be hard to build a block to hold search terms, query clusty and returns the results in a separate page. Perhaps someone has already done that.

or get an army to tag all your contents and use taxonomy

Jim

On Tue, Feb 23, 2010 at 5:58 PM, LESLIE FRIESEN < FRIESEN.LESLIE@co.polk.or.us> wrote:

Hi, everyone,

In preparation of Phase II of our website redesign, I have a question regarding searching tools. Say a person wants to search for "permit" on the website, hoping to find information regarding a driveway access permit. Right now, the search results bring up not only that info, but every time the word "permit" has been mentioned in any way, shape or form for the last ten years - including an obscure reference found in the middle of .pdf minutes from old commission meetings, etc. The list results maybe ten pages long and only a few references are actually relevant. I have to find a way to limit the search results to only webpages that are truly about permits. Does that make sense? I often see "native language" search tools, but not "drill down" type of tools. Is there a way to control what types of information is included in the search results -- say, only actual nodes and not published documents or images?

Thanks very much in advance,

Leslie

Polk County, Oregon

BTW, we are using Drupal 6.15

Leslie Friesen Polk County Information Systems Friesen.Leslie@co.polk.or.us 503-623-0713

-- [ Drupal support list | http://lists.drupal.org/ ]