Log out problem with Drupal

Thank you for taking the time to try to help.

Yes, I can confirm Step 5 from the original description.

I have just checked again.

User permissions are set such that anonymous user cannot access any blog or forum functions while authenticated users and other roles can. However, under node access anonymous users are checked to have access otherwise they cannot see the default front page when first coming to the site.

The Navigation block permissions exclude anonymous users but when step 5 is executed the logged out user cannot get into "My account" or "Create content" but can get into "My blog", "Recent Posts", "Feed aggregator", and "Category browser".

I have also created a block called Features Menu that includes two items, one for blogs where "?q=blog" and the other for forums where "?q=forum". Again, I have checked the block permissions and anonymous users are excluded yet these functions are still active for the logged out user.

If the logged out user truly became an anonymous user with the correct permissions that might be fine but that is not what I am finding.

I hope the additional clarification is helpful. Any suggestions are welcome. Thanks,

Izzy

Thanks for this. I will try it out and report back.

Izzy

gpk Thanks very much for your help I believe the problem is solved.

I don't know if this is right, but I have changed the topic Priority to normal and the Status to fixed.

I discovered that:

1. There was a conflict with the beta version of Site doumentation module (v 1.5.2.1) and the logout; sometimes causing the logout not to reset the left bar where we have the user navigation menu to the default. Not a criticism, something to be expected at this stage of development.

2. I have not had time to try the tac_lite module and look forward to adding that as it seems the behaviour we are now experiencing is exactly as you describe. To make some content visible to an anonymous user we had to give user permission to content access. This has made other Page views visible, but not any custom views created with the Views module.

Thanks very much,

Izzy

On further testing I have found that Site doc is not the problem.

The problem is in setting the Drupal Performance page cache to "normal" as recommended for production sites. Site doc just alerted me to the fact that it was originally disabled. I have since disabled it and the main problem of the left bar continuing to show the navigation menu even after logout has been resolved. I left Block cache enabled.

Sorry, for an confusion with my earlier false alert to the Site doc module. Just as well I didn't rush to send such a notice to those developers.

I still need to get to the Tac-Lite module up to deal with content.

Thanks for all your help

Izzy

Thanks for hanging in there with me on this one, gpk.

I haven't had time to take that any further right now as the object is to have the site up and running yesterday. So, as you can appreciate, now that this one is sufficiently advanced there are other priorities.

I changed the status of the message back to active (needs more info), hope that's the right thing to do.

There are a couple of other items that I should maybe post under a separate title. Although, they are closely related and have to do with the Login and registration sequence.

I am trying to integrate the Drupal Login with LoginToboggan, the Front page module and Autologout which I understand are early adaptations.

1. I seem to be having trouble locating the message displayed to users when they have registered. I need to change that because on this site users must be authenticated first. It works fine but I need to change that message.

2. The web links that are sent to users when they have been authenticated and whenever they request a password default to one day. I need to change these. One value would be fine but each separately would be better, I think.

3. Also is there a default logout message that is displayed or is it just the return to the beginning default page? This is a lower priority to me but it would be nice to have the choice.

Again, thanks for the help.

Izzy

I have installed Drupal 6.2 and the behaviour seems to be fixed to what I was expecting. I haven't had time to fully test this but noticed two items in the Drupal bulletin http://drupal.org/node/244667 that may have resolved this:

http://drupal.org/node/232037 by pwolanin: (performance) block regions should only be populated when called for, not in all cases (fixes performance expectation on 403/404 pages)

http://drupal.org/node/226728 by chx: (performance) temporary cache table entries were not flushed, causing cache_menu and cache_form to grow big

Izzy

This issue is discussed further at

http://drupal.org/node/197786

Unfortunately someone recently changed the title of the post. It used to be something like "authenticated content still visible after logout" which I thought was a more appropriate title.

Fortunately, there is a solution in comment #61 http://drupal.org/node/197786#comment-1055633 of that thread that is worth trying. I have been very happy with it. http://drupal.org/node/197786#comment-1649624

My previous comments in this thread were from last year when I was more of a neophyte. I now realize that my solution was not a true solution but simply the result of using the Advanced front page module and not allowing anonymous users access to content and setting permissions to allowing anonymous users to access Advanced front page.

But, check out the other thread. The solution is a hack to core, but hopefully sometime soon the experts will find a solution to commit. Meanwhile, I am using the solution offered there.

Hope this helps,

Izzy