Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This is technically not an AF issue but it affects forum use quite a bit. Node Comments caches the topic view for performance reasons. That's pretty important to keep the topics from being horribly slow. But this caching has some serious trade-offs. I'm creating this issue in the hopes of getting some bright ideas by people who know more about views caching than I do.
Here are the conflicts I've encountered so far:
- Author Pane - Got around by putting a token in that gets replaced.
- Signatures
- Ignore posts by certain users
- Special classes on posts to indicate new posts and more
I think there's more that I'm forgetting but the gist is that anything that is different in the topic based on who views it conflicts with this caching. I'm hoping there is some way around this besides going the token route that was done with AF. Possibly some alternate caching that will cache just the data but not the whole thing? I know I need to learn more about Views caching and will at some point. In the mean time, it would be great if someone who already knows a lot about it could look into this and see if there's anything that can be done.
Michelle
Comments
Comment #1
michelleAdded core signatures to tokens. Signatures for Forums requires too much of the node so it's impossible to get out of the caching without defeating the caching.
Added last post edit to outside of cache.
Michelle
Comment #2
michelleReminder: Still need to do #4 because the code is in there and not useful as is. #3 will likely get shifted to its own issue as it is a major project.
Michelle
Comment #3
michelleOh... Should tag it as an alpha blocker as well. Somewhat of a bug to have code in there that isn't useful.
Michelle
Comment #4
zack85 commentedWith signatures for forums, why not just clear the cache whenever someone updates their signature? People only update their signatures after weeks or months so it would not affect performance like it would if you took that route for author pane which could mean clearing cache multiple times a day for each user.
In fact wouldn't clearing cache when they update signatures (signature for forums) actually be even better performance wise than the way standard signatures are handled which requires pulling the signature from the database for every post?
Comment #5
michelle@zack85 - Yeah, that's what needs to be done but that's not something AF should be doing. That's a SfF issue.
Michelle
Comment #6
michelleOk, got the post-by-viewer class working. That's all I'm doing on this issue for now. The whole ignoring thing will be a separate project at some point.
Michelle