Am I correct in assuming that it's not possible to deselect all node types from the "Node type condition" list in the node edit screen? Or is this a browser or drupal problem?

A solution would be to always add an option "none" (and possibly add a Javascript that will then actually deselect all but the None option). This way, if you accidentally select a Node Type Condition you can undo your mistake.

Or perhaps Drupal has a standard way of dealing with this.

Comments

brankoc’s picture

brankoc commented

I just had a customer complain that they couldn't deselect the node type they had accidentally selected. I had to go into the database and remove the selected node type by hand, which is Not Fun, as it is not clear what the values in the relevant field stand for.

I am willing to try and patch this myself, but would like some feedback on what kind of solutions you would accept. In my earlier report I already listed a possible solution.

Please let me know if you are interested,

sense-design’s picture

sense-design
sense
Primary language German
Location Münster
commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not pose the problem comprehensible.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order this issue no longer remains, I put this issue to "fixed".

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.