By kitsunechan on
I've used Views before dozens of times, but I'm having an issue today and I can't figure out what's wrong. I'm assuming I'm overlooking something simple.
I have pages and blocks created with Views. I wish for all roles, including anonymous visitors, to see Views content. However, all users but anonymous users are able to see Views content.
I am using custom fields with CCK, so in permissions I have enabled 'view [the cck field]' across the board for all roles. I have also enabled 'access all views' for all roles. I have gone into the View to make sure 'Access: Unrestricted' is set.
Am I forgetting to check something?
Edited by WorldFallz - moved to appropriate forum.
Comments
_
Might seem obvious, but does the anonymous role have the generic 'access content' permission?
Good idea, but not the issue
Yes, that permission is enabled too. That's just the sort of easy thing I'm assuming I've overlooked.
maybe not so simple
Okay, now I'm starting to wonder if the issue isn't just some simple thing I overlooked. I'm stumped.
cleared cache, rebuilt access permissions
I cleared my cache and rebuilt my content access permissions. Neither did anything to help.
=-=
as a test remove the field level permissions being used.
as you sure there are no permissions set on the view itself in the view?
?
I'm sorry, I don't understand. Should I disable the permission for all roles to view the CCK fields for the content type the View is for?
I've gone into the View many times and 'Access: Unrestricted' is set for all items (default, pages, and blocks) in the View.
I found this post when I had the same problem.
See if your code validates first. Mine didn't.
I had put some "helpful" comments into each view, so I could easily scan the rendered code and know where each template was affecting the code. It turns out, the file name that I put in the comments had a "--" which the firefox thought was malformed comment code, so it was hiding all of my fields in the views.
I was using IE for admin & FF for anon users, so I thought it had to do with roles/permissions. It didn't. Just invalid code.
good idea, but not the problem
That was a good idea, but everything seems fine. I ran a validation test and the only things wrong had to do with Facebook Connect tags. I disabled Facebook Connect and it still wasn't working.