Block pane content caching

Drupal's page cache caches whole pages. There is nothing that Panels can do about this, it happens at a very low level. It's not just the block that's cached. This caching only happens for anonymous users, which might explain why it appears differently in another application.

I'm not lying, I'm not stupid, and I'm not wrong.

To be a bit less curt: Seriously, it's not possible. Page caching is absolute. If you have page caching on, then there's nothing dynamic, and Panels never even gets loaded.

@reubidium: re-opening the issue when the module's author has marked it as "won't fix," and going the next step of dismissing his clear, direct answer IS tantamount to saying one of those three things about him. Taking the patronizing approach afterwards doesn't help, either.

Aggressive caching is not what merlin is describing. Caching is a complex issue that has occuppied the minds of many drupal devs for some time; normal page caching allowing content to "poke through" is a nice metaphor, but metaphors and code don't really mix.

I'd disagree that it warrants UI feedback, at least as the UI exists right now. Not because it's not important information, but because a) there are at least a dozen more crucial edit-time sensitive pieces of feedback that are more important, but that we don't display because the interface is already cluttered enough, and b) because the general assumption within Drupal is that those who really need to think about performance issues aren't usually doing so at the level of the interface.

You may be interested in the Boost module, it's kind of a poor man's reverse proxy cache.

If this indeed is purely impossible, then this might warrant a feature request for UI feedback alerting the user .. or something similar.

I disagree. It is not Panels responsibility to teach you how to use Drupal's features. And how are we supposed to alert the user, anyway? I can't think of anything that really makes sense here. The fact is, you turned on a feature that does X, and it caused unintended side effect Y, and you're trying to pin the responsibility on Y.

Sir, I was not implying you were lying or stupid. Geezus. Please let us try to keep the spirit of community and professionalism here. Remember we are all representing the Drupal community and by extension the Drupal brand.

Let's examine:

I said:

There is nothing that Panels can do about this

You retorted:

come on now, there must be a way.. i don't buy that this simply isn't possible.

Perhaps of the 3, 'stupid' was not really implied. But certainly 'wrong' was implied, despite your obvious lack of knowledge of Drupal internals (no offense meant by that either, I don't expect that to be common knowledge), and either 'lying' or 'mistaken' are the two possibilities for being wrong. I thought I was quite clear in my commentary as to why it was not possible, and since you didn't address that, I admit that 'lying' was pretty much the conclusion since you obviously had no argument that I was merely mistaken.

The point being, if you have something to support an argument, that's fine, but since you're really unhappy with how a core feature is working, please address that with the core issue queue (though they would likely shut such a feature request down there as well) rather than here.

As I've said before, and I will say again, there is nothing Panels can do about this, and I do not agree that it is Panels responsibility to warn you that caching will reduce the dynamic nature of the page. That warning would simply become text that doesn't get read and takes up space. It would be more annoying than it is valuable.