Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After upgrading to FLV Media Player 6.x-1.0-beta4 I am getting a "blank" player on nodes where I never entered any FLV parameters. These nodes contain other content, and were never intended to have videos. This is really making my site look bad!
I corrected it for SOME nodes by opening those and saving them again, but that does not work for all of the nodes. And even if it did, it would be a task to check all of my nodes, which number over 600 on a site with only a couple of dozen videos.
Suggestions, please?
Thanks!
Comments
Comment #1
wmfinck CreditAttribution: wmfinck commentedWell, I got this narrowed down, but not exactly solved. One of the CCK add-ons is causing this to happen, but I am not sure yet which one. However when I create a dummy FLV profile, and uncheck all the options for player display (node and teaser), making that the default, the problem goes away.
Comment #2
admixarts CreditAttribution: admixarts commentedThis is happening to me too. Basically I have 2 content types...1 is "blog_post" and the other is "video". sometimes I'll put a short promo video in a blog post and the full featured video goes in the "Video" content type. The problem is that when I tell FLV player its ok to use these two content types it sticks a default player in my node teaser and node body even if I did not place in any video code on that particular node.
Shouldn't it check to see if the field actually contains a value before deciding to serve up a default player?
The only other option I can think of right now is to create a new content type called "video_blog_post" and when I want to post a promo video in a post I then use that content type instead of just "blog_post". That's not a very elegant solution but it'll work for now until I find a way around this issue.
Drupal: 6.16
FLV Media Player: 6.x-1.0-beta4
Comment #3
wmfinck CreditAttribution: wmfinck commentedThanks! I am glad that I'm not the only one! This problem still persists, and affects nearly all of my (over a dozen) Drupal sites.
Comment #4
arthurf CreditAttribution: arthurf commentedThere is a problem with the way that I'm caching things. I hope to get a chance to get to this this week.
Comment #5
arthurf CreditAttribution: arthurf commentedI committed a fix to the dev branch, please review.
Comment #6
jcmarco CreditAttribution: jcmarco commentedLast patch broke the on node player display.
I am using XSPF to create the video list settings for the player and checking changes on line 1090 from flvmediaplayer.module
I found that I don't have any $data['flashvars']['file'] in my $data array, but only a ['config'] with the xspf settings url.
Comment #7
wmfinck CreditAttribution: wmfinck commentedThis error no longer exists in the updated versions of the moduloe. Thank you!
Comment #8
selfuntitled CreditAttribution: selfuntitled commentedDoes this mean that the patch has been included in the dev version of the module or has is it included in beta4? If it's included in beta4 I report that testing the patch has failed, I'm having the same problem. If it's in dev, I'll upgrade and test.