- Issue created by @g089h515r806
- Status changed to Postponed
over 1 year ago 5:45am 30 July 2023 - 🇨🇳China g089h515r806
After I move them to field_validation_legacy, to enable field_validation_legacy module, I get fatal errors:
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "unique_field_validation_rule" plugin does not exist. Valid plugin IDs for Drupal\field_validation\FieldValidationRuleManager are: length_constraint_rule in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of core\lib\Drupal\Component\Plugin\Discovery\DiscoveryTrait.php).
Which make it difficult to update. It seems Drupal core does not support enable a new module when there is PluginNotFoundException.
- Status changed to Active
over 1 year ago 6:03am 30 July 2023 -
g089h515r806 →
committed 6c90fa2b on 3.0.x
Issue #3377899 by g089h515r806: Move original validation rule to...
-
g089h515r806 →
committed 6c90fa2b on 3.0.x
- Status changed to Fixed
over 1 year ago 6:06am 30 July 2023 Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
5 months ago 3:03pm 18 August 2024 - 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
Upgrading from 8.x dev to 3.0.x dev causes the error described in #2 with no way out so the user is forced to downgrade back to 8.x - There is no obvious way for the average user to upgrade now to v3.
- 🇨🇳China g089h515r806
There is document for update:
https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →