Posted by ppoetsma on September 11, 2009 at 4:13am
Jump to:
| Project: | Creative Commons |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
When I create a new node, the message "License is not available" appears. I have a site-wide license enabled and no content specific ones. Any clue what the cause is?
Comments
#1
I solved it myself by selecting the first license as well in the settings tab. I never use that first license, but at least the annoying message is gone.
#2
closed
#3
Hey guys,
I tried the solution that was provided and it didn't seem to work. Every time a node is actually created / edited an error message appears at the top. We are only using a site-wide license (although previously we had this setup for content-types).
Thanks heaps
Shane
#4
Alright I tested this in the latest beta version and it seems resolved.
#5
I'm using 6.x-1.0-beta3 and it's still happening for me, using a site-wide license. When saving a node, the cc class is being constructed and then saved with no data, causing get_license_unavailable_message() to be called and the message "The license "All Rights Reserved (None)" is not enabled." output.
#6
Same problem with beta3 in a site where "All Rights Reserved" is nos a valid license.
The wired thing is that I see those messages on content that don't has creativecommons associated.
I mean, for content with CC attached, default license (in my case CC-sa) is set and everything works fine. For content that I don't like to attach any license (disabled in /admin/content/types/content as well as in /admin/settings/creativecommons/types) I got the annoying Copyright license.
I think it's a bug (CC don't need to do anything on content that don't require CC attached) as well as a problem of design: Copyright (All Rights Reserved) is not the same as NONE... so they must be distinguished as different choices.
Any clue about how to fix this?
Thanks a lot for the great module,
m.
#7
I believe the fix I committed for issue #722056 solved the error for sites using site wide licenses as well.
#8
I implemented the fix described in http://drupal.org/node/722056#comment-3283330 and it seems to have resolved this issue, thanks.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.