Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.So, when disabling the Announcements feature set on the Enabled Functionality page, for example, I expected that I would no longer be able to create Announcements, but that's not the case. Disabling that feature set removes the Featured News section from the homepage and the user group sidebars, but you can still create announcements and even feature them.
The same is true when you disable Galleries, and I suspect it would be true for Events, too (though I haven't tested, because, at least at one point, dire consequences would ensue if I were to disable Calendar & Events).
It may be that this works as intended, but it was contrary to my expectations, so I wanted to check and make sure.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | Error_Announcement_NoAssociation.png | 30.69 KB | kellyo |
Comments
Comment #1
kellyo CreditAttribution: kellyo commentedOne other note on this subject:
If I disable the Admissions feature set, any Admissions content is still displayed (including in the Featured News section, if it's been promoted there). But then, when re-enabling the feature set, that same content is not automatically re-associated with the Admissions user group. In addition, it doesn't show up in the Recent Content block on the Admin dashboard (it is listed when you click on All Content, but for whatever reason, it doesn't make the Admin Dashboard cut).
Finally, when editing those pieces of once-Admissions content, you get the following error:
Comment #2
jgraham CreditAttribution: jgraham commentedAgreed, that this behavior is very misleading and contrary to what most(all?) users would expect.
Unfortunately this is external to julio and a core issue #1441950: Node types removed from hook_node_info with base = 'node_content' cannot be deleted related to features #1055460: Disabling a feature does not disown content type
We might be able to get some helper code in place to help mitigate the problems you are describing.
What should happen;
1. Warn user that disabling feature may delete content. Destructive options should be protected against.
2. Delete all content of necessary types depending on disabled functionality.
3. Delete the content types.