Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
My goal in taking this over was to update it to work with 5. I did the 4.7 update, but haven't had time to really dig in to get it to work with 5. I also maintain TinyMCE. Getting that module to work with JQuery has prove far more time consuming than I expected. Once that's done, I'll get back to this. I'm more than happen to look at any patches anyone submits (hint, hint).
I see that a lot of the update work would merely involve shuffling around the settings forms to comply with the FormAPI changes. Not that that isn't quite a tedious job - especially making _submit() functions to replace all the code that accesses $_POST directly. And the code that mixes page display with form building, which are completely separate in 5.x.
But I'm fiddling with this a bit and might have a patch ready at some point in the future.
Arancaytar: Have you made any progress? I'm considering looking into poking the code towards D6 compatibility - having a D5 instead of a D4.7 code base would most probably be quite helpful. :)
I got stuck on some problems, but I identified the problem and solution - CC uses a kind of custom spaghetti logic to implement a multistep form that wasn't yet supported by 4.7. This needs to be ported to FAPI 2.0, which does support them.
Specifically, I'm currently at the "submitted data and new form array mismatch" problem that http://drupal.org/node/101707 describes how to solve in FAPI 2.0.
-----
I would like this module to get around the multistep form more elegantly (I dislike having to submit multiple times; afraid that I might post prematurely or lose input). Unfortunately, ActiveSelect wouldn't work here because the base license type not only determines the options (which ActiveSelect can update), but also what select menus are actually available.
Perhaps a future version could "save" license profiles, allowing a user to create a license once and attach it to future nodes from a single menu without going through the multistep form again. Licenses could even be nodes. But that kind of thing goes well beyond a port; also, it would be a ridiculous idea for me to change the basic architecture of a module I'm not going to maintain. So I'll call it a day if I can get the multistep form working in 5.0.
Arancaytar:
Any progress? Have you tried playing around with the Coder module? It's been greatly helpful in aiding me port a few things from D5 to D6, but it has checks for D4.7 to D5 as well.
I spent some more time on it, but haven't got anything to show really.
My exams and BSc thesis are going to take up most of my time for the rest of the year at least, so I'd like to unassign myself from this issue (if I ever actually assigned myself to it in the first place, that is).
Is there anyone working on this update? Perhaps we all could chipin a little bit of code, and update it step by step. I'll try to take a look into it.
Arancaytar it would be great if you could provide us with some hints, if not a patch.
You can try out Creative Commons and Copyrights computed field and node type which I just posted for adding your own licences. Then apply one of the many node access modules to secure the granunalrity of each license you create.
NOTE it is for 6.x, but you can use the documentation and code to roll your own in 5.x.
Comments
Comment #1
Freso commentedJust adding myself here for the subscription, and to echo the fact that I'd like to see this available to Drupal 5 (and 6, when that time comes).
Comment #2
kreynen commentedMy goal in taking this over was to update it to work with 5. I did the 4.7 update, but haven't had time to really dig in to get it to work with 5. I also maintain TinyMCE. Getting that module to work with JQuery has prove far more time consuming than I expected. Once that's done, I'll get back to this. I'm more than happen to look at any patches anyone submits (hint, hint).
Comment #3
cburschkaI see that a lot of the update work would merely involve shuffling around the settings forms to comply with the FormAPI changes. Not that that isn't quite a tedious job - especially making _submit() functions to replace all the code that accesses $_POST directly. And the code that mixes page display with form building, which are completely separate in 5.x.
But I'm fiddling with this a bit and might have a patch ready at some point in the future.
Comment #4
Freso commentedArancaytar: Have you made any progress? I'm considering looking into poking the code towards D6 compatibility - having a D5 instead of a D4.7 code base would most probably be quite helpful. :)
Comment #5
cburschkaI got stuck on some problems, but I identified the problem and solution - CC uses a kind of custom spaghetti logic to implement a multistep form that wasn't yet supported by 4.7. This needs to be ported to FAPI 2.0, which does support them.
Specifically, I'm currently at the "submitted data and new form array mismatch" problem that http://drupal.org/node/101707 describes how to solve in FAPI 2.0.
-----
I would like this module to get around the multistep form more elegantly (I dislike having to submit multiple times; afraid that I might post prematurely or lose input). Unfortunately, ActiveSelect wouldn't work here because the base license type not only determines the options (which ActiveSelect can update), but also what select menus are actually available.
Perhaps a future version could "save" license profiles, allowing a user to create a license once and attach it to future nodes from a single menu without going through the multistep form again. Licenses could even be nodes. But that kind of thing goes well beyond a port; also, it would be a ridiculous idea for me to change the basic architecture of a module I'm not going to maintain. So I'll call it a day if I can get the multistep form working in 5.0.
Comment #6
Freso commentedArancaytar:
Any progress? Have you tried playing around with the Coder module? It's been greatly helpful in aiding me port a few things from D5 to D6, but it has checks for D4.7 to D5 as well.
Comment #7
cburschkaI spent some more time on it, but haven't got anything to show really.
My exams and BSc thesis are going to take up most of my time for the rest of the year at least, so I'd like to unassign myself from this issue (if I ever actually assigned myself to it in the first place, that is).
Comment #8
Freso commentedArancaytar:
Perhaps you could upload a patch of and some words on the work you've done so far?
Comment #9
chrisroditis commentedIs there anyone working on this update? Perhaps we all could chipin a little bit of code, and update it step by step. I'll try to take a look into it.
Arancaytar it would be great if you could provide us with some hints, if not a patch.
Comment #10
pkej commentedFor anyone waiting for the updated module:
You can try out Creative Commons and Copyrights computed field and node type which I just posted for adding your own licences. Then apply one of the many node access modules to secure the granunalrity of each license you create.
NOTE it is for 6.x, but you can use the documentation and code to roll your own in 5.x.
Comment #11
balleyne commentedUnless anyone objects, plans are to skip D5 for the sake of focusing on D6 (and eventually D7) development. CC Lite is available for D5.