By cipster@blogger.com on
Hi there!
First of all thanks for the effort you put in Drupal. It really is a great tool.
I just installed 4.1.0 on Linux/Apache1.3 and I'm trying to build my website. I've created an admin user following the installation manual and posted a test story. The story is visible on the main page (http://localhost/) only if I'm still logged in as admin. If I click "logout" I get an empty page with the login box on the right and no content.
I've checked the status of the item and everything seems OK. Anyone can help?
Thanks in advance.
Comments
Grant permissions to anonymous user role
Admin -> User Management -> User Permissions and then check the "access content" and any other permissions for the 'anonymous users' column.
Acess Denied
I have enabled this setting, but still get access denied as the only story content for a non-logged-in user (even after server restart).
Fix.
Had to post a new story....
Path update
A minor clarification for the literal-minded (I'm running 4.3.0 so the terminology may have changed.)
Use Administer->Accounts->Permissions to set this.
Cannot access any pages when logged out - 4.5.2
4.5.2 doesn't have an "access page" permission - only "create" and "edit" page. How do I get pages to show up for anonymous users?
Anonymous access denied 4.5.2
I just installed 4.5.2 on Mac/Apache 1.3
Anonymous users get an "access denied" message.
I set permissions for anonymous to node module "access content" in Administer>users>configure>permissions.
For testing purpose I checked all boxes for anonymous users permissions. Same "access denied" message.
I made new posts, restart the server. Same problem.
What else can I try?
EDIT
I made an identical installation on an other virtual host (on the same server). Let's say the first host is named host_1, the second is host_2. No other differences. And it works ! ?
Anyone find any tricks to
Anyone find any tricks to fix this? Exact same problem here.
Same problem
I also configured my system by activating ...
> administer > configure > permissions > node module: access content [√]
... and still have no anonymous access to content.
Recent change: moved files to a new subdirectory (having edited the conf file and changed permissions).
All content is still visible to admin and authenticated users.
UPDATE: I went to the node_privacy_byrole module, clicked it on and clicked it off. Things are fine now.
same trouble ..
hello, good to read others have similar trouble - been trying to give anon. access to front page X-]
But it doesn't work .. i have gone
" administer > users > permissions "
anonymous users are allowed to access node module, vote on polls, access comments .. and search content, but still the front page is the original no-content default node (or blogs if i change that)
anything published or promoted to front page is still only available to the administratore.
(driving me mental :)
any more clues? where's this node_privacy thing? is that an extra plugin module?
thanks .. michael
Same were with 4.6.0
SQL commands from
http://drupal.org/node/12757
specificlally INSERT INTO users_roles (uid, rid) VALUES (0, 1);
did the trick for me! uid 0 was absent from users_roles after upgrade 4.5.2 -> 4.6.0
fixed this one, thanks
well i reinstalled everything, and upgraded to 4.6, where the access permissions work fine, (except the poll which closes after somebody votes :)
michael chalk, melbourne, oz
Argh!
I've tried all the SQL commands and every trick, but I'm still getting this error!
My install is a completely clean install (from scratch) from the latest release.
Is there ANY way around this?
Regards.
I had a similar problem
I had a similar problem today (no idea how it happened) and after some debugging and carefully comparing a good and a bad copy of the drupal database I fixed my problem with this:
UPDATE blocks set status=1 where module='user' and delta='0';
This is assuming the status was accidentally set to 0 like on my installation...
Judging by what delta means ("The largest in absolute value the weight can be..." as in common.inc) this makes no sense to me. Puzzled.
same problem
solved it by enabling nodes_privacy_byrole then going to
settings>nodes_privacy_byrole and toggling disable
don't understand it but it worked!