#64 didn't quite work for me with Drupal 10.3.2. The links showed up (yay!) but they were permanently visible and laid out inline (boo).
I wasn't able to test prior patches as they no longer apply. I'm guessing the JS changes they included are necessary to fix the formatting.
The patch in #4 works in my limited testing. It fixed the import of the following entry, which previously showed the literal \textquoteright
@article {sullivan24ToH,
title = {Comparing the Perceived Intensity of Vibrotactile Cues Scaled Based on Inherent Dynamic Range},
journal = {IEEE Transactions on Haptics},
volume = {17},
number = {1},
year = {2024},
pages = {45-51},
keywords = {Actuators, Frequency modulation, Frequency response, Haptic interfaces, psychometric testing, Resonant frequency, Vibrations, wearable devices, Wrist},
doi = {10.1109/TOH.2024.3355203},
author = {Sullivan, Daziyah H. and Chase, Elyse D. Z. and O{\textquoteright}Malley, Marcia K.}
}LGTM, solves the error. Thanks!
Has anyone figured out how to recover from this? It just took down another one of my sites. Everything was working, I made a tiny change to a view and saved it, then got the WSOD:
The website encountered an unexpected error. Try again later.
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "grid_responsive" plugin does not exist. Valid plugin IDs for Drupal\views\Plugin\ViewsPluginManager are: in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).
Nothing (drush cr, drush updb, composer update, drush cim / reverting config) makes any difference. The site is just hosed.
Interesting. I think it was also a composer update that killed my site. Considering that your only package updates weren't Drupal-related, I do wonder if this is a bug with Composer not generating autoload files as expected.
If you commit your vendor dependencies to Git (such as in a build artifact), try doing a diff to see what, if anything, changed between the working and non-working versions of the site.
Sorry, I think the composer lead was a red herring. I tried everything I can think of to troubleshoot this, and today for whatever reason my site just started working again. Spooky.
I'm suffering this issue as well as of a week or two ago. Overnight and without any changes that I'm aware of, I started getting these plugin errors.
I suspect it's actually a Composer issue: https://github.com/composer/composer/issues/11982
Notice that the list of valid plugins is empty. This suggests an autoloading issue, i.e., Drupal doesn't see any plugins at all. This led me to look at Composer and I noticed that autoload_static.php is practically empty when it should be about a megabyte in size.
Hello drupal.org maintainers! Please transfer ownership of the Mailhandler project from my to id.rem.dev: https://www.drupal.org/project/mailhandler →
@id.rem.dev sorry I missed your comment. Are you still interested?
quietone → credited Dane Powell → .
I got this error after upgrading to 3.x-dev as well. I think it's partially a problem with bibcite migrations, because a piece of content that was previously listed in biblio with the month as "July-September" got created in bibcite with the date published "July-September", which is invalid.
This seems to be only a problem with this date format; normally-formatted dates seemed to be imported correctly.
Patch looks good and I confirmed it fixes the issue on php 8.2/8.3
I'm not sure if this is the best technical fix or not, but I can confirm it works and I opened an MR.
Dane Powell → made their first commit to this issue’s fork.
Hey Wim! I use the D7 Biblio module, which had a recommended migration for AMA:D9. But when this was merged, the migration was removed. I don't understand why, given that the replacement module (bibcite) has had a recommended (though not stable) release since last year.
Do you know why it was removed?
I also encountered this bug using Media 7.x-1.10 and File Entity 7.x-1.10, which don't have any such file_metadata table, and can confirm the patch fixes it. However, I'm not sure if it might leave unresolved issues (i.e., whatever data exists in that table not getting migrated).
Does the media_migration module intend to support Media 7.x-1.x?
Please transfer ownership of Mail Comment from Dane Powell to ram4nd
Thanks!
Please make Steven Jones owner and remove me as maintainer: https://www.drupal.org/node/1140304/maintainers →
Dane Powell → created an issue.
Dane Powell → created an issue.
Dane Powell → created an issue.
Dane Powell → created an issue.
Dane Powell → created an issue.
Dane Powell → created an issue.
Dane Powell → created an issue.
Dane Powell → created an issue.
Dane Powell → created an issue.
For anyone wondering about the commits for this (#162, #163, #166, #167) those are from waaaay back in 2009. No idea why they are just now being attached to this issue. This is still an issue in all 8.x branches.