Morning jivanmukta;
tick the checkbox to empty wp youtube lyte’s cache, after that it should fetch the data from the YT v3 API.
frank
Hello Frank,
thanks for your very quick answer, only few minutes after my support request 🙂
I forgot to mention that I had already ticked the checkbox but still the youtube device support video is displayed.
I have retried to tick again the wp youtube lyte’s cache option but seems that the option is not saved after that I click the save button, I still see the checkbox unchecked.
I have also disabled my cache plug-in (wp fastest cache) but the issue does not disappear.
Thanks in advance
Regards
Well, “empty cache” is a one-time option, which after activation triggers the lyte cache to cleared and then is switched off again.
I have already seen occurrences of lyte’s cache not being entirely cleared (not sure why), but as this is stored as post_meta, you can tell WordPress to show it as a custom field by adding this code in a small helper plugin or in your (child) theme’s functions.php;
if (is_admin()) {
add_filter( 'is_protected_meta', 'lyte_unprotect_meta', 10, 3);
}
function lyte_unprotect_meta($protected, $meta_key, $meta_type) {
if (strpos($meta_key,"_lyte_")===0){
return false;
} else {
return $protected;
}
}
If you do that and you go to the “edit post” screen, then you will see a custom field with a name that starts with _lyte_ and then the YouTube id (e.g. _lyte_wHENTMGVb74). Go to the post that has the “youtube device support” video, delete the _lyte_<videoID> custom field, update your post (confirm there’s no custom field _lyte_<videoID> any more and then visit the page again to have lyte-refetch the info from YouTube (api v3).
Let me know how that works! 🙂
frank
Hi jivanmukta;
Had a quick look at your site, but the problem is not WP YouTube Lyte (which seems not to be used), but “Youtube Channel Gallery” which has a huge thread about this very problem in the support forum?
good luck with your endeavors,
frank
Hi Frank,
you are right, sorry, my mistake 🙂
I had also WP YouTube Lyte installed on this website (and other websites), so I thought this was the problem.
Thanks anyway for your deep and good support!
Regards
Massimiliano