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.<br><br><div><span class="gmail_quote">On 5/16/07,
<b class="gmail_sendername">Jason Flatt</b> <<a href="mailto:drupal@oadaeh.net">drupal@oadaeh.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday May 16 2007 8:41 am, Metzler, David wrote:<br>> Jason,<br>><br>> The best way I've found on getting a handle on what's wrong with node<br>> access is to inspect the node_access table directly.
<br>><br>> In some cases (like simple_access) the module's don't keep a separate<br>> store where they keep track of a permission to a node, and if that's the<br>> case, executing the reubuild node permissions will actually remove all
<br>> access restrictions from all nodes.<br><br>I'm actually okay with that, and I've done it several times in an attempt to<br>figure out and fix what's going wrong.<br><br><br>> I'm not familiar with the access
<br>> module that you're interested in, so I don't know if this is the case<br>> there.<br>><br>> So the best advice I can give is to rebuild permissions on a test site<br>> (not upgraded), and try setting up node_access from scratch.
<br><br>I'm already using tac_lite successfully on another site, so I know it's not<br>the module.<br><br><br>> If it<br>> works, try inspecting the contents of the node access table on your<br>> upgraded site with what you've got on your functional test site.
<br><br>I did that, and as near as I could tell, everything was okay, but I wiped it<br>anyway to make sure I wasn't overlooking anything.<br><br><br>> Does that seem like a plan?<br>><br>> Alternatively, maybe someone out there who's using the module (or the
<br>> maintainer) might be able to look at the data from your node_access<br>> table.<br>><br>> If you don't get help, let me know and I'll give a shot to reading the<br>> module code and seeing if I can let you know what the node access table
<br>> should look like. Have you logged an issue on the project site?<br><br>No, because I'm fairly positive it's not the module's fault, though I'm sure I<br>could file a support request. I just think it's something to do with the
<br>site and was hopping for some places to look, which I have received and<br>followed through with.<br><br><br>--<br>Jason Flatt<br><a href="http://www.oadaeh.net/">http://www.oadaeh.net/</a><br>Father of Six: <a href="http://www.flattfamily.com/">
http://www.flattfamily.com/</a> (Joseph, 13; Cramer, 11; Travis,<br>9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005)<br>Linux User: <a href="http://www.kubuntu.org/">http://www.kubuntu.org/</a><br>Drupal Fanatic:
<a href="http://drupal.org/">http://drupal.org/</a><br>--<br>[ Drupal support list | <a href="http://lists.drupal.org/">http://lists.drupal.org/</a> ]<br></blockquote></div><br><br clear="all"><br>-- <br>Jean Gazis<br><a href="http://www.jeangazis.com">
www.jeangazis.com</a><br><a href="http://www.boxofrain.us">www.boxofrain.us</a><br><br>"Believe those who are seeking the truth; doubt those who find it." - André Gide