Situation:

I set up a view with node->nid as an argument, allowing multiple terms per argument with +. I link to the view, for example, with compare/cms/1+2+3+4. This works fine. It shows a table of the nodes by argumented nids.

Problem:

I delete node #1. Now the argument invalidates and (standard) redirects to 404 page. I know I can set validation to "all values", preventing the 404. But here comes the feature request: why not drop the invalid single argument 11, and show the page as if with 2+3+4?

Currently it's "all or nothing" when validating an argument. My feature request is to have a validation option "ignore invalid {nid}", and show the table with nodes 2+3+4 anyway. Is this possible? Maybe not by design, right?

Reason why I need this:

Google direct my users to 1+2+3+4 pages. If 1 is deleted, they either get a 404 error or the wrong table. This is undesireable. They should find 2+3+4, what they were looking foor.

Comments

Anonymous’s picture

Alternatively, a 301 or 307 Redirect to the All Values page. To instruct search engines something moved. Anything between the "all or nothing" approach would be an improvement.

merlinofchaos’s picture

This is reasonable. Note that I don't have time in the near future to get to something like this, but would accept patches.

dawehner’s picture

I think there should be two options, or?

- Ignore invalid and show the rest.
- Don't ignore invalid and use "Action to take if argument does not validate".

dawehner’s picture

push :)

iamjon’s picture

Category: feature » task

I'm marking this as an unassigned task. If anyone would like to role up their sleeves and take it upon themselves to write a patch it would be awesome

andiart’s picture

Version: 6.x-2.x-dev » 6.x-2.16

This still is a problem in 6.x-2.16.
Is it still existant in newer versions?

mustanggb’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)