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.
In swftools exists a module with the same name. I checked the CVS and it appears that this module was developed later. I suggest that you change the name of this module to prevent conflicts with the one in swftools that was there earlier.
For instance, Blue drop video module depends on this module and on swftools, but since it conflicts with the flowplayer module in swftools, this module won't even appear in the modules page. I had to delete the swftools flowplayer to make it work.
Comments
Comment #1
RobLoachThe Flowplayer Drupal module is not changing its name. SWF Tool's Flowplayer module will have to change as that's a sub-module. Looking at the source, it seems like SWFObject module is a candidate for this problem as well.
Renaming SWF Tool's Flowplayer module to "swftools_flowplayer" and "swftools_flowplayer3" will solve the problem. Another thing we could do is move the SWF Tools module hooks over to the Flowplayer module and integrate the two? Thanks.
Comment #2
jbrown CreditAttribution: jbrown commentedtagging
Comment #3
jbrown CreditAttribution: jbrown commentedComment #4
Stuart Greenfield CreditAttribution: Stuart Greenfield commentedI've picked this up and am in the process of correcting it for the 6.3 release.
You're right that this is a wider issue since all the child modules of SWF Tools don't use an swftools_ prefix to avoid name space collisions. So I'm implementing the fix in all modules before going any further to get things back on the right track.
Comment #5
Stuart Greenfield CreditAttribution: Stuart Greenfield commentedCommitted on DRUPAL-6--3. I have gone through and manually corrected all modules and constants to the swftools namespace. I've not run full tests on all the modules yet as I'm still restoring my development rig and don't yet have all the players back, but the change was fairly simple so fingers crossed I got it right.
If anyone is able/willing to test the new set up and post their results here that would be a big help!
Comment #6
jbrown CreditAttribution: jbrown commentedReally glad your working on this Stuart!
Comment #7
fluxrider CreditAttribution: fluxrider commentedI'll test this w/e and get back to you here, probably sunday.
Comment #8
jbrown CreditAttribution: jbrown commentedComment #9
Stuart Greenfield CreditAttribution: Stuart Greenfield commentedAll SWF Tools modules are now part of the swftools_ namepsace.
Comment #10
cooldeeponline CreditAttribution: cooldeeponline commentedyeah like the description states .... deleting the flowplayer modules from the swf tool folder seems to be the only way by which the flowplayer api shows up in the module page...