search

clarin-eric / component-registry-front-end

Test prototype for new CMDI Component Registry frontend
https://trac.clarin.eu/wiki/ComponentRegistryAndEditor/ReactFrontEnd
GNU General Public License v3.0
3 stars 1 forks source link

Feedback on trying to publish a group component with group dependencies #52

Open twagoo opened 8 years ago

twagoo commented 8 years ago

https://trac.clarin.eu/ticket/720

It seems possible to publish any group component, but if it has group-private dependencies, this fails with an ugly warning (see below). The feedback should be nicer and/or it should be communicated that you can only publish once all referenced components are published.

Very similar to #150 (consider merging)

Original report:

On 04/12/14 15:07, Alexander König wrote: When you try to publish a component from the group space and it depends on other components within the group space, you can't do it and get the following error:

Server Failed to handle registration. Unexpected error, try again later. (httpstatus code was: 500) Unable to load file. (error: Error #2032)

Doing it in the right order (from bottom to top) works without problems.

twagoo commented 6 years ago

Jan Odijk reported seeing the following error message upon trying to publish a profile from a team space:

["referenced component cannot be found in the appropriate registry components: clarin.eu:cr1:c_1505397653788 (private component in public registry).","referenced component cannot be found in the appropriate registry components: clarin.eu:cr1:c_1505397653785 (private component in public registry)."]

This is not very informative for the user. It would be better to at least show the component names and which (team) space they live in, so that the user can find them and choose to publish these first.