By greencheetah on

Hello,

I have created a Drupal site where privacy is very important. First I tried the Privacy Module but there were problems because all nodes created by any content type where privacy was an option (but not even selected) were invisible to everyone but me. So then I tried the Group Module so that users could have privacy by creating private groups. Same problem! All content is invisible to everyone but me, even content that is marked public. I have checked simple solutions like access control settings. I am at a total loss. Please help.

Thanks, Brian

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

This situation is typical when access module are installed then removed and another used wihout first resetting the node access table.

see: http://drupal.org/node/64114

greencheetah’s picture

greencheetah commented

Thanks, should I uninstall the privacy module before I run those queries? Can I use the privacy module and the groups module?

greencheetah’s picture

greencheetah commented

Okay, I uninstalled the Privacy Module and performed the queries. Now all content is visible to everyone, even private group content. Any way to fix this?

vm’s picture

vm commented

lets first get our terminology straight, There is no privacy.module it is called private.module ? correct ?

I ask because i cannot find any module for Drupal 5.x called privacy.

secondly, wen you uninstalled the module, how did you do so ? was it listed as a module under administer -> modules uninstall? and did you do so from there ? so that it removed the db information it added ? or did you just disable it in administer -> modules ?

the node access table was returned to its default state with the querries that you ran, if you want to run privacy again you will, need to reinstall them in total. Including any changes they would have made to the database.

I have never used private.module and og.module in same installation to confirm or deny that theyt will work in harmony. There used to be a golden rule, never install more than one access module into any one installation. I don't know if that golden rule has been lifted.

edit: found the answer and its no, Organic Groups does not work with other access modules. according to : http://drupal.org/handbook/modules/og

greencheetah’s picture

greencheetah commented

Yes, I am talking about the private module. And yes, I uninstalled it using the new uninstall tool.

I am going to forget about the private module for now.

So do I have to reinstall the groups module for it to work correctly? Will this erase all group content already created?

vm’s picture

vm commented

if you aren't getting any errors and your access is like its supposed to be now that private isn't part of the equation. The you are fine and nothing else needs to be done.

In the future consider "testing" modules out on a test site first, either on your server or on you local machine, so that you don't adversely affect your production environment, when you have content that can be lost.

greencheetah’s picture

greencheetah commented

I'm not getting any errors, but all group content that is supposed to be private (for subscribers to the group only) is now visible to everyone. Any idea how to correct this?

vm’s picture

vm commented

make a backup of your database.

install devel.module to reinstall the Mysql tables, the tables with information should remain and it should fix whatever is broken, you may recieve "warnings" of tables already being created. This would be understandable since you don't want to delete the tables that area there.

Personally, I would uninstall the module and reinstall it. I can't imagine you have that many things added to OG, if you just recently put the provate module in, then put in the organic groups module after ?

greencheetah’s picture

greencheetah commented

I installed the devel.module and backed up the database, but I don't know how to reinstall the Mysql tables. If it was automatic, then the problem of private content being public still exists.

I will try to uninstall the og module and reinstall it, but there is no uninstall option. I will have to do it the old-fashioned way.

vm’s picture

vm commented

after installation of devel.module, you should have enabled the devel.block in administer -> blocks and you would have had a menu item called "reinstall modules"

greencheetah’s picture

greencheetah commented

Okay, great. I will try that today. Thanks for everything.

greencheetah’s picture

greencheetah commented

I reinstalled the OG module and now everything seems to be working correctly!!!
Thank you so much!

niccottrell’s picture

niccottrell commented

This fixed it for me too - even with the reset cache button og_user_roles. I guess maybe there should be a status check in the og module admin page that can check for certain common problems like this?