No content for guests displayed
ksc - June 15, 2009 - 12:44
| Project: | View own |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I installed view_own,
rebuilt permissions,
set view_own permissions for nodes (also for guests),
but guests can´t see any content (only drupal standard home page)
Created new content - same problem.
The I tried 6.x1x-dev version, rebuilt permissions again - no change.
For logged in users the module works fine.
I use drupal 6.12 + Protected Node (besides other modules).
#1
I tested again, disabled Content Permission, disabled protected node, enabled all view_own rights - no change. Guests (user not logged in) don´t see any content - they have all rights to see content.
It must be a bug.
#2
I too am having this very issue. Anonymous (guest) users can't see the content.
#3
I'm having the same issue. I have menu by role module installed. I think they are clashing. It also disables fivestar.
#4
I too have menu by role installed, however from what I understand that module only affects what menu options are displayed and doesn't do anything to control content.
#5
With 1.1 stable version is the same problem?
#6
I'm using 1.1 stable and am having this issue. I should have been more clean when I responded... I didn't look at the version #.
#7
Ok, because I did some changes to dev so I wanted to be sure that nothing was broken by those changes.
It's probably anonymous don't have any uid.
I'll try to reproduce it soon and check for solutions.
#8
tried both the stable and the dev versions and the guest cannot see the content.
Sorry to rush, would there be an update soon?
Really would like to use this module so that people who create events will only the event that they create.
P.V.Anthony
#9
I've tested it and I can't find any problem with that.
Step 1.
Set up proper permission on admin/user/permissions page (view any ... by anonymous)
Step 2.
Rebuild permissions on admin/content/node-settings page
Step 3.
Clear the cache on admin/settings/performance