WordPress.org

Support

[Resolved] 3.5 Support

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

    @kylegilman

    I have tested it. At the moment 3.5 will severely cripple the plugin and at the very least I’ll need to do some large cosmetic changes. I don’t know exactly how the new system is going to work. I’ve seen major changes happen in a single day. I’m going to do my best to get it working once the developers have made more progress.

    I know they’re working on backward compat. Waiting things to settle is probably a good idea. Hopefully once we hit RC (very very soon) we’ll have a good idea.

    The only reason I asked was because I was considering using it on a project and I saw some of the screenshots. I haven’t looked at how you hooked in to the media thickbox, but I know that has been a touchy area in the past.

    Plugin Author Kyle Gilman

    @kylegilman

    I’m currently using the rather lightly documented attachment_fields_to_edit hook, which now sort of works (crucial hidden fields aren’t being generated) in the new media box but doesn’t work at all in the new Media Library, which will require a new custom meta box. I was already in the middle of a huge upgrade, and I have a job right now so it might take some time for me to understand how to make it work.

    I’ve been waffling on using this for the client… but may be able to throw in some time to make it work… is your current dev committed to trunk in the plugin svn repo or do you still have a lot of uncommitted changes?

    Plugin Author Kyle Gilman

    @kylegilman

    Oh I’m nowhere near that organized. The trunk on svn is months out of date. The current dev is a mess that only half works. I’m not really a developer. I just made this thing so I could share videos with clients easier and it spiralled out of control. I’ll commit what I have to the svn in a few days but it might not help you much.

    Plugin Author Kyle Gilman

    @kylegilman

    Hi Ryan, I never committed my development work. I got sidetracked. It’s in the svn now. The good news is I asked the WordPress devs to implement the attachment_fields_to_edit hidden fields in 3.5 and it turned out they had just forgotten to do it. So with a little bit of tweaking the plugin will work in 3.5. I’m getting much closer to releasing a new version that will add a lot of functionality and will be compatible with 3.5.

    We’re just setting up a site with 3.5 and the plugin, while not working as the instructions say, works just fine for us. The only thing we need is the ability to turn off the full screen option. The site is “here’s a little peek, but come back tomorrow for the rest” thing so we can’t have users hitting the full screen option before tomorrow. Is there a way to do that? Or will it be a feature in the next release? I’m bleary from looking at so many video plugins and this is the closest to what we need.

    Thanks in advance!

    Plugin Author Kyle Gilman

    @kylegilman

    @j_folkes I have no idea how to disable full screen playback with the current Flash player. You’d also have to figure out how to disable it for the native HTML5 players. With the next release (coming soon) I’ll be including the video.js player which allows easy custom skinning through CSS and you could use these instructions to disable the fullscreen button. http://help.videojs.com/discussions/questions/12-is-it-possible-to-disableremove-full-screen-button

    How is the development of the compatible plug-in with 3.5?

    Plugin Author Kyle Gilman

    @kylegilman

    It was released about 10 days ago.

    To simply block the fullscreen playback capability of Flash player: remove the parameter allowFullScreen from the generated embed & object tags (or set it to false). Of course, this does not remove the fullscreen button from the player.

    More info here (skip to ‘Enabling full-screen mode in Flash Player’).

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘[Resolved] 3.5 Support’ is closed to new replies.
Skip to toolbar