We're updating the issue view to help you get more done. 

relationship type woes

Description

Hi,

I'm having some troubles with relationship types which I've never seen before in my setup for the provenance researchers from Vienna.

I put a dump to test this out on antwerp in /home/stefan/provenienz_18_jan.sql. You can log in with stefan/stefan.

a) If you edit an existing relationship type without specifying a hierarchy location, the parent_id is set to 0 after the save which essentially means that the rel type will not appear in the hierarchy browser anymore. Also, the table_num is set to 0 which is even worse, I guess.

b) The relationship bundles do weird stuff with the type restrictions and I guess this might be related to a). Have a look at the rel type

/index.php/administrate/setup/relationship_type_editor/RelationshipTypeEditor/Edit/type_id/138

It says Provenienzmerkmale <-> Provenienzmerkmale (objects_x_objects), right? Now try

/index.php/editor/objects/ObjectEditor/Edit/Screen6/object_id/88

This is a "Trägerobjekt" (different object type). Try relating something in the bottom "related objects" bundle. This one is restricted to only display "Provenienzmerkmale" (the bundles have meaningful names in German). And there it is: "ist physisch verbunden mit". Weird.

Environment

latest cleanup branch

Activity

Show:
Stefan Keidel
January 23, 2012, 6:49 AM

Any news on this? Let me know if I can help ...

User known
January 23, 2012, 10:35 AM

Hi,

There's a fix for (a) in SVN. It was a bug related to the new hierarchy browser functionality
(b) is a result of the hierarchy field values being corrupted by (a)

Stefan Keidel
January 23, 2012, 12:08 PM

a) seems fixed indeed. Thanks for that!

The example I used to describe b) above still doesn't work as intended though. I tried saving the reltype again with the updated code and I rebuilt all available indices. Is there anything I need to fix in the db to get this working again?

User known
January 23, 2012, 11:47 PM

Ah, ok. I see the problem now. I just committed a fix for this. It seems to work but it might cause other problems so please test it out and let me know... Ick, I hate type restriction stuff. Hurts me head.

Stefan Keidel
January 24, 2012, 7:55 PM

That seems to have done the trick! I'll have them work with that version now and will report if something is off. Thanks!

Assignee

User known

Reporter

Stefan Keidel

Labels

None

Components

Fix versions

Affects versions

Priority

Blocker
Configure