Problem/Motivation
Uninstalling the module does not accomplish clean up of user custom fields nor access data.
The fields are locked preventing administrators form manually deleting the fields from the user entity.
Attempts to reinstall the module are blocked as the fields already exist.
Steps to reproduce
Uninstall module
Attempt to reinstall, blocked.
Proposed resolution
Add uninstall hooks to delete the fields from the user entity and token records for all users.
This blocks the ability for me to use the module or conduct R&D.
Unless I have a database backup prior to first install.
Which is impractical for any "live" actively in use drupal instance.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 2024-08-05-azure_oauth_sso-uninstall.patch | 891 bytes | emptyvoid |
Issue fork azure_oauth_sso-3466030
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
emptyvoid commentedFor those looking for ways to actively salvage a corrupted database config refer to this thread.
https://drupal.stackexchange.com/questions/164612/how-do-i-remove-a-conf....
I'm attempting to create a patch which explicitly deletes the fields on uninstall.
And attempting to clean up an active install using drush.
Comment #3
emptyvoid commentedOn an active build where you installed the module and then uninstalled it. There by preventing you from reinstalling you can issue the following commands to free up the user entity.
Comment #4
emptyvoid commentedpatching adding uninstall for user settings
Comment #5
mahdiwadi commentedI've fixed the patch and successfully applied it. The issues have been resolved.
Comment #6
mahdiwadi commentedComment #7
mahdiwadi commentedComment #8
ahmadhalahComment #9
mahdiwadi commentedComment #10
mahdiwadi commentedComment #11
mahdiwadi commented