The experimental block_place.module is now in core, but we can't file issues against it. It needs an issue component to be created for it.

Comments

andrewmacpherson created an issue. See original summary.

cilefen’s picture

cilefen commented
Project: Drupal core » Drupal.org site moderators
Version: 8.2.x-dev »
Component: other » Project/Git problem

I think this goes to the webmasters. It should not be controversial.

cilefen’s picture

cilefen commented
Project: Drupal.org site moderators » Drupal core
Version: » 8.2.x-dev
Component: Project/Git problem » other

Oh wait, you were right the first time.

cilefen’s picture

cilefen commented
Status: Active » Reviewed & tested by the community

I am just going to mark this RTBC.

pwolanin’s picture

pwolanin commented

My hope is that this will be merged with the block module, so I'd be happy to have people file issues against block module in the mean time.

Certainly agree experimental modules are in an odd place in terms of issue components since they may proliferate, and may be removed later. Maybe just an "expermenal modules" component?

xjm’s picture

xjm
she/her
Primary language English
commented
Status: Reviewed & tested by the community » Postponed
Related issues: +#2660144: [Plan] Update core components, +#2702321: Group core components into broad categories

I'd actually prefer to just file issues for block_place against the block.module component. See: #2660144: [Plan] Update core components If that's what the authors prefer as well, let's not add an additional component for now.

Something like #2702321: Group core components into broad categories would be ideal for this, but that's not likely to happen soon unfortunately. The module is likely to be in the core Block system before that happens. For now, let's postpone this issue and continue to file issues against the Block module, and maybe this can be wontfix before the too-far-flung future.

Thanks all!

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

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented

Can we agree to tag issues with block_place? Otherwise how do we search for issues against a block_place? There are 5 pages of 8.x block issues.

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

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.

nerdstein’s picture

nerdstein
he/him
Primary language English
Location United States
commented
Issue tags: +MidCamp2017

I found this issue and it looks like it hasn't moved recently. I had some thoughts on this.

I think this should be a separate component and a separate module. By not merging it with the block module, this offers a clean way to turn this feature on/off.

Also, it would be really nice to be able to separate the issue as a component to be tracking that specific feature.

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

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now 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.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). 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.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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.

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

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

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

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now 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.

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

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now 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

quietone commented
Status: Postponed » Closed (outdated)

block_place was removed from Drupal 9.0.0 so there is no longer a need to add it to the component list. #3084472: Remove Place Blocks module

I am closing this as outdated.