path: #overlay=admin/structure/taxonomy/tagname
- click 'Show row weights' after creating some term ( all weights are '0' )
- set the weight of one term
- click save

now the items are not sort as they are supposed to.

Using the normal 'drag to re-order' works fine.

tested in firefox 3.6.10 and chrome 8.0.552.0 dev

issue occurs only when the weights of multiple terms are '0'

CommentFileSizeAuthor
#97 941266-97.patch4.08 KBnginex
#89 d7_order_of_terms_with-941266-89.patch1.33 KBJohn Cook
#86 after-apply-patch-941266.png33.55 KBamit.drupal
#86 before-apply-patch-2-941266.png33.85 KBamit.drupal
#86 before-apply-patch-941266.png34.01 KBamit.drupal
#84 941266-84.patch4.04 KBaerozeppelin
#84 test-only-fail-941266-84.patch1.8 KBaerozeppelin
#78 941266-78.patch2.83 KBpfrenssen
#74 order_of_terms_with-941266-74.patch1.69 KBkerby70
#71 941266-70.patch1.69 KBrpayanm
#71 941266-interdiff.txt689 bytesrpayanm
#68 941266-68.patch1.7 KBrpayanm
#68 941266-68-test_only.patch1.13 KBrpayanm
#64 order_of_terms_with-941266-64.patch1.13 KBNitesh Sethia
#50 order-weighted-terms-941266-49-test_only.patch1.21 KBpfrenssen
#49 order-weighted-terms-941266-49.patch2.95 KBpfrenssen
#49 interdiff.txt3.85 KBpfrenssen
#48 order-weighted-terms-941266-48.patch4.37 KBpfrenssen
#43 order-weighted-terms-941266-43.patch4.36 KBsidharthap
#40 order-weighted-terms-941266-40.patch2.25 KBsidharthap
#36 order-weighted-terms-941266-36.patch2.12 KBDavid_Rothstein
#35 order-weighted-terms-941266-35-D7.patch2.1 KBDavid_Rothstein
#29 order_weighted_terms-941266-29.patch3.98 KBparanojik
#22 order_weighted_terms-941266-22.patch3.55 KBAlbert Volkman
#19 941266-19-taxonomy_preserve_term_ordering-test_only.patch2.35 KBpfrenssen
#19 941266-19-taxonomy_preserve_term_ordering.patch3.5 KBpfrenssen
#13 941266-13-taxonomy_preserve_term_ordering.patch1.15 KBpfrenssen
#13 941266-13-taxonomy_preserve_term_ordering-with_test.patch3.66 KBpfrenssen
#10 preserve-term-ordering-test-941266-10.patch2.51 KBlliss
#4 941266-4-preserve-term-ordering.patch1.13 KBpfrenssen
tax_02.png60.15 KBscuba_fly
tax_01.png56.58 KBscuba_fly
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

scuba_fly’s picture

So as seen in the attached screen shots, i would expect the term 'Bank' to be on top of the list.

scuba_fly’s picture

Assigned: scuba_fly » Unassigned
pfrenssen’s picture

Title: path: #overlay=admin/structure/taxonomy/tagname - click 'Show row weights' after creating some term ( all weights are '0' ) - se » Order of terms with same weight messed up after saving
Version: 7.0-beta1 » 7.x-dev
Priority: Minor » Normal

I can confirm this issue in 7.x-dev. What's more, you don't even need to change any weights. Just click on "Reset to alphabetical" and then again on "Save". The terms are then no longer in alphabetical order.

This happens because taxonomy_overview_terms_submit() does not order the terms the same way as taxonomy_get_tree() does. When the terms are reset to alphabetical, all weights are simply set to 0. This works fine with the standard taxonomy_get_tree() function as this shows terms with the same weight in alphabetical order. However when resubmitting the form taxonomy_overview_terms_submit() is called which only orders by weight, not by alphabet.

pfrenssen’s picture

Status: Active » Needs review
FileSize
1.13 KB

patch

rggoode’s picture

I'm having a problem with this also. I'm running Drupal 7.8 and have a taxonomy that I want to use in a Jump menu.

I can set the desired order for the hierarchical taxonomy term list manually and that appears to work. But when I try to create a view using that vocabulary, the list order is completely different. When I go to admin/structure/taxonomy/vocabulary_name and change the view there to Show Row Weights, the term weights are totally random.

When I change the term/row weights to the order I'm seeking, the weights are lost as soon as I save the settings. They simply return to the random order (even though they are visually retaining the order I set manually)

The manually-set order is preserved in the taxonomy FIELD that I use to apply terms to content. But NOT in any taxonomy list that I try to create in Views. To make matters worse, when I try to set the sort order to just display by the term Title, in alpha order, it still retains the random order in the term weight.

xjm’s picture

hass’s picture

Priority: Normal » Major
marcingy’s picture

Priority: Major » Normal

This is not major

xjm’s picture

Status: Needs review » Needs work
Issue tags: +Needs tests, +Needs reroll

Let's get an automated test to demonstrate this bug in 8.x. The original fix. will also need a reroll.

lliss’s picture

The attached patch creates a test that checks this functionality. The error can be found by resetting a list of terms to alphabetical and then simply saving the list of terms.

tim.plunkett’s picture

Status: Needs work » Needs review

For the bot

Status: Needs review » Needs work

The last submitted patch, preserve-term-ordering-test-941266-10.patch, failed testing.

pfrenssen’s picture

Thanks for the test! I rerolled my patch from #4 to the latest 8.x. First one is without test, second one includes the test.

pfrenssen’s picture

Status: Needs work » Needs review
tim.plunkett’s picture

For future reference, the pattern is to upload just test and then the fix and test combined. But since we already saw it fail, this is fine.

Status: Needs review » Needs work

The last submitted patch, 941266-13-taxonomy_preserve_term_ordering-with_test.patch, failed testing.

pfrenssen’s picture

The test still fails because it is comparing the order in which the terms were initially created with the final alphabetically ordered result, and these are not necessarily the same, unless they were entered in alphabetical order.

What is the intentional behavior in this case? I assume the intention is to have all terms of equal weight to be ordered alphabetically, not in the order in which they were created. At the moment if you create a new vocabulary and enter some terms in random order (eg. apple - strawberry - orange - banana) and then list the terms they are shown in alphabetical order. Only after "resetting" and "saving" the order is back to the original order. This is the way it currently works in both D8 and D7.

tim.plunkett’s picture

I just discusses this with lliss, and we came to the same realization. I think he plans to revisit this tomorrow.

pfrenssen’s picture

I rewrote the test according to my assumptions from #17. Also improved the comments in the patch a bit.

tim.plunkett’s picture

Status: Needs review » Needs work
Issue tags: +Needs tests, +Needs reroll

The last submitted patch, 941266-19-taxonomy_preserve_term_ordering.patch, failed testing.

Albert Volkman’s picture

Status: Needs work » Needs review
FileSize
3.55 KB

Re-roll.

jthorson’s picture

jthorson’s picture

Issue tags: -Needs reroll

Adjusting Tags.

dcam’s picture

I tested #22. Prior to applying the patch, taxonomy terms that were given the same weight would not be ordered alphabetically after saving. After applying the patch, terms with the same weight were being properly ordered alphabetically. So it worked for me.

There was a whitespace error when applying the patch, an extra new line at the end of the test file. I'm not sure if that matters.

pfrenssen’s picture

Status: Needs review » Needs work

@dcam: thanks for the review! Whitespace does matter, so setting this to 'needs work'. I will revisit this asap.

tim.plunkett’s picture

Issue tags: -Needs tests

Removing tag

Albert Volkman’s picture

Status: Needs work » Needs review

Thanks for the reviews. The file was missing a newline, which is required per the coding standards-

http://drupal.org/coding-standards#indenting

paranojik’s picture

git complained about a whitespace error (1 line adds whitespace errors.) and the test's class name was wrong, so the testing module didn't pick it up. I rerolled the patch with the fixes.

Otherwise the patch fixes the problem.

dcam’s picture

Status: Needs review » Needs work

The patch no longer solve the issue. Equally-weighted terms are still sorted in non-alphabetical order after saving. It also fails its own test now.

Albert Volkman’s picture

@dcam so does the new test "WeightAlphaResetTest" fail for you locally?

dcam’s picture

Yes, sorry for not being clear about that. I tested it locally. I'll let Testbot try it again too.

dcam’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, order_weighted_terms-941266-29.patch, failed testing.

David_Rothstein’s picture

Version: 8.x-dev » 7.x-dev
Status: Needs work » Needs review
FileSize
2.1 KB

I don't think this should hardcode alphabetical sorting. Don't we actually want to just preserve the current order when the weights are the same?

I needed this for a Drupal 7 site, so here is a patch (temporarily) for Drupal 7 to let the testbot run on it. I'll post a Drupal 8 reroll in a bit.

This still needs tests (we'd need to check if the tests that were already written above can be modified for this), but in manual testing it seems to work.

It also might make sense to move this sorting function to somewhere more general, since "sort by weight but otherwise preserve the current order" could be a pretty common use case.

David_Rothstein’s picture

Version: 7.x-dev » 8.x-dev
FileSize
2.12 KB

OK, tests passed - here's the Drupal 8 patch.

Still needs to incorporate the new tests and possible other improvements discussed above.

dcam’s picture

Status: Needs review » Needs work

The last submitted patch, order-weighted-terms-941266-36.patch, failed testing.

sidharthap’s picture

Assigned: Unassigned » sidharthap

Assigning

sidharthap’s picture

Status: Needs work » Needs review
FileSize
2.25 KB

Here is the new patch. I tested the patch and it is working. simple test also pass for this patch.

sidharthap’s picture

tagged to IndiaAug31

Status: Needs review » Needs work

The last submitted patch, order-weighted-terms-941266-40.patch, failed testing.

sidharthap’s picture

Status: Needs work » Needs review
FileSize
4.36 KB

i changed the test file.

leslieg’s picture

Assigned: sidharthap » Unassigned

needs reroll - patch did not apply to drupal 8.0-alpha3

pfrenssen’s picture

Issue tags: +Needs reroll
pingers’s picture

  1. +++ b/core/modules/taxonomy/lib/Drupal/taxonomy/Form/OverviewTerms.php
    @@ -31,6 +31,11 @@ class OverviewTerms extends FormBase {
    +  ¶
    

    Remove the whitespace.

  2. +++ b/core/modules/taxonomy/lib/Drupal/taxonomy/Form/OverviewTerms.php
    @@ -379,8 +384,21 @@ public function buildForm(array $form, array &$form_state, VocabularyInterface $
    +    //Sort terms based on weight and on the current order in which they are
    

    Add a space after comment slashes.

  3. +++ b/core/modules/taxonomy/lib/Drupal/taxonomy/Form/OverviewTerms.php
    @@ -466,5 +484,5 @@ public function submitForm(array &$form, array &$form_state) {
    +  ¶
    

    More whitespace.

  4. +++ b/core/modules/taxonomy/taxonomy.module
    @@ -1188,6 +1188,34 @@ function taxonomy_taxonomy_term_delete(Term $term) {
    +  // If the weights match, sort by the current order instead.
    

    "If the weights are identical" might be better.

  5. +++ b/core/modules/taxonomy/taxonomy.module
    @@ -1188,6 +1188,34 @@ function taxonomy_taxonomy_term_delete(Term $term) {
    +  $a_order = (is_array($a) && isset($a['current_order'])) ? $a['current_order'] : 0;
    

    Can be simplified to just $a_order = isset($a['current_order'] ? $a['current_order'] : 0;

  6. +++ b/core/modules/taxonomy/taxonomy.module
    @@ -1188,6 +1188,34 @@ function taxonomy_taxonomy_term_delete(Term $term) {
    +
    

    Too many new lines.

pfrenssen’s picture

Assigned: Unassigned » pfrenssen
Status: Needs review » Needs work
pfrenssen’s picture

Issue tags: -Needs reroll
FileSize
4.37 KB

Straight reroll.

pfrenssen’s picture

Assigned: pfrenssen » Unassigned
Status: Needs work » Needs review
FileSize
3.85 KB
2.95 KB

Addressed the remarks from above and made the following improvements:

  • Replaced the uasort() callback function with an anonymous function.
  • Leverage \Drupal\Core\Component\Utility\SortArray::sortByKeyInt().
  • Removed the cleaning up of the current order weights, this is not harmful in any way, so there's no need to waste cycles in cleaning it up.
pfrenssen’s picture

Forgot the test only patch, here it is. This one should fail.

Status: Needs review » Needs work

The last submitted patch, order-weighted-terms-941266-49-test_only.patch, failed testing.

pfrenssen’s picture

Status: Needs work » Needs review
pfrenssen’s picture

It's been over a month, let's retest the patch to see if it still green.

pfrenssen’s picture

leslieg’s picture

The last submitted patch, 48: order-weighted-terms-941266-48.patch, failed testing.

jthorson’s picture

leslieg’s picture

Assigned: Unassigned » leslieg
Issue summary: View changes
pfrenssen’s picture

YesCT’s picture

Assigned: leslieg » Unassigned
Status: Needs review » Needs work

#49 failed. setting to needs work since the testbot did not. (could also use more direction as to the next steps here)

unassigning also since it has been a while. feel free to jump back in.

pfrenssen’s picture

Status: Needs work » Needs review

#49 was green actually! #50 is the one that is red, but it's the test-only patch which should fail to prove that it works. So this can go back to needs review :)

Berdir’s picture

+++ b/core/modules/taxonomy/lib/Drupal/taxonomy/Form/OverviewTerms.php
@@ -367,8 +368,24 @@ public function buildForm(array $form, array &$form_state, VocabularyInterface $
+    // form.
+    $current_order = 0;
+    foreach ($form_state['values'] as $tid => &$value) {
+      if (isset($form[$tid]['#term'])) {
+        $value['current_order'] = $current_order++;
+      }
+    }

Hm, messing with $form_state['values'] directly is a bit weird.

Not sure if there's a better possibility.

jhedstrom’s picture

Status: Needs review » Needs work
Issue tags: +Needs reroll

Needs a reroll at a minimum, and a response for #62.

Nitesh Sethia’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 64: order_of_terms_with-941266-64.patch, failed testing.

jhedstrom’s picture

Issue tags: +Needs reroll

Patch in #64 is the test only.

rpayanm’s picture

Status: Needs work » Needs review
FileSize
1.13 KB
1.7 KB

Trying.

Status: Needs review » Needs work

The last submitted patch, 68: 941266-68.patch, failed testing.

The last submitted patch, 68: 941266-68-test_only.patch, failed testing.

rpayanm’s picture

Status: Needs work » Needs review
FileSize
689 bytes
1.69 KB

Status: Needs review » Needs work

The last submitted patch, 71: 941266-70.patch, failed testing.

Sharique’s picture

+++ b/core/modules/taxonomy/src/Form/OverviewTerms.php
@@ -380,8 +381,25 @@ public function buildForm(array $form, FormStateInterface $form_state, Vocabular
+    $values = $form_state->getValues();

It should be $values = $form_state->getValues('terms');

kerby70’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll
FileSize
1.69 KB

Reroll with change from #73 attached.

Status: Needs review » Needs work

The last submitted patch, 74: order_of_terms_with-941266-74.patch, failed testing.

pfrenssen’s picture

Marked #2411301: Alphabetical sort order lost after clicking save as a duplicate of this issue.

Please note that up to #49 this patch included a test, which has been lost in the reroll of #64. When this is rerolled the test should be added back.

David_Rothstein’s picture

Issue tags: +Needs backport to D7
pfrenssen’s picture

Status: Needs work » Needs review
Issue tags: +DrupalCampSpain2015
FileSize
2.83 KB

Rerolled and added back the test.

I just tested this manually and this use case doesn't work as expected:

  1. Create a term "A".
  2. Create a term "B".
  3. Drag "B" above "A". Press "Save".
  4. Click "Reset to alphabetical" and confirm.
  5. Drag "B" above "A" again and press "Save".

Now "B" will not be moved above "A" but it remains in alphabetical order.

I also don't understand why the test changed like this. Reading the code it seems like this shouldn't be needed.

manauwarsheikh’s picture

Status: Needs review » Needs work
RavindraSingh’s picture

@manauwarsheikh, what needs to be improved in this issue. please add your comments in detail which you found to be be implemented.

pfrenssen’s picture

@RavindraSingh the needed work is described in #78, the issue was just set to 'Needs review' for the test bot.

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.

aerozeppelin’s picture

Rerolled patch from #78. Added more tests.

The last submitted patch, 84: test-only-fail-941266-84.patch, failed testing.

amit.drupal’s picture

Review Patch #84.
I am little confuse for review patch.
After Apply Patch there is no changes in term Order of terms Weight.

jhedstrom’s picture

Status: Needs review » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update

From the IS:

issue occurs only when the weights of multiple terms are '0'

I cannot manually reproduce this via the UI on the latest 8.3.x. When I set a weight to 0 for more than one item, they automatically get distinct weights.

From Drupal\taxonom\Form\OverviewTerms::submitForm():

    // Renumber the current page weights and assign any new parents.
    $level_weights = array();
    foreach ($form_state->getValue('terms') as $tid => $values) {
      if (isset($form['terms'][$tid]['#term'])) {
        $term = $form['terms'][$tid]['#term'];
        // Give terms at the root level a weight in sequence with terms on previous pages.
        if ($values['term']['parent'] == 0 && $term->getWeight() != $weight) {
          $term->setWeight($weight);
          $changed_terms[$term->id()] = $term;
        }
        // Terms not at the root level can safely start from 0 because they're all on this page.
        elseif ($values['term']['parent'] > 0) {
          $level_weights[$values['term']['parent']] = isset($level_weights[$values['term']['parent']]) ? $level_weights[$values['term']['parent']] + 1 : 0;
          if ($level_weights[$values['term']['parent']] != $term->getWeight()) {
            $term->setWeight($level_weights[$values['term']['parent']]);
            $changed_terms[$term->id()] = $term;
          }
        }
        // Update any changed parents.
        if ($values['term']['parent'] != $term->parents[0]) {
          $term->parent->target_id = $values['term']['parent'];
          $changed_terms[$term->id()] = $term;
        }
        $hierarchy = $term->parents[0] != 0 ? VocabularyInterface::HIERARCHY_SINGLE : $hierarchy;
        $weight++;
      }
    }

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.

John Cook’s picture

This issue still exists on Drupal 7.

As such, I've started on a backport. The functionality has been ported, but the tests still need to be written.

John Cook’s picture

Status: Postponed (maintainer needs more info) » Needs review

Setting to needs review so the d7 port can be tested.

Alan D.’s picture

Patch #89 helped on D7 but needs work (I think) as D7 needs to support PHP 5.2.... Anonymous functions are 5.3+ I believe, not that we have anyone on these insecure legacy PHP versions

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.

lamp5’s picture

Patch #89 works well on D7, thanks @John Cook.

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.

nginex’s picture

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.

Daniel Kulbe’s picture

After I applied #97 to D8.9 I got 2 notices on save:

Notice: Undefined index: tid:21558:0 in Drupal\taxonomy\Form\OverviewTerms->buildForm() (line 257 of core/modules/taxonomy/src/Form/OverviewTerms.php).

Notice: Undefined index: depth in Drupal\taxonomy\Form\OverviewTerms->buildForm() (line 258 of core/modules/taxonomy/src/Form/OverviewTerms.php).

But the issue remains. The updated weights and parents are not applied to the terms.

danflanagan8’s picture

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

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Needs review » Postponed

This does appear to be a duplicate of https://www.drupal.org/project/drupal/issues/2928661
Credit needs to be moved over but then this can be closed

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Postponed » Closed (duplicate)
Issue tags: +Bug Smash Initiative

Closing as a duplicate, and moved credit over to #2928661: Reordering taxonomy terms after "Reset to alphabetical" yields incorrect results upon save. It is a later issue but there has been recent work over there.