Problem/Motivation

When we create an "entityqueue", the machine name of this one must not already be taken by another entity (a node for example).

When the machine name already exists, several error messages appear: relating to the fields of the other entity (logical).
In addition, on the "entityqueues" management page (/ admin / structure / entityqueue), the link to "Edit items" does not appear on the newly created entity.

Proposed resolution

It might be better to automatically add a prefix for each machine name ("queue_" for example).

Comments

laborouge created an issue. See original summary.

amateescu’s picture

amateescu commented
Status: Active » Postponed (maintainer needs more info)

I'm not sure I understand how this can happen. Nodes don't have machine names, they have serial IDs, and the only way to try and create a clash between an entityqueue and a node is when you assign '10' (for example) as the queue machine name, and you also have a node with ID 10. I just tested this scenario and the queue was created correctly.

Are there any other contrib/custom modules involved in your situation?

laborouge’s picture

laborouge commented

You are right. The nodes have a serial ID. But entity types (as explained above) have a machine name. Example: "page", "article".

So if I create an entityqueue "page" and its machine name is "page", then there is a conflict.

amateescu’s picture

amateescu commented

I just tried this now: I have a content type with the ID page (the default one created by Drupal's Standard install profile) and created and entity queue with the same machine name, and there was no conflict...

laborouge’s picture

laborouge commented

I have created a content type called "news", and created an entityqueue called "news".

The entityqueue is here, but the link to "Edit items" does not appear. And when i try to modify the entitiqueue i have several errors about the node "news" additionnal fields.

I have fixed this by rename the machine name of the entityqueue ("news" => "queue_news").

I can reproduce this !

amateescu’s picture

amateescu commented

Tried that as well, and didn't see any errors. I think there's some other custom or contributed module which causes this problem for you.

laborouge’s picture

laborouge commented

OK ! I will investigate.
Thanks.

amateescu’s picture

amateescu commented
Status: Postponed (maintainer needs more info) » Closed (outdated)