I created my menu manually, because i couldnt get the one that is supplied using glossary style to work with multiple arguments and stay on the top no matter if the argument is met.

Anyway, i want to display all node which titles start with numbers be located under "#", or "0-9".

Is that possible?
I already looked at http://drupal.org/node/673100 but it seems that the code hanschri supplied does not work.

Comments

dawehner’s picture

dawehner
Primary language German
commented

You have to do additional custom work if you want to use @hanschri's code.

This issue is not easy to solve from my perspective.

Letharion’s picture

Letharion commented
Status: Active » Fixed

Answered by dereine months ago, no further questions.

Fidelix’s picture

Fidelix commented
Status: Fixed » Active

Answered, but not fixed.

He only said custom work would be needed.

This issue is not easy to solve from my perspective.

Letharion’s picture

Letharion commented
Status: Active » Postponed (maintainer needs more info)

Fidelix, what would you consider a fix?

merlinofchaos’s picture

merlinofchaos commented
Status: Postponed (maintainer needs more info) » Fixed

It may not be answered from your perspective, but from the ability of the folks maintaining Views', it has been.

I realize it is not the answer you wanted but that is the answer that is available.

Fidelix’s picture

Fidelix commented

It still does not mean the support request was fixed.
Saying "additional work is required" is an easy and lazy way to fix things, don't you agree with that?

Not every answer solves a problem.
This issue is a support request, not a bug report, therefore the "maintainer's" perspective matters little.

The proper way to close this issue is "Closed (Won't Fix)" since maintainers do not wish to apply effort in it.
But do what you will.

merlinofchaos’s picture

merlinofchaos commented
Status: Fixed » Closed (won't fix)

Not every answer solves a problem.
This issue is a support request, not a bug report, therefore the "maintainer's" perspective matters little.

Uh. This is the queue for Views, so the maintainer's perspective for this actually matters a great deal. We have specific processes for what this means. Your opinion may disagree with this process, but in the case of a disagreement, I think we get priority.

And I apologize, but we may not be able to completely answer every question to the asker's satisfaction. That said, we use this queue to do work on a daily basis. This is not stackoverflow.

We do not have the ability to walk you through writing custom code to utilize the Views' API. While you could probably get away with posting code you're trying to get working with Views, we simply cannot be expected to spend the hours it would require to show you what it is you need to do. In this case, the problem is quite complex. Unless you're already an expert with SQL, your chances of solving the problem are quite low, and the ultimate answer is that Views does not support a feature like this at this time. You are welcome to attempt to implement the feature and contribute it back.

If you prefer, though, I'll mark it closed (won't fix).

Fidelix’s picture

Fidelix commented

OK. Thank you for the attention.
Just one more observation:

fixed indicates that the issue has been addressed. In the case of a bug report, task or feature request, a commit has been made to the code or change to supporting documentation. In the case of a support request, the question has been answered as well as is possible. When a Bug Squad member has answered a question, even if the answer might be incomplete, fixed is the best status to use. It is unfortunately common for Views' maintainers to forget to use this status and leave answered support requests as active. These can simply be marked fixed. If the user finds that the answer is insufficient, they are free to mark the issue active again when they request further information.

But i agree with you that this issue should not be active. So i do believe Fixed (Won't Fix) is the best.
Thank you again.

aacraig’s picture

aacraig commented

It's actually quite an easy fix.

You can simply use the PHP validator and change the argument if the # symbol is passed.

Under "When the filter value IS in the URL or a default is provided" select the PHP validator, and paste the following in as the validator. This checks to make sure the argument is alphanumeric or the # symbol, and then expands the argument to any number if # is passed.

if (preg_match("/[^0-9a-z,\+#]/", $argument)) {
  return FALSE;
}

if ($argument == '#') {
  $handler->argument = '0,1,2,3,4,5,6,7,8,9,0';
}
return TRUE;