By OneTwoTait on

Whenever an anonymou user submits a node it leads to a "Page Not Found" page. It seems these nodes bare saved in the datbase but only appear as "n/a" on the site. They cannot be edited or deleted from the site but can be deleted directly using phpmyadmin.

I've setup test content-types with CCK and the result is the same. Even if a content-type only has a title field, the result is the same.

If Anonymous users are given "administer nodes" permission, it works. However, I don't want them to be able to choose whether the node is published, the authord on date, etc.

⋅ Categories: Drupal 6.x

Comments

chrisopeterson’s picture

chrisopeterson commented

Sound like these nodes have to be accepted for publication by an administrator before they are published. If only administrators can see them then this is the most likely issue.

http://inletmedia.com

OneTwoTait’s picture

OneTwoTait commented

The nodes display only as "n/a" for all users, including the administrator on a View. Going to the node page shows a "Page not found" for all users including the administrator.

tewson’s picture

tewson commented

I'm experiencing the same problem. It's so nonsense. My Drupal 5 site works properly for the anonymously-created contents. I thought that it's a permission issue but it's not since I've revised my permission table for tens of times.

I think that looking at the mechanism of displaying a node will help, but I have no idea where to get that.

Any idea, anybody?

netrom’s picture

netrom commented

I also had the issue with the error message "page not found" on all pages. The error occured only when I logged in as an ordinary user/member and NOT when I logged in as administrator.

This led to my first conclusion: It has to be about permissions! So, I went through all permission settings and checked every field that was necessary. That solved part of the problem. Now I could acces all pages as an ordinary member EXCEPT all the edit related tabs in the profile acount. These still gave me the error message.

After comprehensive investigation I found out that the problem was the userfriendly urls. So I disabled the path-module and related modules. And then all pages worked as intended.

Now I just have to work out a solution to get my userfriendly urls back without bugs. But the site is running as it should.

As described, in my case it had nothing to do with code, scripts, core-bugs or anything like that. But simply settings.

Maybe this is not the case for you but I just wanted to share this perspective too.

regards, Morten