Ok,
I am not sure if this is a bug of views 2 or if this is simply my ignorance of the software. Here is how to replicate the error:
1) Create a view of type "node"
2) Click on "add display" button. Make sure the pulldown menu says "page"
3) Under "page settings", click on "Path: none" to create a new path for the view
4) under "Page: The menu path or URL of this view" put, say, "temp"
5) click update then save
6) Visit the URL you created and you should get the following error:
Page not found
The requested page could not be found.
Do other people have this problem? I can't seem to find it on any of the messageboards. I know some PHP and I may be able to help debug it, but I'm not sure if this issue has already been addressed.
Also, some other questions:
1) Are there any unit tests for views?
2) Do any of you guys use a step-through debugger for Eclipse on PHP? For the life of me, I can't find a way to integrate eclipse with a decent PHP debugger.
Comments
Comment #1
PhilippeB commentedHello Steveeq,
I had the same "problem" until I selected a Field. It seems it is now requiered, even for the Page display (which is different from the 5.x version).
Comment #2
merlinofchaos commentedI don't think you're getting a valid view with just that set of steps. If you scroll down and click the Live Preview button, it will tell you whether or not a query was even run; if it was not, the view did not validate. A view that does not validate will not be used.
Comment #3
merlinofchaos commentedComment #4
steveeq commentedActually, I found the source of the error. It occurs on the page where you edit the specification of the view. On this page, when you specify the path, if you specify the trailling slash in the URL, it won't register right. So "/testing/restaurants" will work while "/testing/restaurants/" will NOT work.
Comment #5
steveeq commentedComment #6
steveeq commentedChanging status
Comment #7
merlinofchaos commentedUpdating title
Comment #8
merlinofchaos commentedThis is now fixed in CVS.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.