Inaccurate status history
-
Since version
1.8
, the history queries are cached via transients, which dramatically improves speed and lowers DB calls during the display of the Orders and Users screens. The trade-off though is that the Orders history column information might be at times inaccurate, as is now rebuilt with some delay of up to 1 hour. If that’s an issue to you, theBulk action -> Rebuild history cache
allows updating the history cache manually.Additionally, filter
oshwoo_cache_ttl
, (goes intofunctions.php
), can help control the baseline of how long the cache stays fresh before going stale and rebuilding itself (default is 1h). Example usage:add_filter( 'oshwoo_cache_ttl', function(){ return 0.5; });
- The topic ‘Inaccurate status history’ is closed to new replies.