Support » Everything else WordPress » I'll try my luck here with the FLV Embed MYSTERY…

  • Problem – WP blog plays video on ‘index’ page, but will not play EXACT same video on any other pages of blog.


    Blog URL –
    2ND page with SAME FLV code –

    Checking View Source, you will see that both possess the SAME embed code pointing at the SAME movie.

    Home page plays movie, Talent page does not.

    Can ANYONE explain this mystery?

Viewing 15 replies - 1 through 15 (of 26 total)
  • PS, I have tried EVERYTHING. Moved files around root, moved into separate folders, changed paths, even deactivated ALL plugins as well as scaled back to BASIC 2011 theme.

    The problem seems to be somewhere in some hidden corner of the WP core code that is STOPPING a second iteration of an FLV to play anywhere on the site once there is a reference to the FLVPlayer_Progressive.swf in the root.

    Ok, that’s just conjecture. I have NO IDEA. Seriously, though, there MUST be an answer…someone has to have had this problem before, or be able to see the WP code, like the Matrix, and knows just where the code is stopping my movies from playing…

    hopefully and pensively crossing my fingers and whimpering….

    Chris Olbekson


    Level 12 Bug Squasher & Forum Moderator

    The problem is with the path to the .swf file.

    <param name="movie" value="FLVPlayer_Progressive.swf">

    This works on the home page because the file is in your website root directory. When you are on an internal page the browser is looking for this file relative to what page you are on and returning a 404 not found error.

    To fix this make the path to FLVPlayer_Progressive.swf absolute.

    Ok, that makes sense except on both of those pages, it is simply pointing to the exact same movie.

    So, in the interest to trying it again, I did. Here was the resulting code (which you can see live on the domain)

    <div id="apDiv1">
      <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="325" height="483" id="FLVPlayer">
        <param name="movie" value="" />
        <param name="quality" value="high" />
        <param name="wmode" value="transparent" />
        <param name="scale" value="noscale" />
        <param name="salign" value="lt" />
        <param name="FlashVars" value="&MM_ComponentVersion=1&skinName=Clear_Skin_1&streamName=/intro/intro&autoPlay=true&autoRewind=false" />
        <param name="swfversion" value="8,0,0,0" />
        <!-- This param tag prompts users with Flash Player 6.0 r65 and higher to download the latest version of Flash Player. Delete it if you don’t want users to see the prompt. -->
        <param name="expressinstall" value="../Scripts/expressInstall.swf" />
        <!-- Next object tag is for non-IE browsers. So hide it from IE using IECC. -->
        <!--[if !IE]>-->
        <object type="application/x-shockwave-flash" data="" width="325" height="483">
          <param name="quality" value="high" />
          <param name="wmode" value="transparent" />
          <param name="scale" value="noscale" />
          <param name="salign" value="lt" />
          <param name="FlashVars" value="&MM_ComponentVersion=1&skinName=Clear_Skin_1&streamName=/intro/intro&autoPlay=true&autoRewind=false" />
          <param name="swfversion" value="8,0,0,0" />
          <param name="expressinstall" value="../Scripts/expressInstall.swf" />
          <!-- The browser displays the following alternative content for users with Flash Player 6.0 and older. -->
            <h4>Content on this page requires a newer version of Adobe Flash Player.</h4>
            <p><a href=""><img src="" alt="Get Adobe Flash player" /></a></p>
          <!--[if !IE]>-->

    It clearly is now pointing to that resource. (whimpering….)

    This is the confusing part. This is what has me hng up. I tried the ‘change paths’ thing previously. But, thought because you mention it, I might try again.

    And, as you can see at the site now, both pages have same code, and only ONE is playing.

    (tearing up….)

    What d ya think sir….?

    And let me clarify, when I say same code, I mean I made the adjustment in the ‘secondary’ file page so that it would point to the same files, with your suggestion about changing the path to the swf for page two and beyond….

    Did I miss your direction?

    Chris Olbekson


    Level 12 Bug Squasher & Forum Moderator

    Not sure why it is not working. Your best bet is to contact the vendor for support,

    The only vendor that seems to be an issue would be Worpress. I can get them to play on static pages. In different folders on different pages. Its ONLY a Worpress issue.

    But thanks again.

    And sorry about the other post. Didn’t realize it was same forum. I wanted to spread this around to as many areas as possible…’s a crazy problem

    Moderator Ipstenu (Mika Epstein)


    πŸ³οΈβ€πŸŒˆ Halfelf Rogue & Plugin Review Team Rep

    WP doesn’t include an FLV player (it’s not GPL) so … no. Not so much us πŸ˜‰

    You see how you have lines like this?

    <param name="expressinstall" value="../Scripts/expressInstall.swf" />

    Those are all relative URLs and can be problematic. What plugin are you using for FLV?

    Mika – thanks for chiming in.

    First off, I have done this with and without plugins. Just to test, I deactivated ALL plugins and just did a basic copy and paste into the HTML editor. And, the result was that on the first page, the video streamed, on page two, nothing.

    As for the plugin that I have decided to use (ONLY) to manage the structure of the embed code, Embedit. And, as usual, when I embed it into the first page, works as you see. On any other pages, nothing.

    And just FYI, in the last 24 hours, I have tested other ideas. I have changed all paths back and forth from relative to absolute. I have tried it all.

    When it’s a static HTML page, no problems. When it is a video of this type on the ‘index’ page, all is good. When I add this EXACT code that is on page one, to page two, nothing.

    This is the strangest thing. It almost feels like I have found a bug. I posted to the hackers list to see if someone there may have seen this before. I am coming to the slow conclusion that this may be a bug unknown to date….(wouldn’t that be cool to find a bug….)

    I am stuck though. I can’t seem to find ANYTHING that changes what the results are.

    What does it seem like to you?

    (i’m so confused…..softly crying…)

    Currently (you may have changed the code) – the problem is as stated previously – your relative links are causing the player not to load.

    On the sign up page, your embed code is looking for:

    Which of course doesn’t exist, and returns a 404.

    In addition, even if you correct that it’s then going to look for your player skin file:

    Which will further prevent the player from loading.

    So if you were changing from relative to absolute and overlooked the skin URL, that could explain why you didn’t get the results you seek.

    Ok, now that makes some sense, but let me ask you this. Are you inferring that everything after the ‘talent-sign-up-here-to….’ is a directory?

    Please don’t laugh. Let me

    That is a page. I ‘add new”d a page, and named it ‘talent sign up here to become a conversion assistant’. As you know, what we are looking at is the slug for that page.

    So, my question is this. How does WP look behind the page, for files? In other words, in terms of ‘directory structure’, I get how on the first page it is seeking the FLVPlayer_Pregressive.swf in the root. That is the path there.

    But on the second page, the path points to the same player – <object classid=”clsid:D27CDB6E-AE6D-11cf-96B8-444553540000″ width=”325″ height=”483″ id=”FLVPlayer”>
    <param name=”movie” value=”FLVPlayer_Progressive.swf” />
    <param name=”quality” value=”high” />

    only the path to the file has changed. And again, I apologize for extending this further than I imagine I needed to…

    But how is it again, that WP is looking to the root of the ‘talent-sign-up…’ when that isn’t a directory? Shouldn’t it just look to the root for the same player each time?

    Thanks…..I REALLY appreciate your help…

    WP isn’t looking for anything – your browser is.

    <param name=”movie” value=”FLVPlayer_Progressive.swf” />

    That is a relative URL:

    It’s meaning is relative to the context in which it appears. In this case on a page whose URL is :

    So your relative URL = when the browser tries to load the player.

    Ok. Now I know I sound like I don’t get what you’re saying…I do.

    It’s just that I am learning something new here and I want to make sure I get it.

    So, let me just take a sec…

    Here is an example of what I was referring to in terms of ‘directory’ versus ‘page’ (which I am sure you clearly understand, I think it’s me..)

    On this page –

    All elements are seeking the FLVPlayer_Progressive.swf that is in the /test/ directory. I get that.

    On this page – view-source: same thing. The FLVPlayer_Progressive is IN the root folder of where THIS document resides, and as you explain, that is where the browser is looking for the player.

    This makes sense to me so far.

    Where I get lost is how this works on WP when it’s a dynamic page. In the above examples, the forward slash indicates (usually) a directory switch – from the root of the domain, to either a ‘page (html, php or otherwise) where it terminates, OR, into a new directory (like /test/).

    In this case, the /talent-sign-up-…/ is only pointing to a page, not a directory, as in test.

    Now according to your example, in my working examples above, the /test/ example for instance, you are saying that the browser is looking for the player at when we know that it is ‘finding’ it at (working version)

    So in this case, it would logically follow (by the examples that are working) for the non working page ‘talent’ the path to the player SHOULD be, based on what works elsewhere, since there is no directory to PUT the player file into at…/ (its just not a directory like /test/ so I don’t understand how IT is the place where the browser is looking to, for the file….)

    Geez I hope that made sense….and please know I am NOT trying to be difficult. I like your logic, except there just isn’t a ‘directory’ to put the FLVPlayer file into at the /talent-sign…/ location….


    Ok….now while just thinking through this, here’s a question….and I ask it because of this;

    The page we are in discussion abut is dynamically created. This is my issue with the path. It has the markings of a directory, but it is a dynamic piece of content only generated when a link in WP is clicked.

    Question – is there a way to add code to my WP core, that would tell WP to always use the FLVPlayer that is located in ONE specific place?

    This way, I could have the player file in ONE place and just worry about the paths to each of the files individually.

    See, I think the issue is much of what you are saying. There is a hiccup in the path process here. But it’s not anything I could fix on my end because as I have said, there is no where to PUT the FLVPlayer_Progressive file at the path you describe. that is obviously because of it’s dynamic nature.

    So, it seems the only way would be to hardcode the location of the player file for universal use all around the WP site…..

    Does that make any sense?

    Just for reference, I changed the paths on the ‘talent-…’ page to point to the directory WHERE the FLV file is (the one playing successfully on the index page) and still nothing.

    Ya know…I just wanted to mention, the page that is playing the video now, is set as the ‘static page’ in the blog (it’s one of four pages created on the blog). Is it possible there is something to the idea of the ‘static’ page element? I’ll test it while I’m away, but I was just wondering…because the page that is playing a video was created the same was the page that isn’t was. That’s what is so confusing.

    Same method. Same page concept. Same embed (exactly and with path changes) and only one page will play.
    ok enough rambling….sorry.

    NEW NEWS!!!!! Haven’t solve it yet, but here is what I tried (based on my last post)

    I turned off ‘static front page’ and set it to ‘last posts’ (The reading setting…of course)

    And this stopped even page ONE from loading. So now, with the blog as a non static page blog, NO videos play….?

    The code was COMPLETELY stripped out. Nothing there. Now maybe I am into another problem here, but what the heck is going on with THIS?

    I turned off ‘static front page’ and all of the suddent ALL of the embed code is stripped out?

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘I'll try my luck here with the FLV Embed MYSTERY…’ is closed to new replies.