- Issue created by @jcrump@tulane.edu
- 🇺🇸United States tjhellmann Indianapolis, IN
I'm facing the same issue. @jcrump@tulane.edu, did you find a workaround?
Unfortunately, I have not.
To continue upgrading all of our sites, we decided to leave the module enabled in Drupal 10 and just remove the icon from the wysiwyg toolbar.
- 🇩🇪Germany jurgenhaas Gottmadingen
For some reason, the views module believes that the view depends on this module. Which, if anything, is an bug in the views module.
If that can't be fixed over there, then you can manually resolve this:
- Export your config
- Edit the view config entity which wrongly depends upon the wysiwyg_template module and remove that line from the dependency list
- Import that config again
- Then you should be able to disable this module
That makes sense Jurgenhaas.
However, it's just not practical when upgrading a 125+ sites, many with unique views.
I'll investigate the Views angle on the problem.
Thanks, James
I've done some more testing, and it seems like if you first do the Drupal 10 upgrade, then uninstall the module, you don't run into the View deletion.
