![]() ![]() Updating dependencies (including require-dev) Loading composer repositories with package information ![]() See ĭrupal/captcha 1.2.0 1.3.0 The CAPTCHA module provides this feature to virtually any user facing web form on a Drupal site.ĭrupal/content_access 1.0.0-alpha3 1.0.0-alpha4 Provides flexible content access control.ĭrupal/core 9.3.9 9.4.2 Drupal is an open source content management platform powering millions of websites and applications.ĭrupal/core-composer-scaffold 9.3.9 9.4.2 A flexible Composer project scaffold builder.ĭrupal/core-recommended 9.3.9 9.4.2 Locked core dependencies require this project INSTEAD OF drupal/core.ĭrupal/image_captcha 1.2.0 1.3.0 Provides an image based CAPTCHA.ĭrupal/matomo 1.17.0 1.19.0 Adds Matomo javascript tracking code to all your site's pages.ĭrupal/metatag 1.19.0 1.21.0 Manage meta tags for all entities.ĭrupal/metatag_dc 1.19.0 1.21.0 Provides the fifteen Dublin Core Metadata Element Set 1.1 meta tags from.ĭrupal/metatag_dc_advanced 1.19.0 1.21.0 Provides forty additional meta tags from the Dublin Core Metadata Institute.ĭrupal/metatag_google_cse 1.19.0 1.21.0 Provides support for meta tags used for Google Custom Search Engine.ĭrupal/metatag_verification 1.19.0 1.21.0 Verifies ownership of a site for search engines and other services.ĭrupal/metatag_views 1.19.0 1.21.0 Provides views integration for metatags.įollowing the Drupal guide Updating Drupal core via Composer I run: $ composer update "drupal/core-*" -with-all-dependencies Warning from : Support for Composer 1 is deprecated and some packages will not be available. Only when updating to 9.4.2 I ran into a problem, caused by that missing module user_points. All the way through that process, I did not recognize that I had a blind passenger. After integrating composer into the old Drupal 8 site, I updated from latest Drupal 8 to Drupal 9.3.6 or something. The site was manually installed from a tar ball without using composer. I recently composerized a Drupal 8 site (find my detailed howto that explains how to add composer to an existing site in the Drupal docs). Let's dive into an example I encountered today. In any case, you will have to get your hands dirty and manually remove all traces of that module from your databse and/or file system. Or it might even be a module with a bad uninstall routine. It might be incompatible with your current setup or Drupal version or maybe it was a custom module that you can't get hold of. The quick solution would be to temporarily download and enable the missing module ( composer require drupal/module_name, drush en module_name), then perform the update or config import and finally uninstall and remove the unwanted module again ( drush pmu module_name, composer remove drupal/module_name).īut what if you can not simply install the module. The error message, when an import or database update fails, usually tells you, that a module or entity type is missing. Usually I run into that sort of problems when performing a Drupal update and finally run a database update drush updb or when I try to import configs drush cim. If something shows up, open the database dump in a text editor and search for the module's system name, to see which tables hold relicts of old modules. Find some screenshots further down.Īnother way - if you prefer working on the command line - to find references to missing or corrupted modules is exporting your Drupal database drush sql-dump > mysite.sql and grep for the module's name grep module_system_name mysite.sql. You can use phpMyAdmin to search through all tables of your database to find the module name. A good spot to find module leftovers are the tables You can find those abandoned modules also when you dig into your database. There might be yml files with the old module's name, or configs referring to that module. I'll tell you a "funny" story about that further down below.īut where are those leftovers hiding? You might find these relicts of old/unused modules in your config/sync/ dir. You might even drag those module relicts in your database through a major upgrade. Those module leftovers might stick around for a long time unrecognized because they often don't show up on the modules page (/admin/modules) or when running drush pml from the command line. Leftovers from modules that have not been correctly removed from a Drupal installation can cause troubles with your Drupal site in the long run. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |