By Danio on
Okay... I dunno what I did. Everything's fine when I'm logged into my site. Once I log out, I get Drupal's welcome message. The one that you get right after installation:
Welcome to your new Drupal-powered website. This message will guide you through your first steps with Drupal, and will disappear once you have posted your first piece of content.
The first thing you will need to do is create the first account. This account will have full administration rights and will allow you to configure your website. Once logged in, you can visit the administration section and set up your site's configuration.
Etc. etc. etc.
All I get from the main page is that above message when I'm not logged in. The sticky post and all the other posts aren't there, but everything else is the same. When logged in, everything is normal. Anyone know what's wrong?
Comments
Forgot to mention... I'm usin
Forgot to mention... I'm using 4.5-rc, and I didn't just install it. I had it up and running since it was available, and already posted my "first piece of content" a long time ago. :)
And actually it seems that all content is missing when I'm logged out, as if I just installed Drupal (but with the theme in place). But when I'm logged in, everything's there again.
It seems that I need to have
It seems that I need to have 'administer nodes' permission enabled for the nodes to appear. Only roles with that enabled can see the nodes. Anyone know how I got things to become that way?
Permissions
No, you need the 'access nodes' permission for the nodes to appear.
Yyou're not using any of the node-level permission modules, are you?
I had nodeperm_taxonomy insta
I had nodeperm_taxonomy installed but not enabled.
Using 4.6
Been using 4.6 final on a test site for the last two days and am a little baffled why the "Welcome to your..." message from the node.module is now showing up.
I created several messages while testing the image module, the image assist module and various other posting modules which were visible when I logged out earlier today.
I went to dinner and when I came back to the site, the "Welcome to your...." message was there until I logged in.
The node access is set to access node for all roles.
The site was not access by anyone, I have only admin can create accounts set, the database is intact, etc...
Anyone have any idea what would cause this without having made no changes to the setup of the site?
Same problem
I've got the same problem here. My site was live two days ago but, yesterday, no anonymous access to items on the front page. I've checked the access permissions dozens of times and can't find anything wrong. The site is not available at present--except for logged-in users; I want to allow access for anonymous users, too.
Not sure what caused this or how to fix it. Pulling my hair out hasn't helped so far...
NPBR - permissions for permissions?
This is a longshot, but... I had a similar problem and it was caused by a user who doesn't have the (node_privacy_byrole) 'permissions for permissions' permission, who edited a node created by another user and was on the front page.
It seems that doing that 'resets' the permissions of that node (unless the editor has 'permissions for permissions'), which is probably a bug I should file. So I ended up restricting the permissions on front page nodes to only those people who have permissions for permissions...
That's configured in http://{site}/admin/node/configure/types/page and similar urls for all other node types.
Administer Nodes Permission Restricted
I know how to configure content types but I'm not sure how this applies to the issue I'm dealing with--not completely sure I understand what you're saying.
The content on my front page wasn't edited by a different user than the original author. I'm don't know how a user who doesn't have administrative access could change the content type configurations unless there is a major bug in the system (I assume there's not such a bug since I can't do that with a non-admin user). Theoretically, only "users with the administer nodes permission will be able to override these options", according to the content type configuration instructions.
check your tables.
When I recently helped someone with a similar issue, we were able to trace the problem to an incomplete database setup. The db schema was incorrectly loaded and the node_access table was empty.
Please check your db and report if you see anything suspicious.
---
Code0range: Drink Your Juice
No suspicious tables
The node_access table isn't empty. However, I'm sorry to say that I don't know much more than that since I'm not well-versed on SQL. I did the Fantastico install of 4.6. All I've done with the SQL since then is load themes and modules. So, no, I don't see anything suspicious but I'm not exactly sure what would be suspicious.
In case it's useful, here's a screenshot of the table info from myPHP.
Never mind...
Sorry, my post was not written very clearly (even for me now) :-(.
I was referring to node_privacy_byrole as other users have also mentioned. There is a bug there (I tested again and filed a report), but I guess that's not your problem.
I love Drupal but this is is
I love Drupal but this is is the kind of stuff that makes one go crazy :-(
Your screenshot shows the table structure (which looks OK to me), but if you click on "browse" how many rows do you see? Since you never enabled NPBR there should probably be exactly one row : 0, 0, 'all', 1, 0, 0 (according to database.mysql).
Do your Drupal logs state any errors (access denied springs to mind)? I also once had a problem where I accidentally disabled the "log in" block which disabled the log in but ALSO created access denied on the front page, which didn't make sense. Maybe the same effect can occur with other blocks being disabled too; I'm not sure about that.
Other ideas: have you ever had it working? Are the posts actually published? Which modules/blocks have you recently enabled?
Well, now that I've pulled
Well, now that I've pulled all my hair out, I finally just deleted the site and started clean. Everything seems to be working fine now. I haven't a clue what made my site suddenly go from accessible to nonaccessible. I certainly hope it doesn't happen again!
Thanks for all the help. At least I know some things that weren't causing the problem. :D
Sad that you had to pull the
Sad that you had to pull the plug on your site. I have another strange one and, unfortunately, this is on my live site: http://drupal.org/node/23438
It seems that the best way to avoid such problems is to have one or two test sites and try every new module there before using it on a production site.
Probably node_access table corrupted
Hi
same problem some time back, probable reason was the node-access table corrupted in database. when i update the database with backup, the problem has been nomore. hope this info helps.
Cheers,
Sunny
Node permissions by role?
Are you using, or have you used the Node Permissions By Role module?
It sounds like a problem I saw when it was improperly disabled. When I was logged in as the admin user things were fine, but users who weren't logged in didn't see any nodes they had "permission" to view.
http://www.addingunderstanding.com/node/771
--
Not using that module
As for my problem, I'm not using the node permissions by role module; nor have I used it. However, you've described the symptoms exactly: logged in users can see what they're supposed to see but anonymous users can't see what they're supposed to see.
This is exactly the kind of
This is exactly the kind of problem that is created by node_privacy_by_role module. I once spent three days grappling with your exact problem before deleting the site and doing a new install of drupal. Fortunately, it was a test site.
Even though you are not using it, I suggest you read the following thread for possible hints about how you could set this right:
http://drupal.org/node/22406
If you are using phpmyadmin, try optimising or repairing the node_access and cache tables for what it is worth.
Not sure how it applies
Thanks for your help. I read over that thread and looked at my tables but I don't see anything that applies. Since I've never had the node privacy by role module, theoretically, the issues caused by that module shouldn't be occurring on my site. For what it's worth, I ran a check and repair on all my tables from mySQL. Everything came up OK.
Does the screenshot of the node_access table show any signs of incorrect settings?
Thanks for all the kind help everyone's offering!
If you have installed Organic Groups
Then that module could be the problem. I installed it, fiddled with it, and then decided I didn't need it for the moment and disabled it. This was on a dev site - thank god.
Anyway, I ended up having the same problem described in this thread after having disabled OG - or something similar: no content unless logged in as an admin. After looking in the node_access table I noticed that the realm for EVERY node was set to og_group. I went and enabled the OG module again and finally noticed the following on the og settings page:
"After enabling this module via the module settings page or before disabling this module, use the above button to restore default permissions."
It's referring to a disable/enable toggle button on the og settings page. If you disable the module and do not press that button beforehand it will cause this problem, because effectively no one else but the group creator has grant_view for nodes (I think). As a result, the "welcome to your new drupal-powered website" stuff shows up.
If you haven't installed OG at some point then obviously this is not your problem, but perhaps another module was installed that changes perms in node_access. Anyway, re-enabling OG, clicking that button and then disabling it again solved the problem for me. And may I be the first to request that this button in OG be enlarged to 400x400 pixels and that the text referenced above be changed to red 100 point text. Ugly yes. Ahh, but effective.
-- aym
http://www.skatemental.com/blogmental
http://www.skatemental.com
100% Dead On.
Thank you for ending my head ache.. I am attempting to deploy a small college based social site locally and so of course was trying different mods for usability. Of course OG seemed worth a shot, well when I decided that it didn't pan out she didn't want to let go of my board so easy :)
I did as you said and everything is all good. I was not wanting to edit the users in the SQL DB.... Again, THANKS!
EzNet -
http://blog.eznet.frih.net
.
.
Same problem
The same problem is also discussed at http://drupal.org/node/45782