As far as i could tell, there are currently 2 other CC plugins for WordPress – wpLicense and cc-configurator – however both of them only let you set your license on a global level. That is, they let you pick one license for all your posts and pages throughout your entire site. I thought it might be useful if each WP user/author could choose between different CC licenses and be able to set them on a post-by-post basis. So, i modified the wpLicense plugin to do just that.

“The main purpose of this plugin is to give WP admins who run sites with multiple users/authors the option let these users/authors set specific CC licensing terms on a post by post basis.”

How it works:
It uses the CC api and the JsWidget to add a new section to the write/edit post page and then displays a small CC graphic/button and text on your published posts for all to see. The widget lets you choose the appropriate licensing structure and then your choice is automatically saved to a custom field the next time you click “Save and Continue Editing”, “Save”, or “Publish”. Then, it uses the CC api (details-license-uri-uri) to call some javascript that displays a small graphic/button and some text linking back to the definitions for the license you have chosen. Jquery was used to insert the new CC license section to the write/edit post pages as well as to open/close the new section. I also had to use Jquery to fix the tooltips for the JsWidget. Lastly, this plugin is optimized so that it will add only 1 DB query (the cc_js_result_uri) to each post that has set a CC license and stores it to a custom field for that given post – whereas the wpLicense plugin seemed to use 3 seperate db queries to set the global licencing for the site.

Screenshots:
Check out the plugin in action.

Download:
Click on the following link to download the plugin: per-post-license_v.02.zip

Requirements:
1. This plugin has been testing and works on WP 2.3.x using the default theme (but it is still a work in progess / comments and suggestions are welcome).
2. Your web server needs either curl (most have it installed and it’s the default setting used in this plugin) or URL file-access enabled (to be able to run file_get_contents() instead of curl).

Install:
1. Unzip and Copy the per-post-license folder to your plugins directiory and activate it.
2. Add the template function (see next paragraph) to where you’d like the CC image/button and text to appear on your post (this might be the single.php or footer.php template file).
3. Go to the Write post page or Edit an existing post.
4. Look for the new section marked “CC License” and click the small “plus” sign to open the section.
5. Select “A Creative Commons license” and choose the appropriate licensing structure.
6. Save the post and You’re Done!

WP Template Function:
Add the following function to the WP template file (like single.php, or footer.php) to get the CC license to appear on your post.

Template Options:
Right now, there are only 2 options that you can use with the cc_insert_html() template function.
1. The first is the $display variable. [$display=true ---> will show the CC license , $display=false will not]
2. The second is the $use_curl variable [default is set to --> $use_curl=true , if you explicitly set $use_curl=false the plugin will revert to the php function file_get_contents() which is not always enabled on all web servers]

CSS styles:
Here is a sample style you can use to center, add padding and margins, as well as a horizontal dashed separator (you can ofcourse use any style you like). You would add this code to your style.css file in your template directory.
#cc_code { text-align:center; font-size:11px; width:450px; margin-top:25px; padding-top:25px; border-top:1px dashed #ccc; }
You could also just use inline css and replace the < div id="cc_code" > and add these styles directly – something like < div style="text-align:center; font-size:11px;" >.

To Do:
- get rss/atom feeds showing CC license
- possibly add CC to header (if appropriate)
- option to set per author licensing (for all an author’s posts)
- option to set global default license for entire site
- option to turn off graphic/button and just show text
- option to choose/add an existing licensing structure (other than CC) by providing a URL
- create another template function to gather and list all posts with CC licensing (by title)

Well, i needed a choice/option that worked in a similar way but for Thickbox. Since both Lightbox and Thickbox are triggered by including special attributes on each anchor (a link) and pointing to a full-sized image – i figured it could not be that hard to find and edit the code that inserts the LightBox bit and swap it out for some Thickbox code.

LightBox format is: < a href="fullsized.jpg" rel="lightbox" >< img src="thumb.jpg" />< /a >
ThickBox format is: < a href="fullsized.jpg" class="thickbox" >< img src="thumb.jpg" />< /a >

All i ended up doing was adding the thickbox class=”thickbox” in addition to the lightbox rel=”lightbox”.

So the final result inserts the combined code into your WordPress posts:

< a href="fullsized.jpg" class="thickbox" rel="lightbox" >< img src="thumb.jpg" />< /a >

Now it works with either Lightbox or Thickbox scripts (i wouldn’t use both at the same time).
Note: you still need to provide the appropriate javascript (Thickbox or Lightbox) and link to it in your header file for this to work.

Tested with:
WordPress v2.3.1
Gallery2 v2.2.3 core 1.2.0.5
WPG2 v3.0.2

Anyway, here are the 3 WPG2 plugin files i edited to get this going:

wp-content/plugins/wpg2/g2image/g2image.php – [download the changed file here]
wp-content/plugins/wpg2/g2image/jscripts/functions.js – [download the changed file here]
wp-content/plugins/wpg2/wpg2embed.inc – [download the changed file here]

These are the exact edits i made (but watch out! because copy/pasting seems to change the single quote marks):

g2image.php – modify option to give choice (in dropdown menu of W2Image chooser) for specifically inserting Thickbox
[code lang="php"] $message['thumbnail_lightbox'] = T_('Thumbnail with LightBox link to Fullsized Image'); [/code]
[code lang="php"] $message['thumbnail_lightbox'] = T_('Thumbnail with ThickBox link to Fullsized Image'); [/code]

functions.js – modify javascript to do the actual inserting of code with Thickbox
[code lang="php"] htmlCode += ' Lightbox Options.
[code lang="php"] $img = str_replace('> [code lang="php"] $img = str_replace('/>

As a follow up to the earlier post entitled AJAX: A Closer Look, i decided to dig deeper into this new technique and the trends in web design / programming that appear to be emerging. The term Web 2.0 is commonly used to refer to a new generation of web applications and systems.

From www.whatsweb20.com, “it’s going to enable a whole bunch of cool new things that we can’t even imagine yet”.

According to the Wikipedia:

A website could be said to be built using Web 2.0 technologies if it featured a number of the following techniques:

Technical:

• CSS and semantically valid XHTML markup
• Unobtrusive AJAX Techniques
• Syndication of data in RSS/ATOM
• Aggregation of RSS/ATOM data
• Clean and meaningful URLs
• Support posting to a weblog
• RESTian (preferred) or XML Webservice APIs
• Some social networking aspects (share your data with friends, etc)

General:

• The site should not act as a “walled garden” – it should be easy to get data in and out of the system.
• Users should own their own data on the site
• Purely web based – most successful web 2.0 sites can be used almost entirely through the browser

Other related technologies include:

• SOAP – Simple Object Access Protocol
• Ruby on Rails

Here a some sites with excellent resources:

• script.aculo.us provides you with easy-to-use, compatible and, ultimately, totally cool JavaScript libraries to make your web sites and web applications fly, Web 2.0 style.
• Behaviour is the missing link for your ajax apps.
• Prototype is an object-oriented Javascript library that aims to ease development of dynamic web applications.
• mir.aculo.us is a site with a collection of thoughts, links and other stuff related to web application development, RoR, AJAX, Web 2.0, and more.
• Rico provides a very simple interface for registering Ajax request handlers as well as HTML elements or JavaScript objects as Ajax response objects.
• Techcrunch is a weblog dedicated to obsessively profiling and reviewing every newly launched web 2.0 business, product and service.
• Tool-man.org has some good resources, including some examples such as: Drag & Drop Sortable Lists with JavaScript and CSS
• JPSpan provides tools to “hook up” PHP and Javascript, for the purpose of fetching data from PHP into a web page which has already loaded, without reloading the entire page.
• SAJAX – Simple Ajax Toolkit by ModernMethod – XMLHTTPRequest Toolkit for PHP.
• CPAINT – Cross-Platform Asynchronous INterface Toolkit. It provides the code required to implement AJAX and JSRS on the back-end, while using JavaScript on the front-end.

Even more resources:
1. Ruby is the interpreted scripting language for quick and easy object-oriented programming. It has many features to process text files and to do system management tasks (as in Perl). It is simple, straight-forward, extensible, portable, open, and free.
2. Snippets is a public code repository. You can easily add code to your personal collection of code snippets, categorize your code snippets with keywords (known as ‘tags’), and share your snippets via this site.
3. RubyForge is a home for open source Ruby projects.
4. Programming Ruby is a book complete with tutorials and reference for the Ruby programming language.