When editing the forum content type to make it a content type for organic groups I get these errors below. How can they be resolved?
Notice: Undefined index: type in rdfui_form_node_type_form_submit() (line 344 of /var/www/vhosts/localhost/httpdocs/sites/all/modules/rdfx/rdfui/rdfui.module).
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'bundle' cannot be null: INSERT INTO {rdf_mapping} (type, bundle, mapping) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => node [:db_insert_placeholder_1] => [:db_insert_placeholder_2] => a:9:{s:7:"rdftype";a:2:{i:0;s:9:"sioc:Post";i:1;s:15:"sioct:BoardPost";}s:5:"title";a:2:{s:10:"predicates";a:1:{i:0;s:8:"dc:title";}s:4:"type";s:8:"property";}s:7:"created";a:3:{s:10:"predicates";a:2:{i:0;s:7:"dc:date";i:1;s:10:"dc:created";}s:8:"datatype";s:12:"xsd:dateTime";s:8:"callback";s:12:"date_iso8601";}s:7:"changed";a:3:{s:10:"predicates";a:1:{i:0;s:11:"dc:modified";}s:8:"datatype";s:12:"xsd:dateTime";s:8:"callback";s:12:"date_iso8601";}s:4:"body";a:1:{s:10:"predicates";a:1:{i:0;s:15:"content:encoded";}}s:3:"uid";a:2:{s:10:"predicates";a:1:{i:0;s:16:"sioc:has_creator";}s:4:"type";s:3:"rel";}s:4:"name";a:1:{s:10:"predicates";a:1:{i:0;s:9:"foaf:name";}}s:13:"comment_count";a:2:{s:10:"predicates";a:1:{i:0;s:16:"sioc:num_replies";}s:8:"datatype";s:11:"xsd:integer";}s:13:"last_activity";a:3:{s:10:"predicates";a:1:{i:0;s:23:"sioc:last_activity_date";}s:8:"datatype";s:12:"xsd:dateTime";s:8:"callback";s:12:"date_iso8601";}} ) in rdf_mapping_save() (line 239 of /var/www/vhosts/localhost/httpdocs/modules/rdf/rdf.module).
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 1271498_3_rdfui_form_values.patch | 1.98 KB | scor |
| #3 | 1271498-rdfui-form-error.patch | 624 bytes | linclark |
Comments
Comment #1
Anonymous (not verified) commentedI would have assumed that this was related to #905340: RDF UI doesn't work when mapping Taxonomy, but that was fixed in the 7.x-2.0-alpha3 version.
The problem is that the forum entity type that you are working on doesn't seem to have a bundle name, or that the bundle name is not being passed to the function.
If you are a developer, one work around would be to use rdf_mapping_save() to save the mapping or possibly to use hook_rdf_mapping() to declare a default mapping for the forum entity type.
Comment #2
BeaPower commentedHow can you do this if you're not a developer?
Comment #3
Anonymous (not verified) commentedTry changing the file sites/all/modules/rdfx/rdfui/rdfui.module where it says
$bundle = $form_state['input']['type'];to$bundle = $form_state['values']['type'];(or apply the attached patch).Let me know if this works for you.
Comment #4
scor commentedI am not sure why we're using form_state['input'] here. This bug will appear on any content type which is defined in a module (where the machine name is not defined in the form), e.g. (forum and book).
Still need to add a test.
Comment #5
dropbydrop commentedI have Drupal 7.8 and rdf extensions 7.x-2.0-alpha4.
At /admin/structure/types/manage/article/rdf, at Title I cannot delete the automatically put (not put by me) rdf predicate dc:title. I delete, I save mappings, the green message box says "RDF mappings have been saved", but the mapping is still there.
I also cannot delete rdf mappings at taxonomies like "skos:Concept"
At admin/structure/types/manage/article, RDF Settings, when I delete the mapping, I get error
I see something similar at http://drupal.org/node/905340 , but you have marked it as fixed.
Comment #6
dropbydrop commentedLin and scor are these patches above related to my problem? Are they included in 7.x-2.0-alpha4? I have 7.x-2.0-alpha4.
Comment #7
Anonymous (not verified) commentedThe issue you are describing is related to #1228872: RDF default mappings override empty values.
Comment #8
dropbydrop commentedThe issue you forwarded me which was for core 8, then forwards to http://drupal.org/node/1229974 which is an rdfx 7.x-2.x-dev issue.
Till this gets fixed please explain to me how I can clean up the database of a production site, since I used this module before I knew the consequences would be permanent.
I need also to clean up imported vocabularies.
Thanks for understanding.
Comment #9
acouch commentedI got the same error described in the issue. The patch in #4 fixed it.
Comment #10
natuk#4 worked for me as well.
Comment #11
steinmb commented