- Issue created by @milovan
- πΊπΈUnited States bburg Washington D.C.
I ran into a similar error after updating drush and Drupal core. Clearing the cache/running database updates seems to have cleared it for me.
- πΊπΈUnited States Coop920
#4 also worked for me. Ran into an error and then ran update.php . No updates were made, but the error did go away. Thanks!
- πΊπΈUnited States nicxvan
I think this is related to the issue I opened that I just tagged. I think I have an idea of what is happening, I'm working on documenting it on the other ticket.
- πΊπΈUnited States japerry KVUO
The issue here is the plugins that were moved are still cached which is causing the error. The next version needs to bring back those plugins and then figure out a way to show them as deprecated so sites start using the new plugin instead.
- Status changed to Closed: duplicate
about 1 year ago 3:26pm 16 November 2023 - ππΊHungary Balu Ertl Budapest πͺπΊ
@milovan β , @bburg β , @Coop920 β please follow the updates on the related ticket: #3397227-21: Update to 3.5 replaces purge_drush but does not disable it β .