By syawillim on

I have two sites that I have upgraded from 4.6.0 to 4.6.1 and am having the same problem on both. I have node_prvacy_byrole.module enabled on both sites and when anonymous users try to access private content they receive a “Page not found” message instead of “Access denied”.

To see this in action go to www.clubswa.com.au and select “member only” or www.avondescent.com.au and select “competitors”.

Any assistance with this would be greatly appreciated, thanks in advance.

Comments

mikegull’s picture

mikegull commented

Upgraded from 4.6.0 to 4.6.2, same issue. Have CVS version (downloaded July 6) of node_privacy_byrole installed, also newly upgraded due to non-admins not being able to set perms.

Opening bug report.

syawillim’s picture

syawillim commented

This problem has also been raised here http://drupal.org/node/26333, I tried reverting back to the old node.module as suggested but had no success.

Sam308’s picture

Sam308 commented

I was the one who made the following posting:
http://drupal.org/node/26333

I said that to fix the problem, I had to restore the node.module file from version 4.6.1.

Actually I think the node.module file was from version 4.6.0. The file ID is listed below and the file itself has the date stamp of 4/11/2005.

// $Id: node.module,v 1.485.2.1 2005/04/11 16:39:40 dries Exp $

By replacing the 4.6.2 file with this one, everything was back to normal.

Sam308
----------------------------------------------
Previous post http://drupal.org/node/26333

Problem in the 4.6.2 upgrade - node.module

I upgrade my site from 4.6.1 to 4.6.2 and notice that the Default 403 (access denied) page does not work anymore. My Default 403 (access denied) page is node/35.

The page setting for the Default 403 (access denied) page can be found on the administer >> settings page under “Error handling”.

To fix the problem, I had to restore the node.module file from version 4.6.1.

I also have the” node_privacy_byrole.module” installed to designate which user roles are denied access to certain pages within the web site.

I know that the node.module file was an important part of the 4.6.2 upgrade, so is this an issue that needs to be fixed and applied to the next 4.6.3 upgrade?

Does anybody else have this problem?

Sam308