Can't uninstall l10n_client_contributor

Created on 4 September 2024, 4 months ago

Problem/Motivation

While trying to translate a module locally, I fiddled a bit with this module. It looks like it doesn't work with Drupal 10... Now I can't uninstall the l10n_client_contributor anymore:

The following reason prevents Localization Client Contributor from being uninstalled:
The Localization client contributor API key field type is used in the following field: user.l10n_client_contributor_key

I didn't add any value to the user api key field.

No big problem, because it's only a test installation, but I wanted to let you know. I skimmed the commit history and it doesn't look like this issue was addressed since alpha2.

Steps to reproduce

Versions:

* Drupal 10.3.2
* drupal/xmlrpc 1.0.0-rc2
* drupal/l10n_client 3.0.0-alpha2 (because alpha3 and @dev both require Drupal 11)

Usage

* installed via composer
* enabled client via GUI
* tried, clicked, experienced bugs
* installed xmlrpc via composer (required by contributor)
* enabled contributor (in hope of magically fixing bugs)
* tried and clicked some more
* uninstalled client (worked)
* tried to uninstall contributor (failed)

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

3.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • 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.

Production build 0.71.5 2024