When I create a new view, the path listed in "Path" does not display the view.

For example, I can create a brand new view called "Test View", and click "Continue & edit.' Then, on the Displays page, do nothing but click "Save". The auto-preview at the bottom displays correctly (by default, a list of content teasers). But if I click the "View Page" button, it takes me to the correct path, but I get a "Page not found The requested page '/test-view' could not be found."
Even if I change the permission restrictions to none, the same thing happens.

I just noticed today that if I try to change the path of an existing and working View, the new path gives the same error, although I can revert it back to the old path without trouble.

I have tried re-installing Views, without success.

Any suggestions?

Comments

dawehner’s picture

dawehner
Primary language German
commented 
For example, I can create a brand new view called "Test View", and click "Continue & edit.' Then, on the Displays page, do nothing but click "Save". The auto-preview at the bottom displays correctly (by default, a list of content teasers). But if I click the "View Page" button, it takes me to the correct path, but I get a "Page not found The requested page '/test-view' could not be found."
Even if I change the permission restrictions to none, the same thing happens.

This seems to be some misunderstanding what views does if you use "continue & edit". Once you do this, the view is not stored in the database. So if you do a "view page" the view is not registered yet.

Once you click save it should work for you as expected.

Maybe someone could hide this link as long the view itself is not saved yet, this should be possible to do.

mysteryv’s picture

mysteryv commented

I guess I wasn't too clear. After "Continue & Edit", I DO click "Save". The auto preview appears correct, but when I navigate to the page (by either clicking "view page" or manually entering the url path) I get Page Not Found.

kars-t’s picture

kars-t commented
Assigned: mysteryv » Unassigned
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed".

If there is new information, please re-open the issue.

--
This issue was edited with the help of Issue Helper

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.