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

Self related content blows up if you have both sides - depending on field order #16420

Closed
wezell opened this issue Apr 18, 2019 · 3 comments

Comments

Projects
5 participants
@wezell
Copy link
Contributor

commented Apr 18, 2019

1. Create a self related content type

  • Taxonomy
    • Name
    • Children (1-n relationship)

and you can manage content and the relationship. And the relationship data looks correct:

| parent_relation_name | child_relation_name |      relation_type_value       |
|                      | children            | Taxonomy.children              |

2. Add the 2nd side of the relationship

(parents) and place the field below the children so your type looks like:

  • Taxonomy
    • Name
    • Children (1-n relationship)
    • Parents (n-1 relationship)

and you can manage content and the relationship. And the relationship data looks correct:

| parent_relation_name | child_relation_name |      relation_type_value       |
| parents              | children            | Taxonomy.children              |

3. move the parents field above the children field.

Edit the content type and change the field order

  • Taxonomy
    • Name
    • Parents (n-1 relationship)
    • Children (1-n relationship)

and you can no longer edit the content (edit screen is blown up) and the relationship data is broken, e.g., it looks like:

| parent_relation_name | child_relation_name |      relation_type_value       |
| children             | children            | Taxonomy.children              |

@wezell wezell added the Type : Bug label Apr 18, 2019

@wezell wezell added this to the Rex Current milestone Apr 18, 2019

nollymar added a commit that referenced this issue Apr 22, 2019

@nollymar

This comment has been minimized.

Copy link
Contributor

commented Apr 22, 2019

Fixed here: #16427

@nollymar nollymar removed their assignment Apr 22, 2019

dsilvam added a commit that referenced this issue Apr 22, 2019

@erickgonzalez erickgonzalez self-assigned this Apr 23, 2019

@erickgonzalez

This comment has been minimized.

Copy link
Contributor

commented Apr 23, 2019

Tested with the provided steps and can edit content without issues.

@erickgonzalez erickgonzalez removed their assignment Apr 23, 2019

@bryanboza bryanboza added this to REX in QA Apr 24, 2019

@bryanboza

This comment has been minimized.

Copy link
Contributor

commented Apr 24, 2019

Fixed, tested on master // Postgres // FF

@bryanboza bryanboza moved this from REX to Done in QA Apr 24, 2019

@dsilvam dsilvam closed this Apr 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.