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

Some setting files not being deleted after deleting a content type #5860

Closed
robertgarrigos opened this issue Nov 14, 2022 · 5 comments
Closed

Comments

@robertgarrigos
Copy link

Description of the bug

After deleting a test content type, some settings files are still present on config/active directory.

Steps To Reproduce

  1. Create a new content type named 'test' and clic on 'save and add fields'
  2. Just don't add any field, but go to config tab and delete the content
  3. confirm deletion

Actual behaviour

The following settings files are still present on config/active:

  • field.instance.comment.comment_node_test.comment_body.json
  • field.instance.node.test.body.json

Expected behaviour

I would say those files shouldn't be there. Am I wrong?

Additional information

Backdrop v. 1.23.0

@indigoxela
Copy link
Member

@robertgarrigos this is mostly a duplicate of #5469.

As for the body field config: you still might have body field content for field.instance.node.test.body in the database.

@robertgarrigos
Copy link
Author

thanks, @indigoxela. I did look for it before posting mine....

As for the body field config: you still might have body field content for field.instance.node.test.body in the database.

Actually, I don't.

@indigoxela
Copy link
Member

Interesting... I'm pretty sure, you didn't run cron in the meantime, because when I run cron, that node body field json file gets removed.

  • For the field.instance.comment.comment_node_test.comment_body.json we already have an issue
  • The field.instance.node.test.body.json thing gets fixed by a cron run

@robertgarrigos
Copy link
Author

No, I didn't run cron. ok. Thanks.

@laryn
Copy link
Contributor

laryn commented Feb 16, 2024

No, I didn't run cron. ok. Thanks.

Closing, assuming the cron run solved this. (Reopen if I'm wrong.)

@laryn laryn closed this as completed Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants