Closed (fixed)
Project:
Creative Commons
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
28 Oct 2005 at 07:23 UTC
Updated:
8 Jul 2007 at 18:22 UTC
Jump to comment: Most recent file
Comments
Comment #1
Marc Bijl commentedLook here (also commented by Dries):
- http://drupal.org/node/35404
Comment #2
omar commentedActually, the node referenced (node/35404) says nothing about the CreativeCommons module.
I am also very curious as to whether or not this module will ever be formally released (as opposed to staying in CVS).
Comment #3
Marc Bijl commentedOops... Sorry :-\
Didn't see it wat as about a module; must have been early this morning...
Comment #4
jmcnaught commentedIt would be great if somebody could port this to 4.7. I won't be able to move my website to 4.7 without it. I'm willing to do it eventually, but I have to learn PHP/MySQL/Drupal API first, so it might take a while.
jeremy
Comment #5
pbull commented4.7 is in the works. Sorry for the delay, but it will definitely be ready when Drupal 4.7 is released.
Comment #6
moshe weitzman commentedany update on this?
Comment #7
ashtonium commentedHow is the 4.7 version progressing? I'm more than willing to help with testing & coding if needed.
Comment #8
jamesJonas commentedHow's it going. We just hit 4.7 RC1. i would be happy to kick the tires when your ready.
Comment #9
marcoBauli commentedInterested in this too...maybe is time to step up and start learning some coding..
if in the meantime anybody is willing to help this mode see the light on 4.7.1 that would be nice ;)
Comment #10
ngstigator commentedany news on the update? if the maintainer is too busy and would like some help pls lemme know.
chris
Comment #11
zrupal commentedYes I love this module and although I am not yet a programmer I would love to help test and possibly document.
Comment #12
lukaspauka commentedCould anyone of you get the Creative Commons module adapted for 4.7 any time soon? I'm am wanting to use it on my music project collaboration site; www.thejamroom.nl in September.
thanks a bunch!!
Lukas
Comment #13
marc.baui realy need this module, too. i tryed myself a patch, but in the last hours i can only get the forms ready to display without errors... i'm a drupal newbie, my problem is there is nothing saved until now... i must spend more time on this or the maintainer will do so!?
Comment #14
gazwal commentedi need this module too !! for drupal 4.7.3
Comment #15
webchickIf someone's interested in porting this, here are some things that could be of great help:
Comment #16
pushkar commentedHello,
I have been trying to update the creativecommons module (http://drupal.org/node/17497) . I have updated the forms using the form update module.
Can someone help me in debugging this? Look at the file here : http://pushkar.net/creativecommons.module.txt
Thanks
Regards
Pushkar
Comment #17
hass commentedi have worked on this more then one week with less knowledge about modules, too. i think i learned something very hard. Asside - only to get out how this modle has worked in past was not so easy. Realy, all you have done until now is a very small step to a working version (lets say ~10-20%)! You need often '#tree' = true in forms to keep the variables tree structure - you haven't until now. what you are doing now - is to save every setting in a seperate variable. in past, there are only a few vars containing arrays of settings. My mayor problem was, to understand how go get out the arrayed vars - variable_get isn't working here very well. now i have worked out this and i must retry to get the rest ready.
but whatever, there is much much more to do... don't get frustrated :-)
Comment #18
MikeyGYSE commentedAny further progress on a 4.7 version of this module?
Comment #19
yraffah commentedAny updates please?
Comment #20
eagereyes commentedI'd like to use this too ... the current HEAD version is from 12/11/2006 - who checked that in? Does that work with 4.7? Are there any alternatives to this module?
Comment #21
eagereyes commentedOkay, I tried it and it doesn't work. My solution now is to have a block with the CC license HTML/RDF snippet in a sidebar. Since I use the same license for everything, that's good enough. Still, it would be great if this module could be revived.
Comment #22
jaxxed commentedI have had some success upgrading to 4.7.
At the same time I had to (anal = requirements) re-arrange some of the methods so I am submitting the new module. Most of the module is the same but the .module file has been updated to allow for 4.7 forms (form_ calls replaced, form element hierarchy re-arranged) and for 4.7 module calls.
the cc class was not touched except to temporarily disable the call to the api.creativecommons.com site on my version (because it is still testing version (and using a set variable instead.) Currently I am using variable_set('creativecommons_test_response',''); as is performed in the .install for testing, but you could disable this in the class to revert back to the original method. I obtained the value for this variable from executing the call for a 'standard' creative commons license (I added the variable set before submitting it here so it might not work, but it should be easy to figure it out from the install file.)
There is an issue. While the module works fine in my limited testing for drupal 4.7, I am not familiar enough with CC conceptually nor the cc api to know if it is actually working. Here are some questions:
1) are details for a piece of content submitted to the api.creativecommons.org site for registration? I notice that some details are passed in, and that a call is made for each association of a piece of content to the api.
2) What is the license revocation policy for cc? I think that legally if you register a piece of content with CC, you might have to retain that content despite whether or not you are using it (deleting a node.)
Anyway - play and tell me what is broken
James
p.s. I forgot to say that the autofill javascript function doesn't yet work
Comment #23
hass commentedBroken:
1. the module isn't working at all
2. cannot select site license
3. everytime i select site license CreativeCommons the page is reloaded and set to "no license"
4. after activated for "Story" and selected CreativeCommons, i pressed save - "no license" on a edit
5. same es 4, and no RDF is embedded to the page.
6. maybe a menu $cache problem only, but the menu point administer > settings > creativecommons is not visible after i activated the module.
All i found working well, is the config page is loading and it seems to save some settings to "variable" table.
Comment #24
aleksey.tk commentedAny progress with updating?
Comment #25
aleksey.tk commentedI am getting the same as hass...
1. Not working module
2. Admin menu exist, but after clicking on it, i get a "Page not found"
3. A lot of more bugs...
Comment #26
jmanico commentedAny progress on getting the creative commons module working on Drupal 4.7? What is holding this up? Should we consider building a new 4.7 from scratch?
Comment #27
ahmetus@groups.drupal.org commentedBecause it can be very useful and if it can use jquery, maybe add some ajax functionality
Comment #28
bpocanada commentedHere is the zip file of Creative Commons module for 4.7.x - The development of this has been funded by a Fortune 500 technology company
Comment #29
ryanlee commentedMany thanks bpocanada (and whomever they represent) for releasing this module.
Everything works pretty well, even having moved from Drupal 4.5 to 4.7 (stopping at 4.6 on the way), except that the URIs for the Creative Commons API appear to have changed. It's a minor patch, attached.
Upgrading made for some odd symptoms, with the 'site license' page not showing any available licenses. This module appears to do some sort of internal caching of fetched API results. So I manually removed a number of entries in the Drupal
variabletable relating to the XML cache, as well ascreativecommons_available_licenses. Re-saving the 'settings' page then brought the 'site license' page back.Again, thanks for your hard work.
Comment #30
Freso commentedThere's a 4.7.x-1.x-dev release available, so bugs against the 4.7 version should probably be filed on their own.
Closing this as I don't really see why it should be open when there's already a development version available for the requestion version of Drupal.
Comment #31
hass commentedas long as this patch is not committed this case should stay open for not getting lost, isn't it?!
Comment #32
Freso commentedhass: Eh? Case lost? There is a version of this module available for Drupal 4.7. If this issue is about something other than making the Creative Commons module available for 4.7, then it should have another title. (Besides, it appears as if both bpocanada's and ryanlee's patches have been committed to cvs...)
Comment #33
hass commentedi thought this patch have never been committed...