Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi all,
Has anyone else experienced issues when trying to uninstall this set of modules? When I try to uninstall the site becomes generally flakey and if I go into the Reports > List Fields page I see a whole bunch of errors relating to PM fields. I approached this as I would any other drupal module ie disable and then uninstall. Currently I have had to put them all back and reenable them to stop drupal flaking out on me.
Comments
Comment #1
GAMe CreditAttribution: GAMe commentedin fact even if I just disable the modules I get the error :-/
Comment #2
juliangb CreditAttribution: juliangb commentedCould you please clarify "flakey". Please could you post screenshots of the errors?
I would also suggest that if you are starting to use this module you start with the 2.x branch. It is more advanced than 1.x, and it will save you having to upgrade soon.
Comment #3
juliangb CreditAttribution: juliangb commentedComment #4
GAMe CreditAttribution: GAMe commentedHi, your right I should have started with v2 but I just wanted to test if I was going with PM or going the custom route. I have fixed all the errors by manually cleaning the db myself removing any instances of pm records. Mainly these records were left in the fields_config and field_config_instance tables however some were still lingering elsewhere. When I said flakey I simply meant the site was running a little sluggish and would throw errors on certain pages. As I have fixed it now I cant show you screen dumps so Im sorry about that but it is resolved now. Maybe this was something with my install but either way thanks for the reply.
Comment #5
juliangb CreditAttribution: juliangb commentedMoving this into a task to ensure that all field / field instances are removed on full install.
Comment #6
D34dMan CreditAttribution: D34dMan commentedComment #8
D34dMan CreditAttribution: D34dMan commentedComment #9
D34dMan CreditAttribution: D34dMan commentedComment #10
juliangb CreditAttribution: juliangb commentedI still see database tables relating to pm person fields, as well as one from pm description field.
Comment #11
D34dMan CreditAttribution: D34dMan commentedIf you are talking about pmperson table then #2353995: Drop pmperson table in next major version could be opened if its time to do so.
For pm description field and any other fields, i would like to know exact table names to debug further.
Comment #12
juliangb CreditAttribution: juliangb as a volunteer commentedSee the field data and field revision tables in the attached screenshots.
Comment #13
NancyDruFields usually do not get deleted immediately. There seems to be a six hour window before a cron run that actually removes them.
Comment #14
D34dMan CreditAttribution: D34dMan commentedoh i missed the priority on this one, sorry. Would be working on this asap.
@NancyDru, yeah that is the default drupal behaviour as expected when field_delete_instance is used
Comment #16
D34dMan CreditAttribution: D34dMan commentedComment #17
D34dMan CreditAttribution: D34dMan commentedSorry for the typo in commit message, it should be "fields" and not "files"...
Comment #19
juliangb CreditAttribution: juliangb as a volunteer commentedTested.