This one surprised me a bit.

To reproduce:

  1. go to "Structure>Menus>Navigation>List Links"
  2. rearrange the article and basic page so that the basic page is first, and save that configuration
  3. delete the article content type from "Structure>Content Types"

Now when you go to the "Add Content" modal, you find that "Article" and its description remain. And if you go to "Structure>Menus>Navigation>List Links" you find that the link also remains.

What's more, if you are tempted that resetting that link with the "reset" option might solve the problem, it instead turns into an extra "Add Content" link which can't be edited or deleted, but only disabled.

Trying cache clearing has no effect.

I'm marking as critical because this is simply too easy to fall into and could easily confuse new users. I'm also unsure if this should go against dev since I haven't tested but I have the issue currently with 7.10.

Comments

AQ808’s picture

Version: 7.10 » 7.x-dev

Probably belongs in dev

AQ808’s picture

Issue summary: View changes

Clarity

joachim’s picture

Version: 7.x-dev » 8.x-dev
Issue tags: +Needs backport to D6

Confirming this on D8.
Marking as needing backport all the way to D6, as I remember seeing it there too.

webchick’s picture

Priority: Critical » Normal
Issue tags: +Needs tests

Uh, no sorry. :) This is definitely not critical. Sounds like a bug worth fixing, though. Should add tests to ensure it doesn't crop up again.

joachim’s picture

Oops, I hadn't noticed it was filed as critical.

Fixing tags.

AQ808’s picture

Don't be too critical. :) Keep in mind that I wasn't marking it critical in terms of D8... I imagine that whole ball of D8 wax is critical at this point.

This is just completely broken UX for the current D7 stable. However, I have no clue how you guys rate priority for bugs in the current stable.

Would this be better served as a 7.x-dev issue, since as a 8.x-dev it has a ton of competition against new emerging features which are bound to come in largely broken?

webchick’s picture

You can read about the severity levels here: http://drupal.org/node/45111

And nope. We always fix things in D8 first, then backport. This avoids any regressions when the new version comes out.

monteith’s picture

Issue is only partially reproduced in 8.x

1. Install the latest Drupal 8.x using the standard profile.
2. In "Structure > Menus > Navigation > List Links" rearrange "Article" and "Basic Page" so that "Basic Page" is listed first.
3. Delete the "Article" Content Type from "Structure > Content Types."

Now the "Add Content" modal defaults to adding "Basic Page" content (there is no Article or description listed.)

However, if you go back to "Structure > Menus > Navigation > List Links" the "Article" link still remains.

Resetting the link removes the "Article" link, and adds an "Add Content" link that CAN be edited but not deleted.

monteith’s picture

Assigned: Unassigned » monteith
Issue tags: +tcdrupal2012
monteith’s picture

Assigned: monteith » Unassigned
cweagans’s picture

cweagans’s picture

Issue summary: View changes

Forgot to mention cache clearing ineffective.

xjm’s picture

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Version: 8.9.x-dev » 7.x-dev
Issue tags: -Needs backport to D6 +Bug Smash Initiative

I tested this on Drupal 7 and the list on "Add Content" modal is indeed incorrect after the deletion of a content type but after clearing the cache it is correct.

For Drupal 9, the node/add page is built in \Drupal\node\Controller\NodeController::addPage where the content type names always sorted. I still tested on Drupal 9.3.x, it works just fine and there was no need to manually clear the cache.

Since this is tagged for backport, changing version.

poker10’s picture