Opened 9 years ago

Closed 8 years ago

#712 closed defect (duplicate)

UI allows private components in group components but backend doesn't

Reported by: Twan Goosen Owned by:
Priority: major Milestone: ComponentRegistry-2.1
Component: ComponentRegistry Version:
Keywords: Cc:

Description

Create a private component and another component (or profile) that uses this component. Move the top level component to a group but not the referenced component. Go to the group and edit the component you just moved there. Save it.

The operation will not be successful and, unless there are other errors, messages like the following appear (one line per referenced private component):

Failed to register: - referenced component cannot be found in the appropriate registry components: clarin.eu:cr1:c_1407745712016 (group registry) 2
 - referenced component cannot be found in the appropriate registry components: clarin.eu:cr1:c_1407745712061 (group registry) 2
 - referenced component cannot be found in the appropriate registry components: clarin.eu:cr1:c_1407745712051 (group registry) 2
 - referenced component cannot be found in the appropriate registry components: clarin.eu:cr1:c_1407745712031 (group registry) 2
 - referenced component cannot be found in the appropriate registry components: clarin.eu:cr1:c_1407745712058 (group registry) 2

Notice that the editor allows dragging in private components and that the browser does not force the user to push the entire chain of private components when moving to a group. This should be made consistent (probably by not allowing mixed private/group hierarchies in the UI).

Reported by Alexander König (MPI-PL), verified in 1.14.1 at http://catalog.clarin.eu/ds/ComponentRegistry by twagoo.

Change History (6)

comment:1 Changed 9 years ago by DefaultCC Plugin

Cc: olhsha@mpi.nl added

comment:2 Changed 9 years ago by Twan Goosen

Milestone: ComponentRegistry-1.15ComponentRegistry-1.14.5

comment:3 Changed 9 years ago by Twan Goosen

Milestone: ComponentRegistry-1.14.5ComponentRegistry-1.15

This is recoverable, so moving to 1.15 milestone

comment:4 Changed 9 years ago by Twan Goosen

Cc: olhsha@mpi.nl removed

comment:5 Changed 8 years ago by Twan Goosen

Milestone: ComponentRegistry-1.15ComponentRegistry-2.1

comment:6 Changed 8 years ago by Twan Goosen

Resolution: duplicate
Status: newclosed

Moved to GitHub as #35

Note: See TracTickets for help on using tickets.