Feed Items Inaccessible in Views

We tried rebuilding node access permissions, but this didn't seem to resolve the issue.

We are using a number of custom content types, and all the content published after enabling module would not display in views for anon users while module was enabled.

Anon users did have access to the full nodes.

Ah! If that's correct then the defaults of the Protected Node would protect the entire website.

I guess I could test that on my end, but I'm pretty sure I've done that and did not run in a similar problem.

Jerimee, was that only a problem with views, or was it with all nodes?

Rebuilding permissions would probably do the opposite which is protect nodes that weren't protected.

Thank you.
Alexis Wilke

@Alexis: I can confirm Jerimee's problem from #1.

The problem is only with Views module (current 6.x-3.x Views version in my case). The node by itself is accessible.
Rebuilding permissions didn't help.

To reproduce:
- create a content type with some CCK fields
- create some sample nodes with this content
- create a View over these nodes
- install protected_node module
---> anonymous user can see the Views output (block or page)

- let protected_node module enabled
- create another content type (or even add a new CCK field)
- ...
---> anonymous user can't see any Views output

Do you use any of the Protected Node Views extensions?

• Protected node list: Node is protected
  
  Whether the node is protected.
• Protected node list: Password last changed
  
  Date when the password for this node was last changed.
• Protected node list: Protected node, but show title
  
  Whether the node title is protected.

I'm also using Views 3.x and I cannot reproduce the problem. I can see the protected and unprotected nodes...

Just in case I added a CCK text field to the type of those pages and I still can see the nodes as expected.

Finally, I'm not too sure I understand the problem. Do you always see the view and some links are broken? Or does the view become empty? (you see nothing more on that page or in that block?)

One thing though... I'm using PostgreSQL and it could be that the generated code for your views breaks in MySQL.

So... anyway... I tried all sorts of cases following your steps and I still cannot reproduce the problem. There could be another problem or the Views your using may be bogus (since the default one is, if you did not fix it, it could be a problem with that, I tend to fix modules when they don't work right for me... If you're a programmer you may find value in this patch: http://drupal.org/node/1344392 since I have those fixes in my version of Views 3.x)

Ah! I have some good news this time!

zyxware noticed that the rewrite_sql() used by the protected_node module was actually wrong. The patch was applied and will appear in the next version of the protected node module (it should appear in the dev version within 24 hours.) See #1578566: Unable to access menu items that used to be protected but are no longer protected because of hook_db_rewrite_sql for details.

Let me know whether that works better for you.

Thank you.
Alexis

Hello,

I close this issue because Drupal 6 is no more supported. https://www.drupal.org/drupal-6-eol

If this issue is present in Drupal 7, feel free to re-open it.