When you add a new block to a region, by selecting the region name while the block is in the Disabled group, the block gets moved to the top of the list of blocks in that region. The block is flagged, as expected, with a yellow marker (telling you that you need to save).

Now click "Save blocks". When the page reloads the block now is at the end of the list of blocks in its region.

You can drag the block to the top and save again, it will stick after this.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ScoutBaker’s picture

This is due to the block weights. If you have javascript disabled, you'll see the weight column just like in D5. I believe that the actual "bug" in this case is displaying the block at the top of the region when you first select the region.

When you set the region to display a block in using the drop-down, the weight of the block is not changed when it is moved to that region. After clicking save, the blocks for a given region are, properly, displayed in weighted order. When you use the drag-and-drop functionality to drag a block to another region, the weights are recalculated automatically in the background to display in the proper order.

lyricnz’s picture

Version: 6.0-rc4 » 6.x-dev

This still happens in Drupal 6. It seems like there are two possible solutions: either update the weight of the newly enabled item, so that it genuinely belongs at the top of the region, or put it into the right place based on its current weight.

The first of those seems like the most reasonable, and should be able to use the existing row-drop code from tabledrag.

lyricnz’s picture

Version: 6.x-dev » 8.x-dev

This UI WTF has been around forever.

Short version: on the block management page, if you change the dropdown of a disabled block to a region, it visually appears at the top of that region. However, if you hit save, it appears somewhere else (depending on the block's existing weight setting, which isn't visible).

droplet’s picture

askibinski’s picture

Issue summary: View changes
Status: Closed (duplicate) » Active

This still happens in Drupal 8, and this issue is not really a duplicate of #1039666: Placing a block in a region via select dropdown moves it to the top of the region, but it will show at the bottom because that one is about Drupal 7 and also a bit different.

In my case, I place a block using the dropdown in the main content region. The admin interface will show the block at the bottom of the list of other blocks in that region. But after saving and viewing the site, it suddenly is at the top of the region. The admin interface also shows the block at the top of the list after the save action.

Maybe this can be solved together with #2138553: Enhance block instance placement to support drag and drop

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.

pameeela’s picture

Issue summary: View changes
Status: Active » Closed (outdated)
Issue tags: +Bug Smash Initiative
FileSize
25.73 KB

Very happy to report that this works now in D8/9. When you create a new block and place it, it correctly appears at the bottom of the list initially and after save.