You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really need to clarification about Timber's cache methods... i just don't understand anything...
Here is an exemple :
I create a little social network with WP & Timber.
I made some test using Cache the Entire Twig File and Data method as describe in the documentation (Timber 1.19)
In the documentation it is said that this cache method, musn't be use i there are any context depend subview.(eg. current user).
In my case, i have a top menu bar with the profil image of the current loggedin user.
If i load the same page, with different account (different session in the same time), my top bar is always the right one (the profil image is updates according to the loggedin user).
I can see that Timber create multiple transient key, for each user which ask a particular page...
So why this method is not recommended ? It's appear to work well, except that it create a lot of transient (one per page / per user). So if i've multiple user at the same time, perhaps this can inflate the database...
Is there any personn to discuss about the differentes Timber's cache methods, and how to have a great strategy with it ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone.
I really need to clarification about Timber's cache methods... i just don't understand anything...
Here is an exemple :
I create a little social network with WP & Timber.
I made some test using Cache the Entire Twig File and Data method as describe in the documentation (Timber 1.19)
In the documentation it is said that this cache method, musn't be use i there are any context depend subview.(eg. current user).
In my case, i have a top menu bar with the profil image of the current loggedin user.
If i load the same page, with different account (different session in the same time), my top bar is always the right one (the profil image is updates according to the loggedin user).
I can see that Timber create multiple transient key, for each user which ask a particular page...
So why this method is not recommended ? It's appear to work well, except that it create a lot of transient (one per page / per user). So if i've multiple user at the same time, perhaps this can inflate the database...
Is there any personn to discuss about the differentes Timber's cache methods, and how to have a great strategy with it ?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions