- Issue created by @toomanynights
- πΊπΈUnited States mwebaze
@toomanynights I am assuming you are using version 8.x-1.1 of the module. Let me setup a 9.4.8 environment to recreate this.
I am also using this module on Drupal version 9.4.8, the same issues occurs with me too, I fixed this and adding a patch for it.
- πΊπΈUnited States mwebaze
@toomanynights I am unable to recreate this particular issue on D9.4.8. From the exception it appears your field doesn't have a revision table usually in the format "node_revision__field_name". When I delete this file manually however, I am able to recreate your issue. What I can do is create a patch that checks if the revision field exists.
- πΊπΈUnited States mwebaze
@toomanynights I notice my exception is slightly different from yours as it is being thrown from Core. Is your happening when you try to access the field storage page? Let me know so I can try to recreate it on my end.
@mwebase It happens when I launch field scale changing. I noticed the exception doesn't point at any particular field, rather it just goes "node_revision__". Maybe it'll help.
@ankit_sonkr, just tried your patch, unfortunately it doesn't work for me. The error is as follows:
Error: Call to a member function setComponent() on null in Drupal\precision_modifier\services\PrecisionModifierService->increasePrecision() (line 89 of modules/contrib/precision_modifier/src/services/PrecisionModifierService.php).
- πΊπΈUnited States mwebaze
@toomanynights my biggest challenge is that I cannot recreate this on my end. It appears you don't have a revisions table for the node you are trying to work with. That is the only thing I can think of.