Posted by DarrinRich on July 9, 2007 at 12:34am
Over at our church site we have a list of Bible QAs which was created using views. We want everyone to access to it. For some reason only admins do. But the content in the views can be access by anyone just not the actual page created with views. Looking at the access control I cant see any reason why everyone shouldnt be able to access it.
Any ideas here on what I could be missing?

Comments
I played around with it and
I played around with it and couldnt figure it out. So I cloned the view and got the same results. I then just manually re-created the view. Even though it was identical to the original view, this time it fixed it. Go figure huh. Oh well, at least its fixed.
each view supports it's own access permissions
If you click edit on a view from admin/build/views, you will see the edit form for that view, if you click to make sure that the Basic Information section at the top is expanded, you will see a group of settings labeled 'Access:' under the 'Name:' field. From here you can define which users can actually 'view' the view that you have built. It sounds like you had an administrative role checked here.
Note that this does not show up at the normal access control settings at admin/user/access, only on the edit page for that particular view.
-Mike
Thats actually what I
Thats actually what I assumed the problem was and is what I did first. When I went to edit for that particular view I had nothing checked. It was really strange. I ended up just manually re-creating the exact same view with all the same settings and it worked.
Thanks though Mike for jumping in here. I appreciate it.
Here's what might have
Here's what might have happened, FWIW.
I went through this.
There are two places to enter a title:
-- "URL:" under "provide page view"
-- "Title:" under "View Type:"
The first time around I missed the first place to enter the title, let's call it "mynewview".
So the request for mysite.com/mynewview was asking for, as far as the web server was concerned, a non-existent page, hence the access denied error.
HTH