Contrib.social

Provide upgrade path if functionality is added to core

Open on Drupal.org →
Created on 16 November 2021, over 2 years ago
Updated 16 June 2024, 15 days ago

Problem/Motivation

If functionality is added to core, we need to ensure this module still works correctly, and that users can move to using the core version. There is an issue currently being worked on here: https://www.drupal.org/project/drupal/issues/2245767 ✨ Allow blocks to be configured to show/hide on 200/403/404 response pages Fixed

Proposed resolution

Test module continues to work, and there are no conflicts with core.
Provide an upgrade path, so users can move to using the core version, and safely uninstall this module.

Remaining tasks

Test module continues to work with changes, once core issue is complete.
Work out proposed upgrade path for 401, 403, 404.
Provide the upgrade path, if possible. Otherwise, ensure this works along side core implementation.

🌱 Plan
Status

Fixed

Version

3.1

Component

Code

Created by

🇬🇧United Kingdom jefflogan

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 9 months ago →
    🇬🇧United Kingdom jefflogan

    Drupal 10.2 now allows for setting Block visibility for the status codes 200, 403, and 404. So for most users they should be able to move to using core. However, this module can safely run along side core's implementation.

    The only exception is that the status code 401 isn't provided for, but that probably isn't being used by most people.

    Once you configured all your blocks to use Drupal core, instead of this module, it is safe to uninstall this module.

    I have added a block listing of all blocks that are using the Block condition provided by this module. This can be found under Configuration > Development > HTTP Client Error Status Block Listing (or /admin/config/development/http-client-error-status ).

  • Status changed to Active 9 months ago
  • Comment 9 months ago →
    🇬🇧United Kingdom jefflogan
  • Status changed to Fixed 29 days ago
  • Comment 29 days ago →
    🇬🇧United Kingdom jefflogan

    A partial upgrade path is now available in the 3.1.x branch.

    There is a listing page (/admin/config/development/http-client-error-status) of all the blocks using this modules plugin for block visibility, allowing for manual configuration to swap from this module to core.

    There are also Drush commands that provide a list and to update existing blocks to use core block visibility for request status code.

    Please note that only 403, 404 and 200 status codes are catered for.

  • Comment 15 days ago →
    System Message

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

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024