- Issue created by @raffaelj
- 🇫🇷France fmb Perpinyà, Catalonia, EU
Thanks for reporting this. Is it also happening with the latest Git version?
> Is it also happening with the latest Git version?
I don't know, but I guess so. If I remember correctly, the latest version requires Drupal 11. I can't install Drupal 11 (in my local docker test setup), because it requires SQLite >=3.45. Now I'm waiting for 🐛 database driver crashes during install (dependency not autoloaded) Needs review to get merged. Than I'll have a working throw-away dev setup for D11 again.
During my quick test with this module, it looked like it is not capable of translating admin/settings pages of self written modules locally. So I also lost interest in digging deeper.
When this module is compatible with D10 again or when I have a working D11 setup, I might have another look.
- 🇩🇪Germany donquixote
Hello.
I was able to reproduce with latest version of this module both with Drupal 10 and Drupal 11.For now the way to resolve it is to manually remove the field before uninstall.
Fingers crossed :)We need to think about what would be the optimal solution to implement in this module.
One thing to consider is that removing the field will cause data loss, because all the tokens per user are lost.
This is why there is some merit in letting the user manually delete the field.On the other hand, this deletion also would need to happen in a deployment. So it would need a custom update hook in the project to delete the field, which would be a burden on the site builder.
- 🇫🇷France fmb Perpinyà, Catalonia, EU
Thanks for spending time on analyzing this bug. We do not really care about data deletion in this case. I would say it is expected to remove the key when the module is uninstalled. Generating a new token would not be that hard anyway.