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.

CommentFileSizeAuthor
#12 image.jpg132.2 KBjuliangb
#12 image.jpg147.69 KBjuliangb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

GAMe’s picture

in fact even if I just disable the modules I get the error :-/

juliangb’s picture

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

juliangb’s picture

Priority: Critical » Major
Status: Active » Postponed (maintainer needs more info)
GAMe’s picture

Hi, 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.

juliangb’s picture

Title: Poor Uninstall » Ensure all fields are removed on uninstall
Category: Bug report » Task
Status: Postponed (maintainer needs more info) » Active
Issue tags: -pm, -error, -failed

Moving this into a task to ensure that all field / field instances are removed on full install.

D34dMan’s picture

Assigned: Unassigned » D34dMan

  • D34dMan committed 019fe37 on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed 0df6f48 on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed 1d79a95 on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed 445afec on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed 56e71f1 on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed 5e33f6d on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed 70e2723 on 7.x-2.x
    Issue #2358051 by GAMe: Fixing wrong function name.
    
  • D34dMan committed 87a3017 on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed bc30f52 on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
  • D34dMan committed e57fffd on 7.x-2.x
    Issue #2358051 by GAMe: Deleting field instances and variabels declared...
D34dMan’s picture

Status: Active » Needs review
D34dMan’s picture

Version: 7.x-1.0-alpha5 » 7.x-2.x-dev
juliangb’s picture

Status: Needs review » Needs work

I still see database tables relating to pm person fields, as well as one from pm description field.

D34dMan’s picture

I still see database tables relating to pm person fields, as well as one from pm description field.

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

juliangb’s picture

FileSize
147.69 KB
132.2 KB

See the field data and field revision tables in the attached screenshots.

NancyDru’s picture

Fields usually do not get deleted immediately. There seems to be a six hour window before a cron run that actually removes them.

D34dMan’s picture

oh 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

  • D34dMan committed 875e87b on 7.x-2.x
    Issue #2358051 by GAMe, juliangb: Removing pmperson files attached to...
D34dMan’s picture

Status: Needs work » Needs review
D34dMan’s picture

Sorry for the typo in commit message, it should be "fields" and not "files"...

  • D34dMan committed a683b6f on 7.x-2.x, develop-7.x-2.x
    Issue #2358051 by GAMe, juliangb: fixing project and table names
    
juliangb’s picture

Status: Needs review » Fixed

Tested.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.