I am trying to uninstall the video module from our website (https://backup-openlab.web.cern.ch), but apparently there are multiple entities that need to be removed until I am allowed to uninstall it. In my attempt to do so, I even broke the website once, so I would be really grateful if there was someone to help me with that!
I know this reply is a few months late, but going on recent DM discussions, this might be helpful for others too.
In order to find out where the Video module is being used - which entities and in what views, you need to look at the Field List report. This can be found at reports > field list and includes 2 tabs entities and views.
Between these two tabs, you can find everywhere video is being used. I did a quick look, and for example on page 2 of entities, you’ll see field_press_coverage_video in the Press Coverage content type, and a couple of others. Of course, this is assuming the field was logically named using video, but it’s a start…
Make a note of where Video can be found, then you’d go to those content types, and delete the field.
If you want to use some media field to replace video, just make sure you have the desired video saved somewhere and noted what’s supposed to go where, you’ll then need to add it back in again later, but using a different module to generate the video_v2 field.
When done, clear caches…
As for removing a module, this is the usual operation uninstall via Extend, then physical removal via WebDav. Instructions for that all here How do I Remove Modules? | Drupal @ CERN
Good luck… ping me if you need to chat about this!
-cath
Thank you very much for the information, it proved to be very useful indeed!
I have now removed all the additional modules that were appearing in in the Field List and cleared Catches, but when trying to delete via extend/uninstall I get the following message: “Fields pending deletion”, is this perhaps a matter of time in terms of refreshing the database or it requires some other action on my end?
I am happy to jump in and help, though this also presents a great opportunity to validate the written guide on oc: https://drupal-tools.web.cern.ch/work-with-openshift-cli, if you would be up for that, @cbolanou? If you face any issues following the above, please let me know.
Thank you very much for jumping in to help! I am afraid I have no experience with Drush and thus I went ahead trying what @gmesaper kindly suggested, but I am afraid I get the following error: “The website encountered an unexpected error. Please try again later”.
I will go ahead and read the guide that Joachim kindly shared, but please do let me know in case you have any other ideas.
I can’t see the images, do you use quotes in the configuration values?, I give you a trick
goto to the export tab,
https://your_site/admin/config/development/configuration/single/export
select
under “Configuration type” select “Simple configuration”
under “Configuration name” select “field.settings”
and copy only the line purge_batch_size…
repeat the import sequence, paste the copied line, changing the value for the size
I am not using quotes, but I am afraid the import is not working. The errors appearing indicate the following: “The configuration cannot be imported because it failed validation for the following reasons:
Configuration block.block.porto_sub_474600158206763008 depends on the porto_sub theme that will not be installed after import.
Configuration block.block.porto_sub_aboutportobottom depends on the porto_sub theme that will not be installed after import.” etc.
I also took a look at the Openshift CLI, but as a very basic user I have plenty question marks on how to use it properly without potentially wrecking the website. In any case, this is not truly urgent at this point and perhaps we could take a closer look with @joachim when we take the step to migrate the website soon.
Of course, if you have any other suggestions until then they are much welcome!
I will let Guillermo get back to you on the above once possible. Thanks for the feedback on oc: We recognise that this is not the easiest (or most comfortable!) if you are not experienced with command line interfaces. If you are unable to make it work using the Drupal UI, we will just sort it together once we finalise the migration—no worries!