Hi Danny,
We have tested with qtranslate in the past and haven’t encountered any issues. We’ll need to do some testing to see what might be going on. Let us do a bit of testing and get back to you with our findings.
Thanks for the follow-up. please let me know if you find the issue
Danny
Hi @dgdesign,
I’ve done some thorough testing and was able to track down the issue for you.
In short, our caching mechanism stores the Timeline Express shortcode markup inside of your cache for a little while. This is done to prevent multiple queries being run each time the Timeline page is loaded, which is especially helpful when Timelines get lengthy.
This would result in a major slow down of our users sites, so this was put in place to prevent our plugin from having any major negative effects on our users sites.
All of this to say, if you add the following snippet of code to your themes functions.php file – the issue should resolve itself.
/**
* Clear Timeline Express cache on qtranslate pages
*
* @author Code Parrots <[email protected]>
*/
function timeline_qtranslate_bust_cache() {
global $post;
if ( ! isset( $post->ID ) || false === get_transient( "timeline-express-query-{$post->ID}" ) ) {
return;
}
delete_transient( "timeline-express-query-{$post->ID}" );
}
add_action( 'qtranslate_head_add_css', 'timeline_qtranslate_bust_cache' );
Essentially, the code is going to check if any cache is stored for the current page and clear it if it does, specifically for our Timeline Express plugin.
Let us know if that works for you. We’re going to put together a knowledge base article explaining the issue further.
Thanks for bringing this to our attention.
