On Thu, May 28, 2009 at 14:07, Cor Bosman <[email protected]> wrote: > Im running into a little problem. message_headers_output is not always > called. If I read the next email, then go back to the previous email > where I just clicked the button (which was removed), the button re- > appears. This is not due to anything wrong with the plugin code, but > because RC sends Etags and If-Modified headers which my browser > happily uses to show me a cached version of the previous header. > > Im assuming this is wanted behavior. The more caching the better I > guess, but in this case its biting me. Is there anyway I can prevent > this from happening? Or should I just give up on trying to show the > right thing?
Looks like we have to add another hook to manipulate the caching of message views. > > (the same can be said for the addressbook-add button.. why show it if > you're already in the addressbook). You're absolutely right... > > Any tips appreciated, > You can try to implement a plugin hook in program/steps/mail/show.inc where the etag is composed. Either the hook can manipulate/replace the hashing function that creates the etag or it just returns true/false to enable/disable caching at all. I'm not sure which approach would fit best. ~Thomas _______________________________________________ List info: http://lists.roundcube.net/dev/
