Hi all,

I am running Drupal 4.7.0 on a Linux box with MySQL.

I have a peculiar problem coming up each time I enable caching in the settings. I have the forum module enabled and running. When a user is authenticated and clicks on the "forums" menu item, they get the list of forum topics, but they also see the login block on their page. If the page is refreshed, then they see their usual menu(my account, create content, log out etc).

If I disable caching, this problem goes away but now each node loads up slowly. Below I've listed some of my php.ini parameters.

Memory Limit 32M
Register Globals Off
Safe Mode Off
Session Cache Limiter none
Session Save Handler user
Upload Max Filesize 2M

Any suggestions on how to overcome this problem?

Comments

beginner’s picture

beginner commented
Version: 4.7.0 » x.y.z

An authenticated person shouldn't see the login block.
Is this a custom login block, by any chance?

In any case, the cache is not used at all for authenticated users, so the cache settings shouldn't matter.
Are you sure your users are already logged in?

How to replicate this error on a fresh Drupal install?

Amadeus123’s picture

Amadeus123 commented

Yes, I'm sure that the users are already logged in because if i refresh the browser or even click on another link, the user block becomes visible.

As to how to simulate this error, I'm at a loss. I'm trying to retrace my steps to find that out too.

Any suggestions would be helpful.

beginner’s picture

beginner commented

First, you should make sure that no contrib module is the cause.
Set a test platform on your computer, replicating your live web site if you don't want to test on your live site.
Turn off all contrib modules, and see if you can replicate the error with only core modules.

beginner’s picture

beginner commented

Btw, is this issue related to that one?
http://drupal.org/node/69985

liam mcdermott’s picture

liam mcdermott commented
Version: x.y.z » 6.0-rc3
Status: Active » Fixed

Marking as fixed since there has been no activity on this for some time. If it's still a problem, feel free to re-open this issue.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.