Hey all,
I'm not having any luck finding a solution to this so thought I'd post this here with the intention of having a comprehensive list of suggestions from the community in one place.
I'm replacing a rather complicated nodequeue based view with one that just uses taxonomy (at the clients request). I've found this very good screen cast from LevelTen shows exactly what I'm after. I was most of the way there myself but this, hopefully, has got me the rest of the way;
http://youtu.be/a_j3xUpdLEs
The problem I've got is that when I hit the URL set in the page I get a 404. Everything that needs to be enabled is enabled and watchdog supplies no hints and ,yes, the spelling of the URL is correct. :) Creating a barebones page that doesn't rely on arguments being passed through to views via panes or anything like that. This page has the same problem.
So, the purpose of this post;
If you've come across anything like this before could you post how you found the solution and what the solution was. Module clashes, menu router clashes, etc.
Cheers,
Gold.
| Attachment | Size |
|---|---|
| NodeQueue free Science Center | NIWA 2011-08-09 16-27-18.png | 49.84 KB |
Comments
Hi Gold, I'm not that
Hi Gold, I'm not that familiar with Panels, but since access is set to public the only thing that springs to mind is that you are testing it with no argument set for %term, and my guess is that the view is set to 404 when no %term argument is supplied.
Does the view have a page view that you can test in isolation from Panels?
Unfortunately not. %term is
Unfortunately not. %term is set and, for testing purposes, the panel is always displayed even in the absence of the term.
Testing a page on the view is showing up the same issue so it's looking like my initial thought that it's related to system pages was jumping the gun a little.
Will be throwing this out there to the rest of the local dev team to see if they know of any modules we have that may be interfering with paths. Entering panic mode now... ;)
Thanks for the pointer. I really should have tried that before putting the word out here.
A couple of thoughts; Have
A couple of thoughts;
Have you saved the view before testing it? Views 3 (and 2 I think) requires that you save changes to the view before they take effect anywhere outside of the view-edit UI. Though are probably already aware of this, it still catches me out sometimes.
Drop some
dpm()s intomenu_execute_active_handler()and see what function is or should be handling the request to the system path you are testing.You should also be able to check there that views has indeed exposed your view's path as a system path to the menu router system.
Finally; Views arguments (aka "contextual filters") have two different places where they can be configured to render a 404; One in the "When the filter value is NOT in the URL" settings, and one in the "Validation" settings. Either can be hide (aka render 404) the view if the argument is missing or does not validate, respectively.
Bevan/