Show on translated nodes in multilingual sites ++

Hi jsmm,

I'm working on this module for the Google Summer of Code right now. Pushing for a 1.0 beta soon, and then moving onto new features for the rest of the summer.

> 1. When applied to a node, it doesn't show on its translated version.

I haven't played around with any multilingual sites yet, but I want to do this in the second half of the summer. I would think that the English version should be showing up no matter what though, but it's not showing anything for translated versions? Any documentation you can point me toward to fixing that for 1.0? Otherwise, I'll take a look when I look at language localization.

> 2. Can admin choose on which node types the cc option will appear?

That's on my list to implement asap. Hopefully this weekend.

> 3. Can it be applied to uploaded files?

Right now, only nodes. Any suggestions for how to add this for uploaded files? Maybe a submodule with dependencies on CC and Upload? I'll put this on my list for ideas to look at for the second half of the summer.

> 4. I cannot find the creativecommons.mysql file. Moreover, is there any documentation on how to proceed with it?

There shouldn't be a .mysql file anymore, as I switched it to creativecommons.install instead. But, warning, the README and Install.txt file have not yet been updated. I'll do that in the next few days (sorry for any confusion, was planning on updating them for alpha/beta releases).

> 5. When pressing the default tab I get Fatal error: Call to a member function is_available() on a non-object in (...) /sites/all/modules/creativecommons/creativecommons.module on line 221

Thanks, I'll look into this!

Expect a more polished alpha coming real soon...

> 1. When applied to a node, it doesn't show on its translated version.

I haven't played around with any multilingual sites yet, but I want to do this in the second half of the summer. I would think that the English version should be showing up no matter what though, but it's not showing anything for translated versions? Any documentation you can point me toward to fixing that for 1.0? Otherwise, I'll take a look when I look at language localization.

Keep in mind that the translated node is its own node entirely - it just has a flag set that another node is a translation of it, or it's a translation of something. Everything else that is stored on a node, can differ. Taxonomy, content, etc. - and also CC data. If you want to keep translated items in sync on certain points, take a look at the "i18nsync" module in the Internationalisation suite.

@Freso: Thanks for the information! I'll look into that.

@jsmm: The next development snapshot (to be created July 12 from latest changes) has #2 implemented (content type selection) and the bug you mentioned (#5) should be fixed. I think you noticed #4 was taken care of (though, I'll review and update documentation in more detail closer to release).

That leaves #1 (license information for translated nodes), which I'll look into, and #3 (licenses for uploaded files), which won't be implemented for this release but is on the wish list for later.

Thanks for the feedback.

Just a heads up that I've put out a beta release:
http://drupal.org/node/529620

Testing would be greatly appreciated.