-
(url redacted)
So what started happening recently is that it takes ages for the play button to appear and it seems to be loading nothing. The video, once you’re able to press play works perfectly and doesn’t appear to be slow at all, it’s just the initial loading that it hangs on. Any ideas?
-
-
Forgot to mention, I updated the plugin around the same time this started happening. Checked the server for issues and couldn’t find anything wrong.
Hello Johnny,
I see there is a JavaScript error coming from the minified file at //cdn.foliovision.com/wp-content/litespeed/cssjs/f331b.js?13306
Please try to disable that optimization and see if that fixes the issue.
If that works, then try to exclude the fv_player_pro.min.js file from the optimization and see if that help. LiteSpeed has some nice documentation about it here: https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/#test-the-list
I can see the issue occurs after vttCssDef in our code. But I want to be sure the issue is with our code and not some other plugin as we don’t run into these issues with minify.
Thanks,
Martin
Thanks, that worked perfectly. Exactly like you said; Disabled JS Minifiy, button loaded fast again, then I excluded fv_player_pro.min.js & enabled JS Minify and it still loads fast. Thank you very much.
Hello Johnny.
it seems we can install that Litespeed WordPress plugin and try to use its JavaScript minify function to figure out the reason why it won’t minify FV Player Pro properly.
Thanks,
Martin
Actually might’ve cheered too soon. It’s still happening so I had to disable JS Minify again, at least we know it’s related to that. Any idea what else it could be? If it helps I could provide an account so you can poke around.
Hello Johnny,
we are planning to test that plugin ourselves and fix what’s necessary to improve FV Player Pro compatibility.
Thanks,
Martin
Hello Johnny,
we haven’t run into any issues during our test. If you have some time, please try to enable JS Minify again without excluding fv_player_pro.min.js and see if the issue still occurs. Perhaps one of the recent updates did fix that issue.
Thanks,
Martin
