Question about weblog software and CC licenses
In 2003, SixApart released Movable Type version 2.6, which included options for Creative Commons licenses. At the time, I was (and still am) very impressed that Creative Commons licenses were built right into the code of a popular weblog software application. Yochai Benkler's framework of layers is applicable here; Movable Type has Creative Commons embedded into the logical (code) layer. Creative Commons' own use of metadata for RSS and searchable CC-licensed content is an instance of this as well.
I believe, if I'm not mistaken, that WordPress has a plugin that lets you choose a CC license within WordPress also, but will a WordPress user please confirm this? I have a wordpress.com account, and I poked around in the dashboard but couldn't find CC license selection anywhere in the options. Drupal has a Creative Commons module.
Finally, are there other weblog software apps which have CC license selection built into the core software code, or which have CC license selection plugins? Doesn't LiveJournal have a CC option now that they're affiliated with SixApart? This information will help me with a paper I'm revising.
- Clancy's blog
- Login or register to post comments
Comments
WP Plugin
Here's the WordPress plugin. No, not native -- gotta install it yourself.
http://wiki.creativecommons.org/WpLicense
--
Mike
http://www.vitia.org/
Drupal's CC module
I cannot get the Drupal CC module to work properly. The first problem was that the URI it references to obtain licenses is no longer active. You have to edit the module code to point to the new address (http://api.creativecommons.org/rest/1.5/ instead of http://api.creativecommons.org/rest/). The next problem is that the buttons for the site set up use variables that may have been in an earlier XML file on the Cc.api site. The module must not be finding the correct values, so the form will not submit properly. It returns with an error but only after injecting the text values you input (i.e. the titles and footer values).
The developer says he is working on a 5.x version and does not intend to upgrade the 4.7.x one.
I think the real problems derive from a change in the CC API since the module was released.
--
rdr