My idea to use this module to create a new content type, called: splash_page, then assign "view" permission to Anon Users. Everything was fine until I remove nodeaccess module.

After I remove nodeaccess module then Anon Users ONLY see the "first time Drupal page" (a page with: Welcome to your new Drupal website! Please follow these steps to set up and start using your website), look like I do a new Drupal site installation. But Registered Users has no problem, they could see any page after login.

I have try to do this task but not help:
- remove nodeaccess
- delete nodeaccess table
- empty drupal cache table
- empty browser cache

Any idea to fix my site?

Comments

marcor’s picture

marcor commented

You are right, this could be made better. But I don't really consider it as being a bug, it's rather a question of support or a new feature. This kind of problem is typical of all modules dealing with new strategies of node access. It's always better to have your database saved before you make changes like these. I had to learn myself short time ago. My still working solution is described here: http://drupal.org/node/122489
You have to look variables table for nodeaccess variables and to change node_access table to default state. If you had other access modules installed before, you might have other settings than the default.

Hope it helps.

drupalnesia’s picture

drupalnesia commented

MarcoR, as we know Drupal only support Access Node. Why you don't add another check boxes for each additional content types directly in administer-access control.
Also, I still don't understand why the core team only support 1 Access Node for entire content types while they support "edit content" for every content types?
Does Drupal 6 will give more control for each content types?

I hope you idea/module will be in Drupal 6 core!

marcor’s picture

marcor commented

I didn't promote a new module - the link just points to advice how to de-install the module if someone ran into problems! ;)

Anonymous’s picture

Anonymous (not verified) commented

How do you mean remove the module? I tried on the test site and when you disable the module (uncheck it in admin modules) it reverts properly to the default permissions of everyone can view everything. If you choose uninstall on the Modules -> uninstall page, it should then get rid of everything.

Did these steps not work for you?

drupalnesia’s picture

drupalnesia commented

Remove mean I really delete this module directly using Windows Explorer. As you suggest, I do reinstall this module and everything fine now.
After a while test this module I think I must include this module in my every project. This module should be part of Drupal core! Thank to provide this great module.

zeitenflug’s picture

zeitenflug commented
Priority: Critical » Minor
Status: Active » Closed (fixed)