pasber

Well, then I need an example page and the [flash] tag you used. For Popups I could modify the JavaScript or PHP codeif needed, but Shadowbox modifications are up to the developer of the script.

You can ease your program heavily by using unserialize to make an array out of the {s:5:”title”;…} string and use serialize to do vice versa. ??

Nothing else I’m doing to store an array in a single option field.

This could have several reasons:

• Does your script use unserialize and serialize to read/store the data from/into the pb_embedFlash_widgets field?
• Do you modify the structure in any way?

If the advices don’t help then I’ll need the full PHP code.

I did not try to embed any Shockwave file yet. But I think, as of they are both embedded identically (except that Shockwave files have a .dcr extension), it should work with pb-embedFlash.

I cannot support on that matter because I had these problems with version 4.0, too. JW supposes to use JavaScript/SWFObject to load the player, but I want it the old fashion way (“barrier free” / “accessibility”).

As of it’s a lot of work integrating v4.x into my plugin, I did not follow that target yet. As said before, maybe in Q1/09.

You could use the latest version with some limitations. Some flashvars have been dropped, others are new. You could not (easily) use the skinning feature and plugins for the player.

I don’t know when exactly I can move on to the next milestone (1.6) containing JW FLV Media Player v4.x and Shadowbox 2.x, but not earlier than February ’09.

The flash tag is correct and the generated html code seems to be ok, too.

Either it’s an issue by JW FLV Media Player or fade and slowfade are not supported though I’ve added it to the admin panel long time ago (copied from the Setup Wizard page, not(!) compatible with version 3.16 I’m using with pb-embedFlash!).

Thanks for the hint!

See other post. =)

The box itself is generated by the Shadowbox script and it’s content changes by the data given with the rel attribute.

As of one box is used for any content loaded in it (html, flash, pictures, etc.) and the box only changes width and height, adding/modifying/deleting information is quite impossible without changing the Shadowbox script from scratch.

So I’m sad to tell you p={} and o={} are not available for Shadowbox. :/

The shadowbox.css is loaded in the header section, so before any post is in the_loop.

As of the plugin is based on a filter parsing the_content of an blog post, it cannot know if there is any Shadowbox on a page – even if <object> is choosen as default display option, the [flash] tag value mode=3 would still be a possible way to embed flash via Shadowbox.

So I think the “dirty” way by forcing shadowbox.css (to ensure a “mode=3” would still work) is acceptable. The file is not that big, any user should be able to load it once (should stay in cache).

This is not possible because there is only one Shadowbox for all objects opened in it.

No problem =)

pb-embedflash only generates the (xhtml) code necessary to embed flash object – like pasting your own <object> tag into your website’s source code.

So: Yes, it should work with a proper .swf file.

Are you sure you’ve copied the correct flash file? The button is a bit different (text/shadows).

Please try https://www.richmondbizsense.com/images/banners/Main.swf as URL in the widget configuration, so you’re hotlinking to the “clickable” version of the flash.