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.

Sign up for GitHub

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

Jump to bottom

Unexpected scope for disambiguated entities #297

Closed
mcolacino opened this issue Apr 14, 2016 · 1 comment
Closed

Unexpected scope for disambiguated entities #297

mcolacino opened this issue Apr 14, 2016 · 1 comment
Assignees
@mcolacino
Milestone
3.5

Comments

@mcolacino
Copy link
Contributor

It happens that post / entity instances are saved with an unexpected thing classification scope even when their type is not compliant with that: this creates and inconsistent situation where entity seems to be properly linked to the content, but entity tiles are not selected.
@mcolacino mcolacino self-assigned this Apr 14, 2016
@mcolacino mcolacino added this to the 3.5 milestone Apr 14, 2016
@mcolacino
Copy link
Contributor Author

The issue happens if the current post is saved once the analysis is failed.

mcolacino added a commit that referenced this issue Apr 18, 2016
@mcolacino
Detect classification scope from current entity type. See #297
f9b0942
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mcolacino mcolacino

Labels
None yet
Projects
None yet
Milestone
3.5
Development

No branches or pull requests
1 participant
@mcolacino