πŸ‡ΊπŸ‡ΈUnited States @mmrtnt

Account created on 16 December 2008, almost 16 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States mmrtnt

Adding just to share.

I had a problem with four modules (three from composer, one custom) not showing up when running config import. I could use drush to "en" them, but config imports kept failing for "Unable to install module since it does not exist"

I was able to get around this by modifying ExtensionList.php and commenting out the cache retrieval section. Apparently even after numerous composer removes, deletes and composer requires, the modules were not getting scanned and put in the module list cache.

This is on Drupal 9.4.7.

274   public function getList() {
275     if ($this->extensions !== NULL) {
276       return $this->extensions;
277     }
278     /*
279     if ($cache = $this->cache->get($this->getListCacheId())) {
280       $this->extensions = $cache->data;
281       return $this->extensions;
282     }
283     */
284     $extensions = $this->doList();
285     $this->cache->set($this->getListCacheId(), $extensions);
286     $this->extensions = $extensions;
287     return $this->extensions;
πŸ‡ΊπŸ‡ΈUnited States mmrtnt

@realityloop @varshith @fonant

Thanks!

My problem was probably caused by implementing Config Split and not having the file in the "local" config directory.

cp web/modules/contrib/search_api/config/install/search_api.settings.yml config/local/

πŸ‡ΊπŸ‡ΈUnited States mmrtnt

Can confirm. Making these changes allowed the module to install successfully.

πŸ‡ΊπŸ‡ΈUnited States mmrtnt

#12 πŸ’¬ The User ID field needs to be updated. Closed: works as designed Worked for me.

Same circumstances - upgrade from 8.9 to 9.5 to 10.2.

Thanks Joakland β†’

πŸ‡ΊπŸ‡ΈUnited States mmrtnt

34 πŸ’¬ Cannot update database because 'module is too old' Postponed: needs info Worked for me.

I've been slowly dragging this upgrade from 8.9 to 10.2, solving things along the way. The error I was getting was "drupal 10 Cannot update database because [modules] are too old"

I plugged all the "post_update" messages into the eval and it was finally successful.

Thanks Pragna β†’

πŸ‡ΊπŸ‡ΈUnited States mmrtnt

Same issue.  I struggled with this for a day.  I don't think I would have found it on my own.  MUCH THANKS!

πŸ‡ΊπŸ‡ΈUnited States mmrtnt

I just encountered this today - not in Olivera, in an override in a Bartik sub-theme - after upgrading from Drupal 8.9 to 9.5.11.

Here's what I did to resolve it, in case someone else lands here after running into it while upgrading:

  • Replace core/Bartik with contrib/Bartik
  • Upgrade drupal/views_infinite_scroll to ^2.0 in Composer
Production build 0.71.5 2024