Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Kyle Gilman

    (@kylegilman)

    Well, if you’re comfortable hacking a little, you could get past the check by hard-coding your URL into the plugin. In the kg_check_ffmpeg_exists function Just replace '.plugins_url("", __FILE__).' with https://www.yourdomain.com/wp-content/plugins/video-embed-thumbnail-generator/ but that might only get you to pass the check for FFMPEG. If all of the files in your WordPress installation are delivered through https then I can’t think of a good fix for you to generate thumbnails other than using the “Embed from URL” tab. In future versions of the plugin I’ll try converting https ffmpeg input to http.

    Thread Starter rriley.cs

    (@rrileycs)

    In my case things are only served over http.

    Is there a way to get the filesystem path to the plugins directory instead of using the URL? It seems like this would fix the problem. (Just access /usr/local/wordpress/plugins/video-embed-thumbnail-generator/ or whatever.) I can hack this manually into my implementation, but is there a nice WordPress to return that path?

    Plugin Author Kyle Gilman

    (@kylegilman)

    Yes, you should be able to use plugin_dir_path(__FILE__)
    I vaguely remember that there was a reason I used the URL instead of the path, but it seems like this would be better.

    Plugin Author Kyle Gilman

    (@kylegilman)

    Version 3.0 and later should solve this problem.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘https support’ is closed to new replies.