HIATUS

[uudon]

Knight Yoshi

http://www.gaiaonline.com/profiles/unknighted-yoshi/15388423/

http://youtube.googleapis.com/v/INITIAL_VIDEO?listType=playlist&playlist=videoID1,videoID2,videoID3

http://youtube.googleapis.com/v/ighEKw6RDBQ?listType=playlist&playlist=ighEKw6RDBQ,1tjfjuPZTWg,7qH4qyi1-Ys

As you can tell, the URL will get quite long for multiple videos, but it works.

❀❀ - - - 春が来た

YAY thank you for sharing this!!!
I'll add this cool code to the guide~ C:
This is so awesome! thank you so much! <3


- - - ❀❀

[Knight Yoshi]

Brink Kale

Knight Yoshi

http://youtube.googleapis.com/v/v-_PhgzVKsE?listType=playlist&list=PL3A3DB79E82B4F130&version=3

I mentioned this in your thread somewhere if I'm not mistaken. version=3 will make it use list since it uses version 2 by default on the googleapis.com domain. As an alternative for a 'very long playlist' of course.

Both listType and playlist parameters are AS3 explicit, I do not specify the AS3 parameter on my profile and it works just fine, so using the Google API URL is not AS2 by default.

https://developers.google.com/youtube/player_parameters#playlist

Edit: Also, if you think about it. If that was the case, then you wouldn't have to use ?/&version=2 to be able to turn the video into a "video bar". Which is not the case you have to manually set the version number in order to do so.

[Melchiore]

Knight Yoshi

Allow me to explain then.

Youtube's flash player modifies the version it sends based on some, not all variables sent within the url as well as the headers sent from the how the connection is made. I will also add that the Youtube Dev documentation has been erroneous and missing critical information since version AS2.0 came out, it is sufficient enough for use on GaiaOnline though. The player still has many hidden flash vars available to it that a lot of people can't readily find within documentation. This is from a culmination of "experimental" features as well as core functionality being mixed and mashed together. fmt and a number of other features were available in youtube's pure v2.0 player a long while ago but, was never documented until they removed it from the main player in an update (so v2.1?). I'm sure you can understand that Youtube itself suffers from rather poor internal documentation which reflects on the outside documentation of its product. Feel free to read through and actually test the developer documentation to see the inconsistencies yourself.

That being said, what I was saying to you is that. When the youtube.googleapis.com player is loaded raw, it will use the Version 2 player; if you explicitly define version=2 and version=3 on the player, you can spot the differences in the player look. The player look is traditionally how Youtube defines its player version, Version 1 was drastically different from Version 2 and Version 3 keeps with this tradition. However, the look in this case doesn't always define the player type used based on certain triggers.

Now, building on that. When you call youtube.googleapis.com with certain variables, it will push out a version 3 player just as, when you call the youtube.com player specifically with version=2 specified it redirects over to youtube.googleapis.com's player because they are looking to phase out the main support of Version 2 just as they got rid of Version 1. Consider googleapis.com to be their archive site in this case.

An example of what I mean;
click these links, don't embed them.

Version 2:
http://www.youtube.com/v/v-_PhgzVKsE?version=2

Version 3:
http://www.youtube.com/v/v-_PhgzVKsE?version=3

Notice if you explicitly define version 3, it won't redirect. It does however still redirect to version 2 when no version is specificed (http://www.youtube.com/v/v-_PhgzVKsE) on link load and then on embed headers, it directs over to version 3 (http://youtube.googleapis.com/v/v-_PhgzVKsE) when no version is specified.

The version is a specific command that forces the player to use a specific version of the script for the base player. The reason that playlist works in AS2 is because the playlist command was actually in AS2 but, never properly documented and thus, it shows up on their documentation as a AS3 command. The way that the player is programmed however, is still a remnant of how the old version would look for a playlist parameter (before the AS3 version was released) and it calls on the base programming (AS2 and AS3 are actually running under the same base script, just imagine it as a bunch of if and elses that have been badly scattered about). The reason that "list" doesn't work in AS2 is because it was never a variable the player looked for until AS3 and thus I can imagine inside their coding, list is written in such a way that it only applies the data when version 3 is shown as active.

I was actually interested in trying to remember how the old playlist parameter worked to see if one could actually use it in that method.

The reason for the differences in case you were interested is because both player types use two different methods of reading data from the Youtube server (because they are encoded differently). AS2 was written back when Web Standards were lax and XHTML was a big thing. If you read through youtube's gdata you could actually see the differences yourself. If you want me to actually find working examples of that, let me know. I'll do some digging. If I'm not mistaken, the current format Youtube would send its data would be pure XML with an sort of RSS mix to it, you could subscribe to certain things such as a playlist via this RSS formatted feed.

Spoilered because its not really for the faint of heart, its a eyeful, irrelevant to the OP's topic, etc.

the TLDR:

I was actually just bringing across to you the point however that Youtube's player in embed mode will use AS2 by default when the playlist and listType variables are defined (no clue why, might be a bug). Force it into AS3 and you can use the actual playlist instead of a just a list of videos.

An example of how this is bugged;
http://youtube.googleapis.com/v/ighEKw6RDBQ?listType=playlist&playlist=ighEKw6RDBQ,1tjfjuPZTWg,7qH4qyi1-Ys&version=3

Embed that, it starts off in AS3 mode (it displays "This video is too small to be played" or whatever) and then forces itself over into AS2 mode and actually plays the video (which in AS3 mode is both, too small for viewing if its under sized and supposed to be blocked by VEVO from being embedded outside of youtube).

Take what I say with a grain of salt though. I'm not a Developer working with Youtube so I don't know their internals. I've just been using and working around Youtube for long enough that I can catch these things based on past experiences.

Edited for coherency? (if you can call writing this post from 1am to 3am on a Saturday coherent).

[Knight Yoshi]

Brink Kale

Knight Yoshi

Allow me to explain then.

Youtube's flash player modifies the version it sends based on some, not all variables sent within the url as well as the headers sent from the how the connection is made. I will also add that the Youtube Dev documentation has been erroneous and missing critical information since version AS2.0 came out, it is sufficient enough for use on GaiaOnline though. The player still has many hidden flash vars available to it that a lot of people can't readily find within documentation. This is from a culmination of "experimental" features as well as core functionality being mixed and mashed together. fmt and a number of other features were available in youtube's pure v2.0 player a long while ago but, was never documented until they removed it from the main player in an update (so v2.1?). I'm sure you can understand that Youtube itself suffers from rather poor internal documentation which reflects on the outside documentation of its product. Feel free to read through and actually test the developer documentation to see the inconsistencies yourself.

That being said, what I was saying to you is that. When the youtube.googleapis.com player is loaded raw, it will use the Version 2 player; if you explicitly define version=2 and version=3 on the player, you can spot the differences in the player look. The player look is traditionally how Youtube defines its player version, Version 1 was drastically different from Version 2 and Version 3 keeps with this tradition. However, the look in this case doesn't always define the player type used based on certain triggers.

Now, building on that. When you call youtube.googleapis.com with certain variables, it will push out a version 3 player just as, when you call the youtube.com player specifically with version=2 specified it redirects over to youtube.googleapis.com's player because they are looking to phase out the main support of Version 2 just as they got rid of Version 1. Consider googleapis.com to be their archive site in this case.

An example of what I mean;
click these links, don't embed them.

Version 2:
http://www.youtube.com/v/v-_PhgzVKsE?version=2

Version 3:
http://www.youtube.com/v/v-_PhgzVKsE?version=3

Notice if you explicitly define version 3, it won't redirect. It does however still redirect to version 2 when no version is specificed (http://www.youtube.com/v/v-_PhgzVKsE) on link load and then on embed headers, it directs over to version 3 (http://youtube.googleapis.com/v/v-_PhgzVKsE) when no version is specified.

The version is a specific command that forces the player to use a specific version of the script for the base player. The reason that playlist works in AS2 is because the playlist command was actually in AS2 but, never properly documented and thus, it shows up on their documentation as a AS3 command. The way that the player is programmed however, is still a remnant of how the old version would look for a playlist parameter (before the AS3 version was released) and it calls on the base programming (AS2 and AS3 are actually running under the same base script, just imagine it as a bunch of if and elses that have been badly scattered about). The reason that "list" doesn't work in AS2 is because it was never a variable the player looked for until AS3 and thus I can imagine inside their coding, list is written in such a way that it only applies the data when version 3 is shown as active.

I was actually interested in trying to remember how the old playlist parameter worked to see if one could actually use it in that method.

The reason for the differences in case you were interested is because both player types use two different methods of reading data from the Youtube server (because they are encoded differently). AS2 was written back when Web Standards were lax and XHTML was a big thing. If you read through youtube's gdata you could actually see the differences yourself. If you want me to actually find working examples of that, let me know. I'll do some digging. If I'm not mistaken, the current format Youtube would send its data would be pure XML with an sort of RSS mix to it, you could subscribe to certain things such as a playlist via this RSS formatted feed.

Spoilered because its not really for the faint of heart, its a eyeful, irrelevant to the OP's topic, etc.

the TLDR:

I was actually just bringing across to you the point however that Youtube's player in embed mode will use AS2 by default when the playlist and listType variables are defined (no clue why, might be a bug). Force it into AS3 and you can use the actual playlist instead of a just a list of videos.

An example of how this is bugged;
http://youtube.googleapis.com/v/ighEKw6RDBQ?listType=playlist&playlist=ighEKw6RDBQ,1tjfjuPZTWg,7qH4qyi1-Ys&version=3

Embed that, it starts off in AS3 mode (it displays "This video is too small to be played" or whatever) and then forces itself over into AS2 mode and actually plays the video (which in AS3 mode is both, too small for viewing if its under sized and supposed to be blocked by VEVO from being embedded outside of youtube).

Take what I say with a grain of salt though. I'm not a Developer working with Youtube so I don't know their internals. I've just been using and working around Youtube for long enough that I can catch these things based on past experiences.

Edited for coherency? (if you can call writing this post from 1am to 3am on a Saturday coherent).

Please provide the link and paragraph(s)/line number(s) where you say it talks about it. Reading the YouTube parameters documentation (https://developers.google.com/youtube/player_parameters) says nothing about what you've mentioned. There are also no redirects from YouTube when the video's load.

Watching the console, for YouTube URLs though I did notice YouTube throttling the video, only giving parts of the video when it's needed. In the throttling I did see the asv=3, I did not once see asv=2. When using a deprecated parameter color2 it still only used the asv=3 parameter, and did not actually apply the color2 parameter. It should be noted in the link I provided above it talks about color1 and color2 being deprecated and only working in AS2 players. The fact that it did not work when using it only further shows that using the Google API URL uses AS3 and not AS2, depending on the parameters passed to it.

Edit: --
The video on my mule in the first column is the one I tested it on, the video ID is, 1tjfjuPZTWg. I included below a copy of the console log when GETTING the YouTube video. Of course this is only a snippet of what was actually loaded, but this is the relevant part.
I have put into bold the parts of the information the video ID and the playback AS version. The URL I used is

http://youtube.googleapis.com/v/1tjfjuPZTWg?color2=0xff0000

Like I said, using the AS2 deprecated parameters yielded no difference in the AS version used, like what you mentioned before.

Quote:

[04:56:09.867] GET 1tjfjuPZTWg&height=200&width=200&el=embedded&asv=3]http://www.youtube.com/get_video_info?eurl=http://www.gaiaonline.com/profiles/unknighted-yoshi/15388423/&sts=1580&hl=en_US&video_id=1tjfjuPZTWg&height=200&width=200&el=embedded&asv=3 [HTTP/1.1 200 OK 152ms]

[04:56:10.102] GET &asv=3&video_id=1tjfjuPZTWg&fmt=5&t=vjVQa1PpcFNtD3lSPPhJY2V6BUr3kghMZH4qXPCMzik=&el=embedded]http://www.youtube.com/user_watch?eurl=http://www.gaiaonline.com/profiles/unknighted-yoshi/15388423/&ptk=youtube_multi&cpn=RHB5LqFHV57nffNg&plid=AATaTk64TxmxVd1c&asv=3&video_id=1tjfjuPZTWg&fmt=5&t=vjVQa1PpcFNtD3lSPPhJY2V6BUr3kghMZH4qXPCMzik=&el=embedded [HTTP/1.1 200 OK 123ms]

[04:56:10.201] GET &asv=3&et=0.028&yttk=1&docid=1tjfjuPZTWg&plid=AATaTk64TxmxVd1c&st=0.028&ctp=1&fmt=34&ns=yt]http://s2.youtube.com/s?cpn=RHB5LqFHV57nffNg&el=embedded&vid=BXvTCX8oLRX0noM669xiSi9cZMtjPo_SC&asv=3&et=0.028&yttk=1&docid=1tjfjuPZTWg&plid=AATaTk64TxmxVd1c&st=0.028&ctp=1&fmt=34&ns=yt [HTTP/1.1 204 No Content 84ms]

--
[04:56:30.390] GET &asv=3&et=20.193&yttk=1&docid=1tjfjuPZTWg&plid=AATaTk64TxmxVd1c&st=20.193&ctp=2&fmt=34&ns=yt]http://s2.youtube.com/s?cpn=RHB5LqFHV57nffNg&el=embedded&vid=BXvTCX8oLRX0noM669xiSi9cZMtjPo_SC&asv=3&et=20.193&yttk=1&docid=1tjfjuPZTWg&plid=AATaTk64TxmxVd1c&st=20.193&ctp=2&fmt=34&ns=yt [HTTP/1.1 204 No Content 31ms]

--
[04:56:40.452] GET &asv=3&et=30.166&yttk=1&docid=1tjfjuPZTWg&plid=AATaTk64TxmxVd1c&st=30.166&ctp=3&fmt=34&ns=yt]http://s2.youtube.com/s?cpn=RHB5LqFHV57nffNg&el=embedded&vid=BXvTCX8oLRX0noM669xiSi9cZMtjPo_SC&asv=3&et=30.166&yttk=1&docid=1tjfjuPZTWg&plid=AATaTk64TxmxVd1c&st=30.166&ctp=3&fmt=34&ns=yt [HTTP/1.1 204 No Content 32ms]

Edit 2: I should also note that the AS2 playback version itself, like the parameters for it, is deprecated. Which means that they are not using the AS2 player, but instead using AS3/HTML5. They would not deprecated it and then use it by default. It would make no sense.

Edit 3: I just ran the same tests on the middle one, which loads the four videos, when loading all four videos it still used the asv=3, and not asv=2 (asv=2 was not used anywhere). If you want the console logs for it, let me know. I decided to omit it this time, since there would be more for loading four videos.

[Knight Yoshi]

Fredy-san

I am thinking "Dahell what I just read here?!" burning_eyes
I am just done fixed my Youtube playlist code to be able to autoplay properly in all browsers. Nuff said: managed to bypass " GAIA killed Youtube ?/&autoplay=1 to just an ampersand "

though yeah I still somehow can not manage to get back AS2 Youtube playlist to work using single Playlist ID from a week ago. Maybe that feature was temporary?

You just read a lot of technical information. That's what. Lol.
I'm not sure for your issue what's happening. I don't know what you did before, what you did now, and if YouTube may or may not have changed anything.

[Melchiore]

Knight Yoshi

There is no compiled documentation on the matter, I'm sure when you get down to Youtube nitty gritties (I assure you, you haven't even broken the surface layer of Youtube), you'll see how it works yourself and understand. As for the lack of redirect, I can't say what the issue is there. Its not something your console will pick up in the parameters, its a part of the data being streamed. In the url variable, it will persist the data being requested, the server will just persist in the data being given (servers can do this, just look into php's ability to create and send an image on the fly). The player can ask for what it wants, however when certain criteria are met, and the data stream opened, it will decipher the data regardless because the player can obviously do so for both types.

There is no list of which parameters will force it down or up but, as I said listType and list seem to be two of those parameters. As I also said, it may very well be a bug. There are many bugs that can be found from playing around with Youtube's player.

Quote:

They would not deprecated it and then use it by default. It would make no sense.

I covered that when I said that youtube.googleapis.com is sort of like their archive. They use that to house the depreciated version of the player. The reason it can use version=3 is because their code for both bases are obviously tied together. This is also proven within both their customizable player, playlist and chromless versions of the player. In their documentation, they specifically use it to utilize their AS2 player, which if I may add, the addition of the version parameter itself was only added within one of the more recent updates to the documentation.

Something you seem to have overlooked however is my mention of the player not being as well documented as it ought to be.

As well, I'm unsure but, the player may actually be caching the video stream in some way, as when I posted it did in fact show the "Player too small" error then suddenly reloading and playing the video but it doesn't when I try it now. That is beyond the scope of this thread and you can feel free to make a thread elsewhere where we can compare notes.

Finishing up, I'm not here to decipher Youtube's internals or compare notes; I was just letting you know that it will use the AS2 version on default when using youtube.googleapis.com version of the link and that if you wanted to use the "list" with a playlist ID you could use version=3 to force it to play as intended. Unless you can somehow get it to use a playlist id without using version=3 then feel free to doubt me.

[Knight Yoshi]

Brink Kale

Knight Yoshi

There is no compiled documentation on the matter, I'm sure when you get down to Youtube nitty gritties (I assure you, you haven't even broken the surface layer of Youtube), you'll see how it works yourself and understand. As for the lack of redirect, I can't say what the issue is there. Its not something your console will pick up in the parameters, its a part of the data being streamed. In the url variable, it will persist the data being requested, the server will just persist in the data being given. The player can ask for what it wants, however when certain criteria are met, and the data stream opened, it will decipher the data regardless because the player can obviously do so for both types.

There is no list of which parameters will force it down or up, as I said listType and list are two of those parameters. As I also said, it may very well be a bug. There are many bugs that can be found from playing around with Youtube's player.

Quote:

They would not deprecated it and then use it by default. It would make no sense.

I covered that when I said that youtube.googleapis.com is sort of like their archive. They use that to house the depreciated version of the player. The reason it can use version=3 is because their code for both bases are obviously tied together. This is also proven within both their customizable player, playlist and chromless versions of the player. In their documentation, they specifically use it to utilize their AS2 player, which if I may add, the addition of the version parameter itself was only added within one of the more recent updates to the documentation.

Something you seem to have overlooked however is my mention of the player not being as well documented as it ought to be.

As well, I'm unsure but, the player may actually be caching the video stream in some way, as when I posted it did in fact show the "Player too small" error then suddenly reloading and playing the video but it doesn't when I try it now. That is beyond the scope of this thread and you can feel free to make a thread elsewhere where we can compare notes.

Finishing up, I'm not here to decipher Youtube's internals or compare notes; I was just letting you know that it will use the AS2 version on default when using youtube.googleapis.com version of the link and that if you wanted to use the "list" with a playlist ID you could use version=3 to force it to play as intended. Unless you can somehow get it to use a playlist id without using version=3 then feel free to doubt me.

You do not seem to understand HTTP packets. When a redirect is preformed there is a 300 status code, no parameters or anything can get around that. To put it in human language it would be something like this:
Browser: "I want this resource -requests URL-"
Server: "Well I'll give you this in place of the URL you want -gives resource w/ status code-"
When that happens a 300 status code is given, there's no way around that. Not even through Flash, because even a Flash file has to make an HTTP request to get new information. Which is what I provided above, those are part of the HTTP requests for the video, which only supplied AS3.

I have provided proof against your claim. I do not know where you have gotten your information, but unless you can back it up, with either console information and steps of how you achieved it so that it can be reproduced or documentation. You do not know what you're talking about. I'm not sure how much you understand about how HTTP web traffic works, but with what you're talking about it doesn't seem very much. No offense, but like I said unless you can provide documentation or logged information that with steps to repeat it, you're wrong. I've watched the console log, preformed different tests with different parameters on the Google YouTube API, and all have returned as AS3.

I should also note, that if this did happen there would be some form of documentation about it. It would not go undocumented, because then people would get results different than they were expecting and no explanation of why.
I'm done with this conversation.

[Melchiore]

Knight Yoshi

and I'll end your conversation with something as simple as, its on the server end. There is no redirect, there is no redirect packet needed. You seem to think that youtube videos locate a static resource that you can always find at that location. The server builds (and I am guessing now, caches) resources as they are requested. Its easy to redirect information on a server without the browser even knowing its not the original information requested. The same applies for anything really. I understand enough about how servers and browsers communicate with one another to know this, its very simple I assure you. The information is given as if it were the information requested. The server does the heavy lifting or you would be able to just pop through the player's opcodes and decode Youtube's entire structure. The information you provided wasn't relevant in any way to what we (or I guess what I was trying to explain). I cannot provide to you information about something so simply in your face. I guess I can just say, stop using your packet viewer for a minute and actually look at how the player operates. Decipher it from that standpoint. A server can be written to send you whatever information it wants to send you and you the user (unless you learned to natively read opcode or you are part machine) can only decipher the information based on what you think vs what you know.

Short answer, its got nothing to do with the packets the server sends you. Its in how the server interprets the information the player gives it but, again. Way beyond the scope here. Feel free to play with your youtube videos and tell me when you finally see / understand what I'm talking about, or don't. Either way, the way the player actually responds is proof of my claim and I don't need anything further to show that.

[Knight Yoshi]

Brink Kale

Knight Yoshi

and I'll end your conversation with something as simple as, its on the server end. There is no redirect, there is no redirect packet needed. You seem to think that youtube videos locate a static resource that you can always find at that location. The server builds (and I am guessing now, caches) resources as they are requested. Its easy to redirect information on a server without the browser even knowing its not the original information requested. The same applies for anything really. I understand enough about how servers and browsers communicate with one another to know this, its very simple I assure you. The information is given as if it were the information requested. The server does the heavy lifting or you would be able to just pop through the player's opcodes and decode Youtube's entire structure. The information you provided wasn't relevant in any way to what we (or I guess what I was trying to explain). I cannot provide to you information about something so simply in your face. I guess I can just say, stop using your packet viewer for a minute and actually look at how the player operates. Decipher it from that standpoint. A server can be written to send you whatever information it wants to send you and you the user (unless you learned to natively read opcode or you are part machine) can only decipher the information based on what you think vs what you know.

Short answer, its got nothing to do with the packets the server sends you. Its in how the server interprets the information the player gives it but, again. Way beyond the scope here. Feel free to play with your youtube videos and tell me when you finally see / understand what I'm talking about, or don't. Either way, the way the player actually responds is proof of my claim and I don't need anything further to show that.

The information I provided was relevant, it says what was loaded and how it was loaded. YouTube does not load the entire video in one URL. It throttles it making multiple requests to it, so each URL is new. If there was a change in the server, it would show when it sends the new URL. It would have to be changed in the parameters so that the format would change. It doesn't "magically" change, visually looking at something does not say anything about what is actually happening. You need to seriously take some web related classes to understand the internet better.

Do not quote me again, or respond to this post in any manner. I'm done.

[Fredy-san]

Knight Yoshi

Brink Kale

If you both willing to be so kind, would you two go discuss it somewhere else and delete those debate posts?? I am deleting two posts of mine in between. This thread is for discussing how to make YT work on GAIA. Not talking technical stuffs. k?

[Melchiore]

Knight Yoshi

If that is your claim then you are definitely able to access Youtube's internal code / server somehow and tell me this exactly?

This is how the Youtube player works.
Step 1:
Player Requests Video, extra parameters either tell the player different methods of asking for this information or different changes to make to its UI

Step 2:
Youtube's server sends the player a video stream

Step 3:
Player plays the video.

Regardless of whether the video is sent using data from their AS2 format or AS3 format, both sets of data can be played in the same player, how do you know what the actual server is processing before sending that stream back? Unless you know something about Youtube's internals that noone but an employee of the site could, if you do then by all means say that you are an employee with inside information or something.

I have been defending the method in which the player reads the parameters, somehow you got it that I was speaking about Youtube's video server. I'm talking about the player. The server will send the player the data it needs if its valid regardless of type. The player will then based on the actual player's (the swf file, not the server) internal checks, decide whether to use the information or not.

In this particular case, I was stating that the player for youtube.googleapis.com will be in AS2 mode (nothing to do with the server again) by default, you can look at how the actual player (the swf file) works to decipher this. There are no server requests that say, Oh hey, change my color to red or change my color to blue. The reason its an embedded parameter is because the actual video (swf) file that it locates will take that data and turn it into something useful. Nowhere inside youtube's actual server data being sent in or out does it reference player color, player loop etc. The server (not the swf file) handles the video and the playlist information being sent. The player handles how it uses the information given. In this particular example, I am saying that when the playlist addition is added into the url for the swf file it might be bugging up based on a faulted or unexpected line of coding and running the video with the playlist (because in all honesty, all the commands could work on the same swf file as they use the same base, they just wrote it not to for whatever their reasons they had).

The end result is that the player uses the list and listType commands in AS2 mode even though its programmed not to. The server would have sent the data regardless the player (the swf file) is the one that decides what to do once that data is retrieved.

This has absolutely nothing to do with the server code. I'm talking about the swf file, I've been talking about the swf file the entire time bro.

[iOrchard]

Great trick, thank you for it (:
I'm just having some troubles, I did the coding for it to be on the bottom but for some reason it still shows it in it's own media box. I'm using V2 (Or Current Version).

[Fredy-san]

iOrchard

Great trick, thank you for it (:
I'm just having some troubles, I did the coding for it to be on the bottom but for some reason it still shows it in it's own media box. I'm using V2 (Or Current Version).

Are you sure you have code it properly?? I dont see any positioning CSS for media panel in your page. Have you saved the changes?