Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
twagoo opened this issue Jul 20, 2016 · 1 comment
Open
Milestone

Comments

@twagoo
Copy link
Member

twagoo commented Jul 20, 2016

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 twagoo added this to the 2.3.0 milestone Jul 20, 2016
@twagoo twagoo modified the milestones: 2.3.0, 2.4.0 Nov 28, 2017
@twagoo twagoo modified the milestones: 2.4.0, 2.3.0 Jan 22, 2018
@twagoo
Copy link
Member Author

twagoo commented Jan 22, 2018

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.

@twagoo twagoo modified the milestones: 2.3.0, 2.4.0 Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant