I get a page not found all the time after upgrading

Have you run update.php ?

How about uninstall and re-install ?

I got the same error with Global Filters. It always show "page not found" when VIEWS return no result.

Re-install doesn't solve the problem. Also, there is a bug on the latest module when install, a lot of people can't success install and have to manual remove some global filter's field.

@zeroxw:

Do you mean, people can't UNinstall? Please describe clearly the steps to reproduce your problem. Please also confirm this is version 7.x-1.11, not 7.x-1.x-dev?

And before you re-installed, did you uninstall first?
Rik

I've just spent quite a bit of time trying to reproduce this on 7.x-1.x-dev, but cannot.
vip_sa and zeroxw, you need to be clearer in specifying what kind of global filter you're using (driven by a View or a field and if driven by field, what kind of field... list, integer, taxonomy...). What kind of validation do you have on the contextual filter? Do you use "Allow multiple values" or not?

Do you get the same result, i.e. "page not found" when you append the (machine) value of the global filter to the URL, i.e. as a contextual filter? You should.

For instance, when on my system I have a global filter driven by a taxonomy term. When I select via the global filter a taxonomy term that has no content associated with it, I just get the page title followed by an empty page. I do not get "page not found", UNLESS I select multiple terms and I have a validation function set to accept numbers only (numeric validation won't accept the '+' signs to separate multiple values, so you need to set it to -Basic validation-).

As for showing a message... you specify that by adding a "Global: Text Area" under NO RESULTS BEHAVIOR, right hand side of the Views UI.

Hi Corne,

I cannot successfully import that View because I don't have the content and content types to match.
I can see you're using 5 Global Filters and that should be fine.
If you want me to investigate further I suggest you give me temporary access to your test system. Otherwise it's too hard.

I still believe that this is a Views configuration issue more than anything.
As I said, if you take the 5 global filter values from one of those "page not found" global filter combinations and you append them in the correct order to the URL, separated by slashes (i.e use them as contextual filter arguments, which is what global filters really are), then you should see the same behaviour. In that case, when the contextual filters are appended to the URL, global filter will do nothing and the behaviour you will see then is pure Views behaviour.

Rik

Thanks for your support Corne,
I and other Global Filter users would be most interested in learning how your developer got it to work.
Rik

Closing due to inactivity.