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.
Am I wrong, or does the module includes (and commits in Drupal.org CVS) files licensed under GPL License V3, where they should be licensed under the same license used by Drupal?
Comment | File | Size | Author |
---|---|---|---|
#15 | flowplayer-n722604-15.patch | 41.16 KB | DamienMcKenna |
Comments
Comment #1
jbrown CreditAttribution: jbrown commentedYes - it should use Libraries API.
See also #579950: Commercial version SWF.
Comment #2
RobLoachI'd love for this move to happen! We'll have to really document the installation of the plugins (like RTMP) as they're downloaded seperately from the main Flowplayer package.
Comment #3
lpalgarvio CreditAttribution: lpalgarvio commentedwell, start by moving the files out of the archive and reading from sites/all/libraries/flowplayer3.
that's a good start.
Comment #4
lpalgarvio CreditAttribution: lpalgarvio commentedand btw, the flowplayer bundles are outdated too...
Comment #5
osopolarI created a patch for this, which allows to set the library path to flowplayer manually or with the use of the libraries module. I added a README.txt and removed the flowplayer files.
I will leave the priority to critical because we need to remove the flowplayer plugin from the module!
SEE: http://drupal.org/licensing/faq Question 4, 5 and 10.
To outsource the flowplayer will also enable it to update. But be careful, the last version provided by this module was 3.1.5. There could be some compatibility issues with newer versions. This is *not* part of this issue. If there are compatibility issues, please open a new issue.
Comment #6
osopolarComment #7
jrreid CreditAttribution: jrreid commentedHere is a reroll of the patch against 7.x-1.x. I added a few more helper functions to get the path to the .swf and .js files individually, since the flowplayer package itself keeps the version number in the file names so we can't just specify them directly.
Comment #8
osopolar@jrreid: Not sure, but maybe just look once for the libraries and store them with variable_set(). And refresh this variable only when showing the settings page + list the files on the settings page.
Comment #9
arisaves CreditAttribution: arisaves commentedHey, jrreid -- I've managed to apply the patch -- but I'm having a tough time configuring the library path. I've added the files to my /sites/all/libraries directory and added the path to the module configuration, but no dice. I am desperately trying to add my own branding, but to no avail. I've tried via array in the video module, in the flowplayer module, and using the JS api.
Comment #10
andy.s.clark CreditAttribution: andy.s.clark commentedRecreated patch with --binary option. Without --binary option, running git apply complains about the binary files.
The patch expects the Flowplayer SWF to have the format 'flowplayer-*.swf'. It also expects flowplayer-3.2.10.min.js to be in the examples sub-folder. After extracting Flowplayer Commercial into sites/all/libraries/flowplayer...
Comment #11
arisaves CreditAttribution: arisaves commentedAndy, I am having a bit of difficulty applying the patch -- is there a different procedure for applying binary patches?
Comment #12
andy.s.clark CreditAttribution: andy.s.clark commentedApplying the patch appears to work fine by just doing "git apply flowplayer-libraries-722604-10.patch".
Comment #13
joelwallis CreditAttribution: joelwallis commentedSubscribing to this issue. What have been decided since then? Flowplayer is going to be in Libraries' folder?
Comment #14
DamienMcKennaComment #15
DamienMcKennaWIP, will also add support for v5 of the player. This patch also completely removes the existing Flowplayer files and adds a note to the README file about it.
Comment #16
kreynen CreditAttribution: kreynen commentedThe Drupal Association recently approved a Licensing Working Group with the authority to finally deal with issues like this. #722554: flowplayer module includes Flash player protected with GPL 3 licence is the duplicate issue in the LWG queue.
Once the process is established for dealing with violations, if the maintainers of the project do not resolve the issue the project will likely be treated more like an unresolved security issue. The project's releases will be unpublished and a notice will be posted to the project page.
More importantly, the maintainers who violated the https://www.drupal.org/git-repository-usage-policy risk losing their git privileges.
If this project is abandoned, it would be great to find a new maintainer willing to make this change to avoid having to unpublish a project used by > 7,400 sites.
Comment #18
RobLoachThanks for the note, @kreynen. Did a couple things:
If there's anything missing, let's file new issues against 2.x. Feel free to review this one and set to fixed if it seems sufficient to you.
Comment #19
kreynen CreditAttribution: kreynen commentedComment #20
Kebz CreditAttribution: Kebz commentedOn the configuration link here "admin/config/media/flowplayer"
It asks for this "Flowplayer Library Path"
Where can I find the files so that I can upload to my "libraries" (path = /sites/all/libraries) section?
Comment #21
Kebz CreditAttribution: Kebz commentedComment #22
kreynen CreditAttribution: kreynen commentedWhile related to this change, this is really a support request. You can find links to the downloads and the source at https://flowplayer.org/pricing/#downloads.
If that doesn't resolve your problem, please open a new support request.