Active
Project:
RDF Extensions
Version:
7.x-2.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Sep 2010 at 11:30 UTC
Updated:
9 Oct 2012 at 19:36 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
groovehunter commenteddestination page with error is http://drupal7a/admin/structure/taxonomy/verfahren/rdf
Comment #2
Anonymous (not verified) commentedIs drupal7a a domain name?
Comment #3
groovehunter commentedyep, it's a local vhost, sorry i thought it would be obvious
Comment #4
Anonymous (not verified) commentedNo problem, I assumed it was but sometimes people post a local URL without realizing that because it is local, other people can't access it. You can just post the path from admin/ on and folks will know what you're talking about.
Comment #5
Anonymous (not verified) commentedI believe the problem here is that we are assuming that the entity type is node... RDF UI originated in Drupal 6 as RDF CCK, so I think some of the assumptions carried through.
When I tested it on content types, it worked. When I tested it on a Taxonomy, I got the following two errors:
I haven't looked through to see where in the code this would be.
Comment #6
Anonymous (not verified) commentedChanging title to reflect.
Comment #7
Anonymous (not verified) commentedAlso, to do what you want, groovehunter, you shouldn't need to change the mappings on the taxonomy.
sioc:topic is a property that links the term on the node to the node itself. You would want this mapping to be on the taxonomy field on the node, not on the vocabulary. skos:Concept is a class, which means that it is a type of thing. sioc:topic is a predicate, which means that it is a relationship between two things.
So you should be able to achieve what you want with the module as it is right now. We (the maintainers) should still look into this issue, though.
Comment #8
steinmb commentedHi
We also stumbled upon this bug while testing out RDF on a vocal. Lin made a point in #7 so it might not be an such a good idea but we are as many other is trying to wrap our heads around how to utilize this D7 RDF awesomeness.
Comment #9
AlanAtLarge commentedFollowing
Comment #10
Anonymous (not verified) commentedthanks for topping this issue, I've been working on a project for a while, but that is winding down. I think I'll have time to look at this stuff in the next few days
Comment #11
scor commentedMarked #1156842: RDF UI assumes nodes? as duplicate.
Comment #12
ronald_istos commentedHere is a patch to fix the taxonomy vocabulary mapping issue - not sure is the right approach but should at least highlight the pain points and someone more knowledgeable on the module could fix it properly faster.
Comment #13
scor commentedany entity type can have multiple bundles, so this comment is unclear. It feels strange to ignore bundle if the type is not a node, but since RDF UI only support multiple bundles for node at the moment, it might make sense to have such a hack.
Having a generic UI would be best to avoid such hack: #1159104: Create a more generic RDF UI mapping tool, but I would not be opposed to solving the taxonomy issue until we have such generic RDF UI.
Comment #14
Anonymous (not verified) commentedThis patch also fixes notices with field collection entity types.
Comment #15
Anonymous (not verified) commentedWe also need to add
$field_name != 'title'to the conditional at line 544.Comment #16
Anonymous (not verified) commentedOk, I committed the patch from Ronald with the minor change that I mentioned.
Comment #17
steinmb commentedThanx Lin :)
Comment #19
smithdalec commentedMy apologies for opening this back up :)
This error still occurs when using an entity type (other than taxonomy term) where the bundle key is something other than "type". For instance, the Taxonomy Term entity type uses "machine_name" as its bundle key (this can be anything as specified in hook_entity_info()).
I've created a patch that fixes this issue: