-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix event dispatch error on Drupal 9.0 #3592
Comments
Undefined index: file_url_type...
error when navigating the the Edit Dataset form
Per discussion with @dafeder, this is pretty low priority since it only affects Drupal 9.0. Drupal 8.9 and 9.1 appear to be unaffected. |
This should be affecting 8.9 and 9.0 equally -- both are using the same version of Symfony event dispatching. So even though no one should be using 9.0 anymore (it is marked insecure and not clear there will be a new safe release of 9.0.x) we want to make sure that 8.9 and 9.1+ are both working without issue, and merge this asap. |
@dafeder A fresh instance of DKAN with Drupal 8.9.17 appears to be working fine on my local. The same is true for Drupal 9.1.11. Drupal 9.0.x appears to be broken on DKAN 2.x. All three of these version of Drupal appear to work fine when on the branch associated with the PR I've opened. |
After giving this some thought, I believe it make sense to retain the simpler logic for determining the correct method signature unless a secure version of 9.0 is release. As is, I don't think we should bring in more complex code that only serves to enable people to continue using an insecure version of core. We'll keep the PR for a while open in case there are any developments upstream, but I'm closing this issue. |
Describe the bug
Whenever I create a new dataset on a Drupal 9.0 site running DKAN, I receive a vague whitepage error, and the following is logged to watchdog:
The above behavior was not exhibited on Drupal 8.9 or 9.1.
Steps To Reproduce
Expected behavior
Creating a dataset on a Drupal 9.0 site should not result in the above error.
The text was updated successfully, but these errors were encountered: