Panels caching despite "no caching" setting

It seems the issue is broader than I had originally thought. For example, I have a primary links menu changing based on whether the user is logged in or not using the "account menu" module. But the state of that menu is being cached.

I also have Ubercart installed, and the price by role module installed. The aim is to discount product prices based on whether the user is logged in or not. But the price of the product is not changing because the product view is being cached despite caching being switched off in the view and on the panel pane.

If we take the menu issue above as an example, if a non-admin user logs in, the menu gets stuck on "log in" instead of changing to "My Account" and "Log Out".

But if I clear the Drupal cache manually, the menu changes as expected.

And then, if the non-admin user logs out, the menu stays stuck in the logged in state.

So it seems that site wide, there is an issue of content which should not be cached at all, or which should change when a user logs in, is being cached aggressively.

None of the above seems to happen for user 1.

Can anyone suggest where to look for a solution to this? I'm not seeing the same problems with standard Drupal installs.

Thanks for the reply, but I have caching disabled - method set to "no caching" for individual panes.

Let me explain a different way. Say, for example, I open the site in Opera and log in as an admin. I manually clear the cache.

In Firefox, I'm logged in as a non-admin user. I refresh the front page, and the Simplenews pane now displays my username with an "unsubscribe" button underneath, as it should.

In Chrome, I open the front page of the website as an unautheticated user, and I see the Simplenews pane with the Firefox user's username, and an unsubscribe button underneath. This is not correct - this user should see a text box for entering an email address, and a subscribe button. This user should definitely not see the username of another user of the site.

The only way to change the contents of the pane is to clear the Drupal cache again.

I don't understand why the panel pane is being cached at all, when the pane cache is disabled. In other cases, for example the "latest posts" pane, which is not being updated when new blog posts are added until the Drupal cache is cleared, both the panel pane and the view are set to not cached.

This is quite puzzling, very annoying. Maybe I'm missing something very simple, but sometimes when you're staring at something for long enough, you become blind to the obvious, so apologies if that is the case here.

I guess from the activity on here that you are concentrating on the Drupal 7 version and aren't interested in looking at this problem. Its a shame because this behaviour is a real deal breaker for me.

I'm now evaluating OpenPublish, and it looks like that's the way I'll go - a pity because I think I like the way things are done in Nodestream a little better.