-
Notifications
You must be signed in to change notification settings - Fork 118
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
[BUG] WSOD when viewing object #934
Comments
The given class still exists in 3.x, so... what exact error is popping? Or do you have stuff applied from the separation effort in Islandora/documentation#2220, which isn't quite finalized, or... yeah, don't really feel there enough info here. |
Exact error from the Drupal logs just states that the service is no longer there:
|
Which then prompts: What version of Crayfish-Commons are you actually running, given the class is still present in the latest 3.x release? Like, running premerged PRs still in progress, or a fork? Any patches applied? |
No fork nor patches 🤷 If the service still exists maybe this is a composer thing? |
Yeah, could be something like the autoloader needing to be rebuilt, or Drupal's/Drush's cache, or possibly just the webserver needing a restart to flush caches. Flush ALL the caches! :V |
Yeah wow crazy. |
Not an Islandora thing per se. If it turns out it's how it got into packagist or something I'll make a separate ticket. Closing this. Thanks for the help @adam-vessey 🙇 |
Looks like in Crayfish Commons 3.0, a service that's used in Drupal got removed and we still require it for populating the Fedora URI pseudofield.
What steps does it take to reproduce the issue?
Try to view an object or an Original File media.
When does this issue occur?
Anytime you view an object
Which page does it occur on?
Any object or media page
What happens?
You get a whitescreen
To whom does it occur (anonymous visitor, editor, administrator)?
Anyone
What did you expect to happen?
To see the object
Which version of Islandora are you using?
2.7.0
Any related open or closed issues to this bug report?
Nope
The text was updated successfully, but these errors were encountered: