Hi,

I've been struggling with the flash media player. When I finally got it to do its basic work (after finding out about changing the folder name and then eliminating the extra files thing in the playlist path...), i.e. to show up as a default player for a single uploaded .mp3 file in a node, the next step was to get a playlist going. Then I got an error message that stated something like there's no player designated for playlist (I had uploaded another .mp3 so there were two of them in the same node) or something like that (I don't remember exactly anymore and since then I've updated the module, see below).

I found some discussion from which I gathered that I should change to the dev version, which I did. Then the playlist indeed appeared - after I first changed the player's display width from nothing to, well, anything (the default won't show it). So far I had been checking only with IE and everything worked (although it bothered me that there still was 1 pixel high video display above the player timeline, when I would have wanted none (the default) for just audio). But then I tried Firefox and Opera - and they show nothing! The player still shows in the source code, anyway. What to do!?! Sorry if my tone is a bit dramatic, but I've been struggling way too long with this and it is fatiguing...

Comments

spede’s picture

Some further info: as I told the player works, when I try with IE6. And at first FF2 and Opera 9 didn't show anything but blank space (not the default non-flash message, but clearly space reserved for the player) - in the source code everything was still there. For some reason FF2 now gets from somewhere a table which shows the playlist's mp3's as links, there are sections Attachments and Size in the table and the list underneath those. I got to try IE7 on another computer and there the player didn't show up either!

So how on earth the browser that everybody who has ever done anything web-related so dearly cherishes - the friggin' IE6 - ís the only one who deals with the player? Cosmic joke, I think... I've tried different settings in the SWFtools and Wijering sections in the administration area, but so far - no luck.

Another problem (totally different scale) is that to show the playlist I have to show a display too (woudn't want to, mp3's could do fine without) and it shows this messed-up version of a default Drupal-related image. Every track in my playlist xml file has a path for this and I made a different image and changed it, named it swftools-default.jpg, but still the player shows that same messed-up (kind of tv screen gone wild, the file has been corrupted somehow?) image, although when I copy the path to an empty browser, it shows my new image. Some weird cache problem? It would be quite nice to hear about this, but indeed it would be sssuperrr nice to get some help for my major problem with the browser...

BINAIRe’s picture

Try clearing private data in FF: Tools > Clear Private Data > cache in FF.

Also try to run the cron in Status Report of Drupal admin.

Then refresh and it might show up, sometimes the cache in FF doesn't refresh even though you refreshed browser.

Otherwise it may be a simple code typo error. Hope it helps, otherwise good luck

Stuart Greenfield’s picture

There were some inconsistencies in how data was given to FF versus IE, so maybe this was causing an issue?

A fix for this issue is built in to a new 5.x-1.x-dev release and is ready for testing. The new package will be available when the packaging scripts next run.

Maybe try the new package and see if this helps.

Also, working with playlists can give some caching headaches - you may need to reset your Drupal cache, clear the playlists directory, and clear your browser cache. Things can appear not to be working when in fact they are ok!

Stuart Greenfield’s picture

Status: Active » Needs review

I have tested the latest 5.x-1.x-dev package on FF/IE/Safari, and Wijering player now seems to be working in all cases.

Please try the latest dev package and check it's ok for you to.

Stuart Greenfield’s picture

Status: Needs review » Fixed

Setting to fixed as new releases of SWF Tools 5.x-2.0 and SWF Tools 6.x-1.1 are now available which address this issue.

There were some glitches with not all parameters getting passed in both OBJECT and EMBED format. This may have explained the issue. All current tests have been ok here, so setting to fixed.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.