Troubleshooting · Developer docs

Troubleshooting

Grouped by symptom, never by module, because the person with the problem does not know which module has it. One hundred questions across ten pages, each answered with the causes in the order they usually turn out to be true.

Answer API requests

A conditional field never appears, or never hides

The rules are applied in the browser by js-forms-conditionals.js, and each of these stops it without a visible error:

  • The rules are not on the page. The layout must print them into window['formConditionals' + form id]. The console then says "Conditionals not found for form ID" and every field stays visible.
  • The script missed its start. It starts only on DOMContentLoaded. Loaded with async, or added by another script, it can arrive later and never run.
  • No container. It works on .coredna-js-form containers with a _formId field, on page-per-step forms too.
  • The element has no id. Elements of some older forms have none, so they render without data-id and no rule can reach them.

A form that shows everything correctly and still cannot be completed is a different problem: a required field on a step hidden by a rule stays required on the server. Hide a group instead of the step.

The wiring is in Conditional logic and the js-forms-conditionals.js reference.

More in API requests

  1. My properties fields come back as "Error: Getter for property … not found", or glued together
  2. "414 Request-URI Too Long", or my long properties selector stops working
  3. The selector in my GET body was ignored, and the full record came back
  4. My filter returned every record
  5. A custom entity list answers a totalCount but no rows

Was this page helpful?

Your answer goes to the docs team.