Quote:
Originally Posted by KirbyDE
|
another question about this. the code you recommend to use in the link above. is the caching done because of the code change or is it because of the hook it belongs to?
as it is now...it works great. when i add the add on, using the option to switch postbits (in the thread display mode menu) doesnt change the postbit. rather...it does, but it requires a refresh after clicking the option. if i use the code in the post you linked to...but change the hook to postbit_display_complete the refresh is no longer required and using the thread display mode menu option changes the postbit accordingly.
i guess what im trying to figure out is...are the additional queries you refer to being caused because of the hook used or the code used...