pasber

As far as I know, the embedded version of YouTube player does not offer any fullscreen option. The allowfullscreen value is for the JW FLV Media Player only.

Mainly, you just need to replace the swf/mediaplayer.swf file with the new version.

But for usage with the whole plugin, it’s not that easy because a lot of flashvars have been dropped and some are new. The new skinning and plugin features are not that easy to integrate – except you’re the same flashvar code on each [flash] tag. But people will ask for default values and maybe some admin panel options for loading multiple plugins easily or switching between skins.

It would take some days of coding to fully implement the new player into pb-embedFlash – but I haven’t got that much time at the moment.

*double post* ??

Yeah and what should pb-embedFlash do now?

Quotation from the plugin description:

See the Installation tab for more information about the usage.

You have to show pb-embedFlash, how to embed what specific flash file:
[flash https://path.to/your/file.flv w=100 h=200 and=some more=options]

I don’t really get the problem. oO

How/where do you “import” the *.flv file?
What do you mean with “linking to it”?
What do you expect the plugin would/should do?

As of I’m not using iTunes I cannot say what’s going wrong there.

You are using the Shadowbox scripts from pb-embedFlash and additionally the Shadowbox-JS plugin.

Either deactivate the Shadowbox-JS plugin and let pb-embedFlash always load Shadowbox (even if no flash is loaded in a page, see pb-embedFlash settings in admin panel) or only use Shadowbox-JS and deactivate pb-embedFlash.

For me, there is no need to use both.

Just enter “playlist=1” as URL in the widget configuration, where “1” is the ID of your playlist.

What do you define as “custom field”?

That’s nice to hear =).

You can tell the plugin not to load any JavaScript libraries, so that it uses the existing one/s (e.g. loaded by another plugin).

pb-embedFlash Settings -> Shadowbox & Popup

So principally you are right: wp_enqueue_script() can prevent errors. But most of the plugins out their load JavaScript files from their plugin folder, so it’s not that safe as it’s claimed to be.

But my prime reason to use the “hard way” is that I cannot load scripts while being in the output. This is important because I don’t want to load all the scripts but give the option to use the different modes (object tag, shadowbox, popup, …) simultaneously.

Unfortunately, I did not get an email yet. ??

If you still want to send me the files, please do it asap as of I’m going to release the final plugin version 1.5 by next week.

I think I’ve found the issue. Other plugins can do changes on the tag (e.g. make hyperlinks out of the https://… text). To circumvent this, the flash filter needs an higher priority. Appropriate code is implemented in the final plugin version 1.5.

Forget my part about <p>-Tags. The problem is the validation / strict HTML: <p> can only hold inline elements – so no divs. But SWFObject needs an div-container(?) to know where to put the flash. Maybe another element fits, too.

You can add flash in template files with pb-embedFlash by using the PHP function pb_embedFlash_plugin(). More information.

Yes, it’s forced to be there because pb-embedFlash is designed to embed flash inside blog posts. WordPress puts blog posts inside <p>-Tags by default.

I could add a switch for the pb-embedFlash function you seem to call in your template file, so you could choose an output format.

I’ll release the final version 1.5 very soon. I’m still collection some errors, but in the past weeks, only a few problems came up. So I think the plugin is quiet bug free. Release should be by next week.

The next step for me (milestone 1.6) is the integration of JW FLV Media Player 4. Not that easy as I thought first.