- 🇦🇺Australia dpi Perth, Australia
Same per #3071608-11: Cannot uninstall module →
Please stop re-opening closed issues.
- Status changed to Active
over 1 year ago 5:41pm 3 April 2023 - 🇫🇷France zenimagine
I have Drupal 9.5.7 and just installed this module. I created a field, which I deleted and it is impossible to get rid of this module for months.
I have this message on the uninstall page with the uninstall checkbox disabled:
"Recurring Dates Field cannot be uninstalled for the following reason:
Fields awaiting deletion"How to properly remove this module? The DEV versions have the same problem.
Please leave this open. This is a big problem and unfortunately there is no warning on the module page to indicate that it is not uninstallable.
- Status changed to Needs review
over 1 year ago 1:00pm 15 August 2023 - last update
over 1 year ago Composer require-dev failure - 🇩🇪Germany szeidler Berlin
I ran into a similar issue. It seems that the
onEntityDelete
method got called, but at a moment where the storage definition events already removed the table.I was able to workaround it by adding a check if the table exists.
It is closely related to the entity type issue, but does not seem to be the same.
- 🇮🇳India NivethaSubramaniyan
I tried the following steps and the issue was not reproducted. After deleting the field, it works fine for me.
Steps:
1) With drupal 9.5, I have added 'recurring date field' module [3.2.0].
2) Then in article content type added a field with this type recurring date field.
3) I go to uninstall page to uninstall this module.
4) It prevents me from uninstall since we are using this field. It shows the field name.
5) Then I go to the article content type and deleted the recurring date field which I have created.
6) Now again I go to uninstall page and I am able to uninstall the module.Note: To confirm whether you have deleted all the recurring date type field. Visit the page admin/reports/fields and search for Recurring dates field and find out in which content type we are using and delete it.
I have attached the screenshot for your reference.
- Status changed to Closed: duplicate
over 1 year ago 4:19am 17 August 2023 - 🇦🇺Australia dpi Perth, Australia
@szeidler I'm going to say this is not related, as that would happen during normal entity deletions. Though the table should certainly exist at that point. New issue to add these guardrails, though I don't know why this would be occurring.
@NivethaSubramaniyan thanks for confirming.
Once again, I did the same. Added field and date to two node bundles. Deleted field from both bundles. Uninstalled.
If your site is encountering this, its likely hosed in some unique fashion. Without clean steps to reproduce, or ideally a PHPUnit test, it cannot be actioned.
- 🇦🇺Australia dpi Perth, Australia
@szeidler 🐛 DateRecurOccurrences::onEntityTypeDelete makes it impossible to delete an entity type and its code at the same time Needs work may be what you want.
- 🇩🇪Germany szeidler Berlin
In my case the table exists and the module works as expected. But when deleting a date recur field and do step debugging I see that the
onEntityDelete
is triggered after the regular field storage and date recur table got removed.I so far haven't tried to reproduce it on a new installation. The site affected used date_recur for some time.
- 🇫🇷France liliplanet Cannes
#17 works, re-create your field in a content type, delete the field, then you can uninstall.
- 🇺🇦Ukraine vasyok
I have same problem
Fields pending deletion [nothing]
with date_recur version 3.4.
Upgrade to 3.6.1 fix this. Problem gone for me.