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

Changing dropdown of a required, single-select bi-directional relationship field leads to Pods error #5364

Open
remcokalf opened this issue Apr 30, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@remcokalf
Copy link

commented Apr 30, 2019

I have a bi-directional field set up between a Custom Post Type and a Custom Taxonomy.
The field settings on both Pods are set to:

  • required,
  • single select
  • drop down

The first time setting the field with the dropdown, all is fine.

But when I want to change the dropdown setting, on Save I get a Pods error stating:

"The [fieldname1] field is required and cannot be removed by the [fieldname2] field"

The error happens on both sides: when changing the field dropdown in the CPT post page and when changing the dropdown in the taxonomy term page.

I have this same error with multiple bi-directional fields in different CPTs/Custom taxomies.

See attached screenshots for error and call stack. And field settings in both pods.

EDIT:
The error is gone when I remove the 'required' setting from both Pods.

Pods Version

pods 2.7.12

WordPress Environment

wp 5.1.1

Schermafbeelding 2019-04-30 om 14 24 40

Schermafbeelding 2019-04-30 om 14 58 32
Schermafbeelding 2019-04-30 om 14 58 41
Schermafbeelding 2019-04-30 om 14 59 12
Schermafbeelding 2019-04-30 om 14 59 18

@issue-label-bot

This comment has been minimized.

Copy link

commented Apr 30, 2019

Issue-Label Bot is automatically applying the label Type: Bug to this issue, with a confidence of 0.76. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the Type: Bug label Apr 30, 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.