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

Orphan entity after deleted and create a new one with same ID #14180

Closed
2 tasks done
jcervantes-sipecom opened this issue Feb 28, 2023 · 3 comments
Closed
2 tasks done

Comments

@jcervantes-sipecom
Copy link

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

Version

GLPI 10.0.6

Bug description

This is an issue that I guess is related with: #14179

When createad an entity, then moved as indicated in the prior ticket, then deleted, and then create a new one, this new entity is assigned the same ID prior entity last deleted. But this new entity is innaccesible, like it's orphan.

Relevant log output

N/A

Page URL

No response

Steps To reproduce

  1. Create a entity, in a sub-entity:

image

  1. Then move this sub-entity to root:

image

  1. Then log out and log int again, the entity dissappear or it's lost, as indicated in the prior ticket:

image

  1. To go the lost entity, just change the entity and select the hide one:

image

  1. Go to the entity, and delete:

image

  1. And error show up, but I think it's ok, but you can check it too:

image

image

  1. Log out and log in
  2. Create a new sub-entity, and as you can see the new entity has the same ID as the last one:

image

  1. Try to change to this new entity, but as you can see nothing happend:

image

The active entity is not the same as the selected one:
image

Even when all the entities is selected, the session variable glpiactiveentities just show an array of 2 elements, but there is a lot of entities:

image

Your GLPI setup information

GLPI Cloud

Anything else?

No response

@cedric-anne
Copy link
Member

@jcervantes-sipecom

#14347 should fix this issue. Could you confirm?

@jcervantes-sipecom
Copy link
Author

Hi @cedric-anne I confirm this fix the issue.

@cedric-anne
Copy link
Member

Thanks for the feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants