OrchardCore icon indicating copy to clipboard operation
OrchardCore copied to clipboard

Taxonomy cannot select Term type, Term content type not auto-restored

Open pyy-alt opened this issue 6 months ago • 3 comments

When using OrchardCore (please specify version), I encountered the following issue:

  1. Due to accidental deletion or content definition corruption, the built-in Term content type is missing and not auto-restored.
  2. When creating a new Taxonomy, the "Term Content Type" dropdown does not show the Term type, only other types like Tag, Category, etc.
  3. This makes it impossible to create/manage Terms, breaking Taxonomy/Term related features.

Expected:

  • OrchardCore should auto-restore/recreate the built-in Term type if missing, or provide a one-click fix in the admin UI.
  • Or, clearly document how to manually restore the Term type.

Steps to reproduce:

  1. Delete the Term content type or corrupt content definitions.
  2. Try to create a new Taxonomy, and find no Term type in the dropdown.

Additional info: Already tried restarting, switching themes, enabling/disabling modules, but the issue persists.

Image

pyy-alt avatar Jul 08 '25 08:07 pyy-alt

It's not really a bug that if you delete something then it breaks things :). So that's expected. But we could have "system content types", similar to system roles, that users can't delete or change in destructive ways. I believe we talked about this before, but I can't find it among the issues (and it's not an existing feature).

Piedone avatar Jul 08 '25 14:07 Piedone

Question is, does it throw a server error or does it show a warning message about the deleted content type? There is no way that we can recover a deleted content type as of now unless we would have an history/audit trail on the content types. That way restoring the content type could be proposed from the UI. And of course "system content types" could be another solution but the issue would still exist for every other "user content types".

Recovery would be a clever thing.

Skrypt avatar Jul 08 '25 15:07 Skrypt

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

github-actions[bot] avatar Jul 10 '25 17:07 github-actions[bot]