Posted by davidsanger on July 15, 2011 at 11:47pm
11 followers
Jump to:
| Project: | Media Gallery |
| Version: | 7.x-1.0-beta7 |
| Component: | Code |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | Beta10-blockers |
Issue Summary
when I select edit to change values of Title, Caption etc. one of the fields is "License settings for this image" with a widget with no possible values to assign.
As a result I get the error message "License settings for this image field is required." and cannot make any changes.
The field "field_license" is Locked
I can't remember if I added the field or not but I don't want it to be a required field.
Comments
#1
Resolved:
If you do not activate the Media Gallery module then you get an "uneditable" state for Media
The Media Gallery modeul contains the definition for the function :
_media_gallery_get_field_license_values()
#2
I don't actually see this being a bug in Media itself? There's noting about a license setting field in the code. Should this issue move to Media Gallery?
#3
I am very new to Drupal, but it sounds like Media Gallery added the license field and then when I disabled Media Gallery the nodes became unupdatable.
moved from Media to Media Gallery
#4
#5
Hi, I agree that it should be possible to make some fields optional, for example the license field. Why does this have to be a required field in media gallery? See also #1165804: How to remove certain fields from being displayed
#6
Is this issue still valid in beta7?
#7
This is still an issue with beta7.
Here is a duplicate: #1345734: Selecte for "License settings for this audio" is empty and file can not be saved
This issue is older, the other has a better explanation. I think one of these could be closed as duplicate.
#8
This is a rather big issue. A temporary workaround is to delete the field from the file types after disabling media gallery.
But I think the best temporary solution is probably to make it "not required".
#9
Tagging.
#10
Retagging.
#11
Retagging.
#12
to #8: I couldn't delete the field even after disabling the module, because the field was set to be locked.
I had to manually unlock the field in the 'field_config' table, before I was able to remove it.