Contrib.social

Upgrade to 2.0 failed, broke site: install hook(s) couldn't run; php 8 requirement not declared or evident

Open on Drupal.org →
Created on 31 January 2024, 11 months ago
Updated 26 June 2024, 6 months ago

Problem/Motivation

I've got a client with a drupal 8 site, using this module. It has been a huge pain and blocker to moving forward with upgrades, breaking the site in a couple different ways.

`2.0` advertises as having compatibility with drupal 8, 9, and 10..

First, an attempt to update from `1.0-beta4` to `2.0` as a preparatory step on the drupal 8 version of the site broke things, which seemed to be due to, an install hook that didn't/couldn't run (to adjust entity field settings, looked like). I thought I got through that, very painstakingly downgrading, uninstalling, upgrading, enabling, but alas those operations resulted in the the content type losing the field entirely.

I attempted to reconfigure the field by hand, though dates/settings from content in the database still weren't populating and the site's events thus still had no dates or all day designations. When I attempted to edit, I had a broken site again, and determined that the use of a union type hint in DateRangeAllDayHelper was responsible, because for other "old site" reasons I was running my dev environment on php 7.4, and union type hints didn't land in php until 8.

But `2.0` didn't advertise or declare php 8 as a hard requirement for installation.

What carelessness. And what a mess I've got on my hands now.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

🇺🇸United States emjayess

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

Comments & Activities

  • Issue created by @emjayess
  • Comment 11 months ago →
    🇪🇸Spain tunic Madrid

    I'm sorry to hear that.

    I suggest to stick to release 8.x-1.0-beta4 until you upgrade to Drupal 9.5, then switch to the 2.0.0 release.

    Personally, I won't have time to work on this, I would just drop Drupal 8 support on 2.0.0. but patchs are welcome.

  • Comment 6 months ago →
    🇺🇸United States emjayess

    In issue #3421437 🐛 PluginNotFoundException: The "field_item:daterange_all_day" plugin does not exist. Active , I see there are others that encountered the same problem, and at around the same time.

    This isn't just inconvenient, it blocks the upgrade path – seemingly because the entity or field update has never been correctly integrated or deployed in a compatible way for Drupal >8.7.

    It *breaks* the site, *breaks* drush actions, and it is an utterly maddening thing to try and sort through. All just because some date fields need to change a little bit, but we're more or less left to guess and stab.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024