I've got an intranet site up and running that was started w/Drupal 4.7.something. I installed, at that time, the node privacy byrole module [1] to control who can access what. Eventually, I got around to updating the site to Drupal 5. Before I started that process, I disabled all contributed modules, including node privacy byrole. I was pretty sure I followed all the steps necessary to disable that module, but I must have missed something, because now no access control module I've tried will work.
What I've done so far is to install and uninstall Taxonomy Access Control Lite [2] (several times), Taxonomy Access Control [3] (a few times), Path Access [4] and one or two others to no avail. I've followed the advice of the Persistent 'Welcome to Drupal' for anonymous users [5] Troubleshooting FAQ node, and I've clicked the Rebuild permissions button (more than once) on admin/content/node-settings. I'm assuming something's not right with my installation, but nothing I've found so far has provided a solution.
I'd really like to install and use the tac_lite module, because I think it suites my needs just fine, and it's not nearly as complicated or difficult to use as some of the others. At this point, however, the priority is to be able to control who can access what.
Does anyone have any suggestions as to what I can try to fix this problem?
[1] http://drupal.org/project/node_privacy_byrole [2] http://drupal.org/project/tac_lite [3] http://drupal.org/project/taxonomy_access [4] http://drupal.org/project/path_access [5] http://drupal.org/node/64114
I forgot to list all the contrib modules that are in use on the site.
front_page
content date fieldgroup nodereference number optionwidgets text userreference
casetracker casetracker_mail
coder
basicevent event event_views eventrepeat
gmap gmap_location gmap_views location location_views
mass_contact mimemail send subscriptions
date_api diff pathauto quote releasemonitor sql_auth tablemanager update_status zzz_mods // Custom add-on code
views views_ui
I had trouble with access with the Account Types module in Drupal 5. We uninstalled it since it wasn't crucial.
On 5/15/07, Jason Flatt drupal@oadaeh.net wrote:
I've got an intranet site up and running that was started w/Drupal 4.7.something. I installed, at that time, the node privacy byrole module [1] to control who can access what. Eventually, I got around to updating the site to Drupal 5. Before I started that process, I disabled all contributed modules, including node privacy byrole. I was pretty sure I followed all the steps necessary to disable that module, but I must have missed something, because now no access control module I've tried will work.
What I've done so far is to install and uninstall Taxonomy Access Control Lite [2] (several times), Taxonomy Access Control [3] (a few times), Path Access [4] and one or two others to no avail. I've followed the advice of the Persistent 'Welcome to Drupal' for anonymous users [5] Troubleshooting FAQ node, and I've clicked the Rebuild permissions button (more than once) on admin/content/node-settings. I'm assuming something's not right with my installation, but nothing I've found so far has provided a solution.
I'd really like to install and use the tac_lite module, because I think it suites my needs just fine, and it's not nearly as complicated or difficult to use as some of the others. At this point, however, the priority is to be able to control who can access what.
Does anyone have any suggestions as to what I can try to fix this problem?
[1] http://drupal.org/project/node_privacy_byrole [2] http://drupal.org/project/tac_lite [3] http://drupal.org/project/taxonomy_access [4] http://drupal.org/project/path_access [5] http://drupal.org/node/64114
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.kubuntu.org/ Drupal Fanatic: http://drupal.org/ -- [ Drupal support list | http://lists.drupal.org/ ]
Quoting Jason Flatt drupal@oadaeh.net:
I've got an intranet site up and running that was started w/Drupal 4.7.something. I installed, at that time, the node privacy byrole module [1] to control who can access what. Eventually, I got around to updating the site to Drupal 5. Before I started that process, I disabled all contributed modules, including node privacy byrole. I was pretty sure I followed all the steps necessary to disable that module, but I must have missed something, because now no access control module I've tried will work.
Make sure that the system table, the cache tables and the variables table is cleaned for the modules you've removed. Although present with at least 5.0 not all modules make use of the hook module to delete itself fully when deactivated. From that point, if you have deactivated contributed modules but still maintain the module source in the modules path it may cause undesired effects because the module file is loaded just because it exists. You should remove these unwanted modules before cleaning the DB tables because they may populate on loading depending on how good the module design is.
Earnie
On 5/15/07, Earnie Boyd earnie@users.sourceforge.net wrote:
Quoting Jason Flatt drupal@oadaeh.net:
I've got an intranet site up and running that was started w/Drupal 4.7.something. I installed, at that time, the node privacy byrole module [1] to control who can access what. Eventually, I got around to updating the site to Drupal 5. Before I started that process, I disabled all contributed modules, including node privacy byrole. I was pretty sure I followed all the steps necessary to disable that module, but I must have missed something, because now no access control module I've tried will work.
What does that mean, exactly? You can't access the nodes? Anyone can access the nodes?
On Wednesday May 16 2007 3:30 am, Victor Kane wrote:
Quoting Jason Flatt drupal@oadaeh.net:
I've got an intranet site up and running that was started w/Drupal 4.7.something. I installed, at that time, the node privacy byrole module [1] to control who can access what. Eventually, I got around to updating the site to Drupal 5. Before I started that process, I disabled all contributed modules, including node privacy byrole. I was pretty sure I followed all the steps necessary to disable that module, but I must have missed something, because now no access control module I've tried will work.
What does that mean, exactly? You can't access the nodes? Anyone can access the nodes?
Everyone can access all nodes regardless of the access control scheme I have in place. I'm trying to limit who can access what, and it's not working. I have another site in place where I'm using tac_lite quite successfully, so I'm sure it's not the module or my use of it, but something in the site's configuration, database, or something else that I have not been able to find yet.
I am no expert, but there was a wonderful drupal dojo lesson on ACL and other niceties of the Drupal node access system, given by Andy Kirkham (ajk^) himself, and I wrote up the class notes, perhaps they might be of help:
btw, make sure you backup your database before zapping your node access table :)
saludos,
Victor Kane http://awebfactory.com.ar
On 5/16/07, Jason Flatt drupal@oadaeh.net wrote:
On Wednesday May 16 2007 3:30 am, Victor Kane wrote:
Quoting Jason Flatt drupal@oadaeh.net:
I've got an intranet site up and running that was started w/Drupal 4.7.something. I installed, at that time, the node privacy byrole module [1] to control who can access what. Eventually, I got around to updating the site to Drupal 5. Before I started that process, I disabled all contributed modules, including node privacy byrole. I was pretty sure I followed all the steps necessary to disable that module, but I must have missed something, because now no access control module I've tried will work.
What does that mean, exactly? You can't access the nodes? Anyone can access the nodes?
Everyone can access all nodes regardless of the access control scheme I have in place. I'm trying to limit who can access what, and it's not working. I have another site in place where I'm using tac_lite quite successfully, so I'm sure it's not the module or my use of it, but something in the site's configuration, database, or something else that I have not been able to find yet.
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.kubuntu.org/ Drupal Fanatic: http://drupal.org/ -- [ Drupal support list | http://lists.drupal.org/ ]
the link to the class notes, sorry: http://groups.drupal.org/node/3307
On 5/16/07, Victor Kane victorkane@gmail.com wrote:
I am no expert, but there was a wonderful drupal dojo lesson on ACL and other niceties of the Drupal node access system, given by Andy Kirkham (ajk^) himself, and I wrote up the class notes, perhaps they might be of help:
btw, make sure you backup your database before zapping your node access table :)
saludos,
Victor Kane http://awebfactory.com.ar
On 5/16/07, Jason Flatt drupal@oadaeh.net wrote:
On Wednesday May 16 2007 3:30 am, Victor Kane wrote:
Quoting Jason Flatt drupal@oadaeh.net:
I've got an intranet site up and running that was started w/Drupal 4.7.something. I installed, at that time, the node privacy byrole module [1] to control who can access what. Eventually, I got around to updating the site to Drupal 5. Before I started that process, I disabled all contributed modules, including node privacy byrole. I was pretty sure I followed all the steps necessary to disable that module, but I must have missed something, because now no access control module I've tried will work.
What does that mean, exactly? You can't access the nodes? Anyone can access the nodes?
Everyone can access all nodes regardless of the access control scheme I have in place. I'm trying to limit who can access what, and it's not working. I have another site in place where I'm using tac_lite quite successfully, so I'm sure it's not the module or my use of it, but something in the site's configuration, database, or something else that I have not been able to find yet.
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.kubuntu.org/ Drupal Fanatic: http://drupal.org/ -- [ Drupal support list | http://lists.drupal.org/ ]
On Wednesday May 16 2007 7:01 am, Victor Kane wrote:
the link to the class notes, sorry: http://groups.drupal.org/node/3307
On 5/16/07, Victor Kane victorkane@gmail.com wrote:
I am no expert, but there was a wonderful drupal dojo lesson on ACL and other niceties of the Drupal node access system, given by Andy Kirkham (ajk^) himself, and I wrote up the class notes, perhaps they might be of help:
btw, make sure you backup your database before zapping your node access table :)
saludos,
Victor Kane http://awebfactory.com.ar
Thank you for the information, Victor. However, while I could certainly follow the lesson and create something that would do what I wanted, I don't think it's necessary if an existing module will work, and I don't think it will work with the existing system until I fix the problem.
Jason,
The best way I've found on getting a handle on what's wrong with node access is to inspect the node_access table directly.
In some cases (like simple_access) the module's don't keep a separate store where they keep track of a permission to a node, and if that's the case, executing the reubuild node permissions will actually remove all access restrictions from all nodes. I'm not familiar with the access module that you're interested in, so I don't know if this is the case there.
So the best advice I can give is to rebuild permissions on a test site (not upgraded), and try setting up node_access from scratch. If it works, try inspecting the contents of the node access table on your upgraded site with what you've got on your functional test site.
Does that seem like a plan?
Alternatively, maybe someone out there who's using the module (or the maintainer) might be able to look at the data from your node_access table.
If you don't get help, let me know and I'll give a shot to reading the module code and seeing if I can let you know what the node access table should look like. Have you logged an issue on the project site?
Dave
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jason Flatt Sent: Wednesday, May 16, 2007 8:06 AM To: support@drupal.org Subject: Re: [support] Access control modules do not work . . .
On Wednesday May 16 2007 7:01 am, Victor Kane wrote:
the link to the class notes, sorry: http://groups.drupal.org/node/3307
On 5/16/07, Victor Kane victorkane@gmail.com wrote:
I am no expert, but there was a wonderful drupal dojo lesson on ACL and other niceties of the Drupal node access system, given by Andy Kirkham (ajk^) himself, and I wrote up the class notes, perhaps they
might be of help:
btw, make sure you backup your database before zapping your node access table :)
saludos,
Victor Kane http://awebfactory.com.ar
Thank you for the information, Victor. However, while I could certainly follow the lesson and create something that would do what I wanted, I don't think it's necessary if an existing module will work, and I don't think it will work with the existing system until I fix the problem.
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.kubuntu.org/ Drupal Fanatic: http://drupal.org/ -- [ Drupal support list | http://lists.drupal.org/ ]
On Wednesday May 16 2007 8:41 am, Metzler, David wrote:
Jason,
The best way I've found on getting a handle on what's wrong with node access is to inspect the node_access table directly.
In some cases (like simple_access) the module's don't keep a separate store where they keep track of a permission to a node, and if that's the case, executing the reubuild node permissions will actually remove all access restrictions from all nodes.
I'm actually okay with that, and I've done it several times in an attempt to figure out and fix what's going wrong.
I'm not familiar with the access module that you're interested in, so I don't know if this is the case there.
So the best advice I can give is to rebuild permissions on a test site (not upgraded), and try setting up node_access from scratch.
I'm already using tac_lite successfully on another site, so I know it's not the module.
If it works, try inspecting the contents of the node access table on your upgraded site with what you've got on your functional test site.
I did that, and as near as I could tell, everything was okay, but I wiped it anyway to make sure I wasn't overlooking anything.
Does that seem like a plan?
Alternatively, maybe someone out there who's using the module (or the maintainer) might be able to look at the data from your node_access table.
If you don't get help, let me know and I'll give a shot to reading the module code and seeing if I can let you know what the node access table should look like. Have you logged an issue on the project site?
No, because I'm fairly positive it's not the module's fault, though I'm sure I could file a support request. I just think it's something to do with the site and was hopping for some places to look, which I have received and followed through with.
Do the site where tac lite is working and the site where it is not working have all the same other modules installed, etc? Maybe it is a conflict between modules or something.
On 5/16/07, Jason Flatt drupal@oadaeh.net wrote:
On Wednesday May 16 2007 8:41 am, Metzler, David wrote:
Jason,
The best way I've found on getting a handle on what's wrong with node access is to inspect the node_access table directly.
In some cases (like simple_access) the module's don't keep a separate store where they keep track of a permission to a node, and if that's the case, executing the reubuild node permissions will actually remove all access restrictions from all nodes.
I'm actually okay with that, and I've done it several times in an attempt to figure out and fix what's going wrong.
I'm not familiar with the access module that you're interested in, so I don't know if this is the case there.
So the best advice I can give is to rebuild permissions on a test site (not upgraded), and try setting up node_access from scratch.
I'm already using tac_lite successfully on another site, so I know it's not the module.
If it works, try inspecting the contents of the node access table on your upgraded site with what you've got on your functional test site.
I did that, and as near as I could tell, everything was okay, but I wiped it anyway to make sure I wasn't overlooking anything.
Does that seem like a plan?
Alternatively, maybe someone out there who's using the module (or the maintainer) might be able to look at the data from your node_access table.
If you don't get help, let me know and I'll give a shot to reading the module code and seeing if I can let you know what the node access table should look like. Have you logged an issue on the project site?
No, because I'm fairly positive it's not the module's fault, though I'm sure I could file a support request. I just think it's something to do with the site and was hopping for some places to look, which I have received and followed through with.
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.kubuntu.org/ Drupal Fanatic: http://drupal.org/ -- [ Drupal support list | http://lists.drupal.org/ ]
-
Earnie Boyd -
Jason Flatt -
Jean Gazis -
Metzler, David -
Victor Kane