When a module (contrib in my case, but probably for core too) defines base fields for an entity (such a node) during uninstall, if there is data for the fields the columns are removed from shared table node_field_data and inserted into a newly cerated dedicated table (named field_deleted_data_f922eea356 in my case). This table will be purged on the next cron run, as expained in core/lib/Drupal/Core/Extension/ModuleInstaller.php uninstall()
// The module being uninstalled might have added new fields to
// existing entity types. This will add them to the deleted fields
// repository so their data will be purged on cron.
However, if you then re-install the module, and then uninstall it again, before cron has run, we get an exception
Drupal\Core\Entity\EntityStorageException: The field publish_on has already been deleted and it is in the process of being purged.
in Drupal\Core\Entity\Sql\SqlContentEntityStorageSchema->onFieldStorageDefinitionDelete()
(line 773 of core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorageSchema.php).
This is because the dedicated table field_deleted_data_f922eea356 still exists, so cannot be re-created. The function in question is onFieldStorageDefinitionDelete() in SqlContentEntityStorageSchema.php (it may be different for other db schemas).
This is a problem for admins because it leaves their site db in a broken state. Also the exception message may not necessarily been seen, and a WSOD is shown instead. This should not be an exception, because it can be caused by normal admin operations.
The original issue in the Scheduler queue is #3168730: 'The field publish_on has already been deleted' error when uninstalling →
drush sidrush en scheduler; drush -y config-set node.type.article third_party_settings.scheduler.publish_enable truedrush pmu schedulerStep 6 produces the exception
There are a number of alternative options to resolve this:
Options 1 and 2 are not good solutions. 3 and 4 are better. I did a trial implementaion of 4 and it worked fine.
Active
11.0 🔥
extension system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
My two cents, because simply running cron, either via UI or drush, can't work in some cases and fully block uninstall of the module...
Found here : https://drupal.stackexchange.com/questions/230156/how-can-you-completely...
run
drush php-eval 'field_purge_batch(1000);'
will resolve the problem in my case.