Cannot disable module - required by Drupal, fields pending deletion

Try running cron multiple times. It took me two times. Other people said they ran cron up tp 6 times.

Deleting the module folder, running cron, then replacing the module directory allowed me to disable the module. Got the idea from this issue: http://drupal.org/node/1284358

@khalladay Thanks for the tip! Worked like a charm :)

Yes, and this is actually a Drupal core bug/feature. It's not specific to the field_collection module.

this solution worked for me #1530812: Field collection cannot uninstall cleanly due to "Required by: Drupal (Fields pending deletion)"

This worked for me too. Thanks!

Per #2/#6

Thanks for the solution!

This solution worked for me also.
It took 6 or 7 times of running the cron.

I had to fire cron off about a dozen times, and it finally worked, thought i was stuck with it forever :-)

Deleting the module and then running cron worked the first time for me :)
I Deleted the module, ran the cron, copied the module back to where it was, and then disabled it from UI.
Cheers

Ironically running the cron did the job actually :D

Run cron x3 worked for me. Thank you

#2 Worked for me at the first try
Thanks!!

I had to run cron 3 times before it actually allowed me to disable the field_collection module due to "Required by: Drupal (Fields pending deletion)".

I had the same problem and this also worked for me
DELETE FROM `field_config` WHERE `field_config`.`deleted` = 1;

i just cleaned the cache after running the query and I was able to disable the module

number #18 works fine : DELETE FROM `field_config` WHERE `field_config`.`deleted` = 1;

Running Cron resolved this issue. !!

Number #18 works nice and fast!

thanks :) #2

Running Cron worked for me. Thanks

I am not sure if its connected but even though I ran cron 1 time it didn't change but I then remembered I have a view that was based upon the (already deleted content type & fields, of that module). After deleting the view I ran cron for the second time and could now remove it.

If it was also possible without deleting the view in a different copy of the site but in any way I wanted to write this here for any case.

Don't waste time with cron.
Number #18 works nice and fast!

Cron run one time and its worked magically instead to play with database :)

I had to run cron 3 times before it actually allowed me to disable the field_collection module due to "Required by: Drupal (Fields pending deletion)".

Deletes a massive 10 rows per cron run. So the number of runs could be high of you have a lot of data. We have a user field; 183 hours or 183 forced cron runs to go to delete the 1830 records...

@perisdr Thanks man.. Run Cron x 1.. :)

Another option is to use this function through /devel/php

field_purge_batch(500);

I had a lot of field data and it saved me in Drupal 8.

drush php-eval 'field_purge_batch(500);'

Worked for me in Drupal 8

#18 worked for me. Thanks!

This khalladay's solution worked for me.

Thanks #2 worked for me

Cron Run #2 Worked For Me

Ah running cron #1 worked for me.. Thanks!

For anyone wondering why cron works. It is because it runs field_cron:
https://api.drupal.org/api/drupal/modules!field!field.module/function/fi...

Which in turn runs field_purge_batch:
https://api.drupal.org/api/drupal/modules%21field%21field.crud.inc/funct...

If you have a lot of content and the default of 10 items is used you might be running cron forever before this works (in my case I had 100,000 nodes affected). You can manually run the drush command below a few times to speed things up:

drush php-eval 'field_purge_batch(10000);'

I ultimately added this code in an update hook for deployment after the removal of the field instances (which takes a while to run but gets the job done):

  for ($i = 0; $i <= 30; $i++) {
    field_purge_batch(5000);
  }

field_purge_batch(500);
Worked in Drupal 7, thanks!

run cron work for me too, thanks

#37 worked to resolve this same issue in Drupal 8. :-)

#1 worked for me. I just ran cron once and it resolved my issue.

#2 worked for me - both for this module and for mass_contact, which was also refusing to uninstall.
Thank you!

#1 worked for me. Running cron one time solved the issue.

Running cron still in 8.8.4 … Thanks for the hint.

#37 works best.

On an updated D8.9.6 site from 8.9.2, encountered the "Fields pending deletion" error message in trying to uninstall the Geofield module, also after deleting an unused geofield. Running cron fixed it.