How to fix "The following module is missing from the file system..." warning messages

If you see a PHP warning such as "The following module is missing from the file system..." (or similar) on your site, this page explains how to fix it.

The warning was introduced in Drupal 7.50 and is displayed when Drupal is attempting to find a module or theme in the file system, but either cannot find it or does not find it in the expected place. Usually this indicates a problem with your site. It is not a major problem, but one which should ideally be fixed if possible. (See the change record for more information on why this warning was added, and these instructions for how to ensure that warning messages like this one are never displayed to your site's end users, but rather only recorded in the administrative logs.)

Note that the problem or inconsistency on your site, which is now causing this warning, might have been existing for a long time already, without any visible symptoms. The introduction of the warning message in Drupal 7.50 does make it visible.

There are a few possible causes and corresponding solutions.

You removed a module from the file system without disabling and uninstalling it

Possible solutions:

Restore the module and actually disable and uninstall it (recommended if possible): First, restore the module to its original location in the file system. Then either go to the Modules page and disable/uninstall it from there, or use Drush (drush dis module_name && drush pm-uninstall module_name, where module_name should be replaced with the name of the module).
Manually remove all traces of the module in the database. This is not the recommended solution because many modules do important cleanup tasks during the disable/uninstall process, and this solution will result in those being skipped. In many cases it will mean that the module will be broken if an attempt is ever made to use it again on this site. However if you decide to use this solution (e.g. for obsolete modules that do not even exist anymore and that can never be added back), it can be done in several ways. Here are some examples:
- Drupal 7
  1. Use the point-and-click, administrative interface provided by drupal.org contrib modules.
    Option #1 - Module Missing Message Fixer
    Option #2 - Missing Module
  2. Use Drush
    For example, run a command similar to the following:
```
drush sql-query "DELETE from system where type = 'module' AND name IN ('old_module1','old_module2');"
```
    When done, clear the site's caches (e.g. drush cc all).
  3. Write an update hook in a custom module
    You can use code similar to the example below, which will remove the missing modules when update.php is run:
```
/**
 * Delete {system} records for long-lost modules.
 */
function MYMODULE_update_7100() {
  $modules = array(
    'old_module1',
    'old_module2',
    'old_module3',
  );
  db_delete('system')
    ->condition('name', $modules, 'IN')
    ->condition('type', 'module')
    ->execute();
}
```
- Drupal 8/9
  1. Enable devel module and on the administrative interface go to /devel/config, edit core.extension delete missing module entry.
  2. Use the point-and-click, administrative interface provided by drupal.org contrib modules.
    Option #1 - Module Missing Message Fixer
  3. Use Drush
    drush sql-query "DELETE FROM key_value WHERE collection='system.schema' AND name='module_name';"
    When done, clear the site's caches (e.g. drush cr).
    Also make sure that the CMI folder is cleansed of the broken uninstalled module. There may be some yml files left over and / or some system config. (this is all not the best way to do things as a FYI. However with Drupal 8 being so young, things don't go as planned always).
  4. Write an update hook in a custom module
    You can use code similar to the example below, which will remove the missing modules when update.php is run:
```
/**
 * Fix long lost modules are missing from the filesystem.
 */
function MYMODULE_update_8100(&$sandbox) {
  $modules = [
    'old_module1',
    'old_module2',
    'old_module3',
  ];
  \Drupal::database()->delete('key_value')
    ->condition('collection', 'system.schema')
    ->condition('name', $modules, 'IN')
    ->execute();
}
```

You moved the module inside your Drupal installation

Possible solutions:

Clear the site's caches so the new location of the module is registered. Or,
Restart the server, since Apache may cache paths. Or,
Move the module back to its original location in the file system.

Since Apache APC caches paths, Drupal may still try to find the module at the old location, even after clearing caches. If you don't have control over Apache on shared hosting, try uncommenting the $settings['class_loader_auto_detect'] = FALSE; string in settings.php, which disables APC cache detection, and clear caches.

Leftover fields or other configuration entries

There could be a leftover field or other configuration entry that depends on the missing module, and was not properly deleted or cleaned up when the module was disabled or uninstalled.

See e.g. #2820939: field_read_fields() does not check whether a module is disabled or missing.

To find out more, you need to get a stack trace, and find out from where the code that triggered the error was called.

You can then open an issue on in the respective project's issue queue, or post a comment on this page, to help document such cases, improve error reporting, and finally fix them for good.

Sometimes leftover items can be cleaned up with cron or cache clearing, but this really depends.

Formally, an unsuccessful uninstall does qualify as a bug - so also read the section below.

Obsolete modules existed from a previous Drupal version

A Drupal site that was upgraded from Drupal 6 to Drupal 7 may also display warnings about modules that were active in Drupal 6 but were disabled before the upgrade. These can only be cleaned up by one of the systems table solutions above.

Example: modules such as imagecache_ui, imageapi, filefield, optionwidgets, and imagefield which were made obsolete by Drupal 7 versions may still exist in the system table.

Your installation profile driven site has a "missing" module that won't go away? Check the info file.

If you've removed a module from an installation profile's codebase, and you've removed the entries from the system table with a missing module solution, but you still have modules showing up, check the profile's info file. Make sure that the "missing" module has been removed from your installation profile's .info file (usually as a dependency).

There is a bug in a module installed on your site

The final possibility is that there is code on your site which is accidentally telling Drupal to search for a file that doesn't exist. This could be because of a typo in the code (where it is searching for an incorrect module name), or because the code is deliberately checking for a nonexistent file but did not update in response to this change record.

If this appears to be the issue, try to figure out what code is causing the problem (it will usually be code that calls module_load_include(), drupal_get_path(), drupal_get_filename(), or similar functions. If the offending code is in Drupal core or a contributed module, file a bug report in the appropriate issue queue on Drupal.org.

Try to produce a stack trace to find out where the problem originates.

When a path is being mistaken for a module look for cases where the path might be given as a module. For example:

/**
 * Implements hook_views_api().
 */
function example_views_api() {
  return array(
    'api'  => 3,
    'path' => drupal_get_path('module', 'example/views'),
  );
}

when it should be

/**
 * Implements hook_views_api().
 */
function example_views_api() {
  return array(
    'api'  => 3,
    'path' => drupal_get_path('module', 'example') . '/views',
  );
}

Problems with hook_system_info_alter() calling other hooks

Some (contrib) modules use hook_system_info_alter() to change the data scanned from modules' *.info files. At the time that this hook is invoked, the module info data is being rebuilt, but an old, possibly outdated and inaccurate, version of this data is still in the database.

Some of these implementations of hook_system_info_alter() directly or indirectly invoke other hooks, which uses the old module info data still in the database. This can cause a warning "The following module has moved within the file system", or possibly "The following module is missing from the file system".

Most of the time this does not cause any real problems. But the warnings can be confusing and annoying.

As said above, this should be discussed in the issue queue of the respective module.

Comments

Wow. What a shitty feature

crystaldawn commented 8 July 2016 at 04:27

Wow. What a shitty warning to add by default. I just had like 20+ modules request to be resurrected from the grave.... on 1 site of 100's. #notcool This should not be a feature that is enabled by default and should instead only be used during a cleaning phase of a site and enabled manually, not automagically.

You can (and should) disable

geerlingguy commented 8 July 2016 at 04:39

You can (and should) disable warning display to end users on production sites, so this should hopefully only impact the backend/logging/development environments—see the change record for more information.

The thing is, this is exposing a lurking evil that caused a lot of problems for a lot of Drupal sites—but which in the past has been hard to diagnose. So it's better for the problem to be exposed (so you can fix it) rather than let it linger until it starts causing real performance regressions.

I had two of a dozen or so sites end up with a few of these warnings, and I followed the advice on this page to either place the module back in the codebase and uninstall, or in some cases run a SQL query to delete the errant/old record from the system table.

__________________
Personal site: www.jeffgeerling.com

Yea I get the idea behind it

crystaldawn commented 8 July 2016 at 04:59

Yea I get the idea behind it but this is going to cause my phone to start ringing off the hook when people start panicking thinking that someone deleted something from their website. I always uninstall modules, but this is going to bring back modules from the dead that were from before my time and may even start people blaming ME for these missing things and thats not nice. I hate damage control for these sorts of things. Clients are not going to understand it.

It seems like such a large hammer thats only going to result in nano-seconds in performance increases for 95% of most sites who only have a few modules that were removed without an uninstall process. The average drupal site isnt missing 1000's of modules :/

#hidethephone

Thing is: we are not

jeroen.b commented 10 July 2016 at 16:34

Thing is: we are not talking nanoseconds here. It would scan your whole Drupal directory looking for the module. Depending on the server/disk speed and size of the website this can take a long time. In some cases it will even do this on every page request

I dont know what century you

crystaldawn commented 10 July 2016 at 16:48

I dont know what century you are living in, but in my century, scanning a dir of even 10000 files takes milliseconds. SSD makes them even faster, so yes, nano-seconds is the correct term here. Unless of course you're still using that old C-64 with a 5.25" floppy. Then by all means, this is a great feature! ;) Please brush up on your hardware technology before speaking again. Thanks. Besides, this thread speaks volumes about how terrible of an idea it was so no need to take my word for it, there are plenty of others to chime in with the same opinion ;) Hopefully it gets reverted/changed to manual drush switches only in the next release. It makes zero sense to not have a drush switch for it at the very least.

crystaldawn, sure, a single

jeroen.b commented 10 July 2016 at 17:12

crystaldawn, sure, a single file scan does not matter that much. However, when you have a website with many visitors and it would scan your full Drupal directory for the module on every page request, it could kill your website.

I hope I can change your mind. Please read my blog about it or the full issue about it.

I understand the whole

crystaldawn commented 10 July 2016 at 17:24

I understand the whole concept behind why this should be done, but that isnt really the problem here. The problem is the UI/UX and the way it's being forced upon others that dont have a clue what drush is let alone have the skill to fix any of it. I agree with you that it can improve performance but in my opinion that performance gain is so minuscule that it really shouldnt be displayed this prominently either in drush nor as a warning when warnings are enabled (like a dev site that a client would see during QA). No mind changing required that this is a good thing to have, but it clearly was not vetted well enough before it was added to core. Especially when there is a contrib module that already does this......... BETTER than core does.

That contrib module is not

jeroen.b commented 10 July 2016 at 17:36

That contrib module is not the same as the core change, please check what was actually changed.
Bu yes, I get your UX point. If you want to improve it, please open up a new core issue so we can continue the discussion.

Like I said, some contrib

crystaldawn commented 10 July 2016 at 17:41

Like I said, some contrib modules are CHANGED slightly to fit in core once they are pulled in. The way the two do the actual detection is different, but the end result is the same. Thus, that module should have been modified, pulled into core, and marked as depreciated after 7.50. That way users of that module will know that they can safely get rid of it once they hit 7.50. It has quite a few installed instances already. This would have given core a much better UI/UX right out of the gate and it would notify users who are already aware of this issue that core now does this already and that the module is no longer necessary after 7.50. See how that works? Like a nice well oiled machine :)

Again: please check what is

jeroen.b commented 10 July 2016 at 17:49

Again: please check what is changed. There are enough cases that can only be detected by this being inside bootstrap, I'm not just talking about missing modules.
Anyway, this discussion ends here for me. The committed change was a community effort with quite some people that took multiple years to land in core, we clearly missed your opinion in there. So please, if you want something changed, open a new core issue. If you link to it from #1081266: Avoid re-scanning module directory when a filename or a module is missing you can get all those people involved.

Maybe you were not part of

crystaldawn commented 10 July 2016 at 17:55

Maybe you were not part of adding Views or CCK to Drupal, but where the detection/functionality takes place is completely irrelevant to the feature/problem that it's solving. Those 2 examples were certainly modified before being brought into core, this problem should have been absolutely no different. That is why I said that modules are often modified before being brought into core because they can do their job better when lower in the bootstrap, something a contrib module simply cannot do.

Slow filesystems are not a thing of the past.

premium-ben commented 16 August 2016 at 08:37

Regarding the time taken to scan the filesystem, it can be significant - if you're developing on a folder shared with a vagrant/virtualbox instance like I am, a missing module can easily change every page load from 1-5 seconds way up to 30-40 seconds.

Thing is, filesystem times aren't the issue - a developer should be on top of these things and keep things clean between, say, changing branches, by disabling unused modules. You can even do this in one pass with a combination of git hooks and the drush clean-modules project.

The more warnings exposed to the back end (in the logs, not to the CMS editors) the better in a system like Drupal where everything's written by different people with different opinions on what constitutes good code.

I just edited the

David_Rothstein commented 8 July 2016 at 14:29

I just edited the documentation now to add a more prominent link to the change record, and also a link to instructions for disabling the display of warning messages to end users.

same problem

Misterloup commented 8 July 2016 at 05:31

hello
i have the sameproblem with all my modules..
i got this message (with each module..): "User warning : The following module is missing from the file system: content. In order to fix this, put the module back in its original location. For more information, see the documentation page. dans _drupal_trigger_error_with_delayed_logging() (ligne 1128 dans /home/vetosent/www/includes/bootstrap.inc)."

i have changed the file "include/boostrap.inc" with the older of drupal core 7.44 and the problem deasapered , excepted that in the admin menu it says drupal core 7.44,; when i go in the section of the updates the drupal core is 7.50

now, i changed the name in this file (include/boostrap.inc 7.44) from drupal 7.44 to drupal 7.50 and all is ok...
but for the next changes, i think the problem will repeat ..

so, what can i do ?
thank you

Agree with this

droddis commented 8 July 2016 at 12:51

I actually think this is a good feature. Certainly my skills have improved over time with regards to best practices on certain sites. this helps find residual issues with my less appropriate behavior on older sites.

Some modules are problematic

uno commented 8 July 2016 at 13:49

Some modules, such as TVI, has being reported as missing, uninstall changes nothing.
Also, some of the modules that were used on D6, prior to D7 upgrade, are still included in this error report, and, on those sites, list is very, very long.

--
... I mind

I am with you and I'm also backing this new so called feature

manyk commented 11 July 2016 at 10:19

You are right @droddis. This is a very good change!

Who doesn't like it should go back and provide support and work with other CMSs. For most of them there is no tell if a module is bad or good and you have to dig and test for weeks to find out what is slowing down a site. This new feature is going to save us nights of tinkering. Who is complaining should stop and go earn their pay. We're suppose to be professionals and our customers are expecting that when you offer them your expertise and support for their drupal project.

Agree, really dumb "feature".

pixelsnap commented 24 July 2016 at 14:20

Instead of issuing a warning (as it seems to do when running update.php as well), it should simply check to see if the module is activated and if not, clean up the tables. Period.

Isn't putting the database tables in order already the very reason why we run that update.php in the first place?

Rather than makes rules and warnings, come up with solutions. Drupal is already complicated, heavy and convoluted enough as it is.

I agree

CM63 commented 24 July 2016 at 14:52

I completely agree, Drupal could do the work after asking confirmation to the user. You may want to submit that to the bug tracker or development.

Saner than sending people

pixelsnap commented 24 July 2016 at 15:10

Saner than sending people editing db tables manually, for sure. The "update.php" process already is in there adjusting tables, so it's kinda dumb not to be fixing this sort of thing as well. Or there could be an option added to the "Performance" page, to "optimize tables" or something of that sort.

+1

travisc commented 30 September 2016 at 16:07

Agree

Drew Oslo commented 15 August 2016 at 23:59

Great example of why Drupal is doomed to failure. No thought at all to dumping this error message and impossible fix on the thousands of non-developers that manage Drupal sites. Then force them to scour message boards and try to come up with a way to 'fix' sites that were never broken.

Is Drupal doomed, or are you?

chowdah commented 9 October 2016 at 16:24

Do you know how many times I've read this kind of drivel? Drupal is used worldwide and has a great community behind it. This added functionality is telling you, the site manager, that there is a problem that could turn into a bigger one. I suggest you join the community, learn about the tool you are using and quit the sniping from the sidelines. It's part of your job as a site 'manager'.

this comment did not age well

StevenPatz

he/him

English

Alexandria VA

commented 23 April 2020 at 16:07

this comment did not age well

Actually this is an awesome feature!

chowdah commented 9 October 2016 at 15:43

I migrated a pretty complex D6 site to D7 in 2014, and have been discovering bits and pieces of the old D6 site in the DB as I've continued to keep content flowing through the upgraded site. This really helped me clean up the system table! There were 77 stale module entries in that table left over from the D6 installation!

After doing the cleanup using drush, I've also noticed a slight MySQL performance bump.

If you have hundreds of sites to fix, you should use the module http://drupal.org/project/module_missing_message_fixer or fix it with drush or directly through MySQL. Leaving the entries in the table will only cause you problems in the future.

Removing Warning

jimweber commented 8 July 2016 at 13:38

The site has been working perfectly for years. Now this warning. Need a much simpler solution to remove this distraction. I can not restore the module because I cannot find it on the Drupal website.

Use the method under "Remove

jeroen.b commented 10 July 2016 at 16:49

Use the method under "Remove all traces of the module manually using SQL (in drush sql-cli, phpMyAdmin or with the mysql command): This can be done, for example, with a Drush command similar to the following:"

Jer, the command is missing.

crystaldawn commented 10 July 2016 at 17:03

Jer, the command is missing. I'll finish it for ya:

drush sql-query "DELETE from system where name='module_name' AND type = 'module';"

I know that is what you were trying to say. But a better response is probably this: Refer to the top of this page, there is no 1 singular way to fix this issue. Maybe this module as well if you dont know how to use command line, phpmyadmin, etc: https://www.drupal.org/project/missing_module

Cmon Jeroen, you're slackin in the wheaties dept today with your responses :D

Is it that weird to think

jeroen.b commented 10 July 2016 at 17:13

Is it that weird to think people actually read this page before commenting? ;)

Contrib modules that help clean this up?

David_Rothstein commented 8 July 2016 at 14:38

Anyone know of any good contrib modules that help fix these problems (e.g. by providing a user interface to help do so)? If so we might consider recommending them in the main documentation.

I found a couple:
https://www.drupal.org/project/missing_module (administrative interface and Drush command)
https://www.drupal.org/project/clean_missing_modules (just a Drush command)

But I haven't tried either of them and I'm not sure they provide a comprehensive fix.

With Drupal 7.50, I guess a module that dealt with this comprehensively would (a) respond to hook_watchdog(), (b) examine the messages that come in, and (c) recommend appropriate actions depending on whether the message says the module is moved/missing, and if it's missing, whether or not it's present in the {system} table in the database.

I tried running both of those

geerlingguy commented 8 July 2016 at 15:59

I tried running both of those on a really old site (upgraded from 5->6->7) and it didn't fix all the modules that were reported as missing, like throttle, upload, content, cleanfeeds, diggthis, etc.—I'm not sure if those modules were never uninstalled correctly or what, but they still existed in the system table. I just tossed in a bunch of SQL commands to delete those entries.

__________________
Personal site: www.jeffgeerling.com

https://www.drupal.org

uno commented 8 July 2016 at 17:22

https://www.drupal.org/project/missing_module does nothing for me, in status report "Check for missing modules in filesystem - No missing modules detected." - all is green, but when I run update.php my whole screen lights up in red :)

--
... I mind

Maybe https://www.drupal.org

stefan.r commented 19 July 2016 at 13:07

Maybe https://www.drupal.org/project/module_missing_message_fixer?

contrib modules that help clean this up

joseph.olstad

French

commented 2 August 2016 at 15:14

Here's a sandbox project I pieced together that does just that:

Download this module cleanup_tool

Then extract it to your sites/all/modules folder

and run these drush commands.

drush en cleanup_tool -y;
drush cc drush;
drush cu-check;#check which modules need cleaning
drush cu-clean all --update_option=all -y; #cleanup all of them
drush dis cleanup_tool -y; #disable the cleanup_tool module
drush pm-uninstall cleanup_tool -y; #uninstall the cleanup_tool module

2 modules already

labboy0276 commented 2 August 2016 at 15:22

Hey Thanks, but there are 2 modules already:

https://www.drupal.org/project/module_missing_message_fixer
https://www.drupal.org/project/missing_module

The first is the one I made and there is a patch for drush integrations here:
https://www.drupal.org/node/2770115

Is yours any different?

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

A gem!

pixelsnap commented 2 August 2016 at 16:16

This script's nifty handiwork should of course simply be part of the update.php script/process BUT it is a gem, just as it is. The proof that the most useful code doesn't always have to be complicated.

A site I took over had long ago used the "calendar ical" module, probably in some kind of testing, then it was never properly "uninstalled" on the modules page... The module is now deprecated and I looked all over the place for that "old" version -- even wrote to the developer, who never bothered to reply -- just so that I could simply put it back in the folder, then uninstall it, etc. etc.

A lot of BS which could have been avoided without that dumb "novel idea" in 7.50, which should come with a way of cleaning the "problem". None of us would walk into someone else's house and point out all that's wrong without a way of making things better, now, would we? ;-)

Thanks for a module that really does the job. Perfect.

Thanks for this

jdhildeb commented 23 August 2016 at 17:02

Thanks @joseph.olstad. Your module saved me a lot of time, since a site I inherited had 70 missing modules.

Thanks joseph.olstad!

HopPhrog commented 16 December 2016 at 19:51

Your cleanup_tool worked great! :)

Works but generates an error on every invocation

voipfc commented 27 December 2016 at 03:19

On my system which is a 64 bit Jessie running PHP 5.6.24, running the command gives the error

Object of class stdClass could not be converted to string syslog.module:115

after running the command. It clears out one entry and halts so I had to use the missing modules fixer module to get the number of missing modules then run it repeatedly via bash.

for i in {1..70}; do drush cu-clean all --update_option=all -y; done

The syslog.module may contain some code which conflicts with it.
Thanks all the same.

I agree - a total gem

dawnbuie commented 28 February 2018 at 17:23

thank you - that worked perfectly for many old module entries.

7.50: not a good move...

interdruper commented 8 July 2016 at 14:41

Usually this indicates a problem with your site

Many customers picking up the phone and asking what the hell means this warning and where were the 7.45-7.49 updates...

And which are the real benefits from this warning? Remember to everybody that someone someday did something wrong uninstalling a module or installing a misspelled one? What is the real-word benefit of this?

See https://www.drupal.org

David_Rothstein commented 8 July 2016 at 15:24

See https://www.drupal.org/blog/drupal-7-50 for more information.

If the warnings are frequent, then the site had a potentially significant performance problem before 7.50. 7.50 deals with the performance problem for the most part (which makes the warnings less important than they would have been retroactively), but it's still there to some extent.

Bottom line: Just like any other warning, this condition indicates something is wrong with the site. It's not necessarily something major that is wrong, which is why it's a warning rather than an error. On a typical Drupal site with a variety of contrib modules installed, there are a number of warnings/notices which are in the logs.... just like any of the others, you can ignore this one if you want to, or try to fix the problem which is indicated by it.

I think that most of the

interdruper commented 8 July 2016 at 16:20

I think that most of the warnings are not due to missing enabled modules (this effectively would affect performance), since drush_missing_modules cannot catch them. They are due to disabled modules that never were properly uninstalled, leaving orphaned rows in the system table... ok, some wasted bytes in the database, but not enough reason to trigger a warning (and an additional problem to solve), IMHO.

Obviously this can be a symptom of wasted resources (tables and variables) left by the not-properly uninstalled modules (a good discussion about it can be found here: http://drupal.stackexchange.com/questions/22/do-non-enabled-drupal-modul...), perhaps by deceased custom or contrib modules, so any cleaning should be done manually anyway.

IMHO, all this stuff should be handle by some contrib module (for those interested in doing the cleanup), not by the core on each 'drush updb' command.

Couldnt agree more. The

crystaldawn commented 9 July 2016 at 04:19

Couldnt agree more. The performance gains that this is going to provide are negligible to 95% or more of drupal sites. It's going to cause more problems than it fixes as evident in this now quite lengthy thread. I had no idea it would get this long but it doesnt surprise me either considering the boneheadery that it is. Just wait for the flood of people who attempt to install old modules that are known to screw sites up and that then take down their entire site and really screw things up. All in an attempt to fix something that really doesnt need fixing to begin with.

Hmmm, but won't this warning

Jeff Burnz commented 9 July 2016 at 14:42

Hmmm, but won't this warning trigger on module_exists()?

Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.

Calling module_exists('some

David_Rothstein commented 9 July 2016 at 14:55

Calling module_exists('some_module_that_does_not_exist') does not produce a warning for me on Drupal 7.50.

there are a number of warnings

CM63 commented 10 July 2016 at 17:50

Hello,

No, until now, before this 7.50, there were not "a number of warnings", till this release , there is this one.. and might not have.

That sounds good in theory,

JakeRogers commented 22 September 2016 at 22:45

That sounds good in theory, but after removing referencing lines in "system" table to my themes, running "MissingModuleFixer", modifying bootstrap.inc, etc...what does one do when none of this removes the error which references a module problem yet lists themes? I really don't know why this has to be so difficult. What good is an error when we can't figure out what/where the error is? Please FIX this in 7.51!!!!!!!

Jake

There's probably a reference

pendaco commented 26 September 2016 at 07:14

There's probably a reference in your theme to a missing module. You should search the contents of your theme's files for the following function names;

module_load_include(), drupal_get_path(), drupal_get_filename()

(on linux/mac it's a bit easier to search within a bunch of files compared to windows)

Maybe Omega?

juankvillegas commented 26 September 2016 at 13:34

If you are using Omega, you could check the patch in this Omega issue (comment #13).

Juan Villegas
micoworker
Diseño y Desarrollo Web

Thanks!

aschiwi commented 8 December 2016 at 13:51

@juankvillegas: Thanks for posting this here, helped me!

Works

ngocketit commented 12 April 2017 at 19:51

Thanks for this!

I have this error message for

april26 commented 11 July 2016 at 07:00

I have this error message for a dozen Commerce modules.

This Drupal 7 site has never had any commerce modules of ANY kind stored in the modules folder, never mind installed and then not uninstalled. I think there is a problem with v7.50.

(I tried a second website that is almost a vanilla D7 installation with minimal added modules, and it does the same thing.)

The full set of errors is:

User warning: The following module is missing from the file system: commerce_cart. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_checkout. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_customer. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_file. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_line_item. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_order. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_payment. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_price. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_product. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_tax. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).

UPDATE 1

Both these sites use the AT-Commerce and AT-Core themes. Perhaps the theme (and not a module) is loading something? If so, you have to be aware of missing theme files and not only modules?

UPDATE 2

The at-commerce/template.php file has code (line 228)

$cart_theme = drupal_get_path('module', 'commerce_cart') . '/theme/commerce_cart.theme.css';

line 235

$checkout_base  = drupal_get_path('module', 'commerce_checkout') . '/theme/commerce_checkout.base.css';

line 252

$customer_admin = drupal_get_path('module', 'commerce_customer') . '/theme/commerce_customer.admin.css';

Is there a chance that the theme is causing the errors?

UPDATE 3

It turns out to be the theme causing the error and I have by-passed the problem by adding an "if (module_exists('commerce_...') before each "drupal_get_path". It isn't the right way to solve it and the theme developer is kindly working on a more elegant solution.

I think it is one of the more popular themes - AT-Commerce.

Don't assume the error is in a module - it could be any function in a theme also.

There are 10 kinds of people in the world, those who understand binary and those who don't!
InterComm South Africa (www.intercomm.co.za)

Ready the problem

amtuam commented 8 July 2016 at 18:33

.../admin/config/development/logging AND none. Ready

deleted

april26 commented 9 July 2016 at 07:37

deleted

There are 10 kinds of people in the world, those who understand binary and those who don't!
InterComm South Africa (www.intercomm.co.za)

Is it some theme?

CM63 commented 10 July 2016 at 17:54

To get the response, just do the following:
- set an other theme in your site,
- uninstall the former theme, and remove it
- and see if the problem still exists

Yes, this was a theme issue.

toamit commented 11 July 2016 at 17:57

Yes, this was a theme issue. I had submitted a patch to this theme which was doing several other bad check checks and causing performance degradation.
https://www.drupal.org/node/2406089 This patch was included and rolled into new release.

You should upgrade your theme to latest version to avoid this problem.

I too had this issue, but

wOOge commented 16 August 2016 at 13:38

I too had this issue, but turns out the inline_entity_form module was causing it.

--
wOOge | adrianjean.ca

commerce module missing but can't find out why

roderickgadellaabsl commented 11 October 2016 at 09:30

I'm also seeing warnings about the commerce module.

I tried the Missing Module Fixer, searched through my MySQL database and searched the entire drupal folder for the word 'commerce' but I can't find any calls to the module except module_exists('commerce') (from the MetaTag module) and as far as I know that should be fine.

Weirdest thing is it only seems to show the warnings when I clear the cache (or run update.php but that probably triggers clear cache..?)

User warning: The following module is missing from the file system: commerce_line_item. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (regel 1128 van D:\Working\www\boekwijzer-prod\www\includes\bootstrap.inc).
User warning: The following module is missing from the file system: commerce_price. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (regel 1128 van D:\Working\www\boekwijzer-prod\www\includes\bootstrap.inc).
User warning: The following module is missing from the file system: commerce_customer. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (regel 1128 van D:\Working\www\boekwijzer-prod\www\includes\bootstrap.inc).
User warning: The following module is missing from the file system: commerce_product_reference. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (regel 1128 van D:\Working\www\boekwijzer-prod\www\includes\bootstrap.inc).

Solved

Alex Malkov

Russian

St.Petersburg

commented 21 October 2016 at 11:28

I had the same error. The problem was solved I upgraded the AT Commerce module from version 7.x-3.0 to version 7.x-3.2.
See issue https://www.drupal.org/node/2763315

Same thing happened to me

alarez commented 8 July 2016 at 17:13

Same thing happened to me after moving my site from Pantheon environment.

One of the errors was:
User warning: The following module is missing from the file system: pantheon_api. In order to fix this, put the module back in its original location. For more information.

The command you provided fixed the issue for me:
drush sql-query "DELETE from system where name='pantheon_api' AND type = 'module';"

Thank you!

Ready the problem

amtuam commented 8 July 2016 at 18:38

.../admin/config/development/logging AND none. Ready

It is a good way to clean out garbage

bobburns commented 8 July 2016 at 18:55

It may be a pain . . . but using phpMyAdmin - you can go to the system table and delete the affected rows

Back up first of course

In my case moving modules to the sites/all/modules folder left this garbage behind and after upgrading to Drupal 7 from Drupal 6

Make sure the first column after the "module" column is "0" meaning it is a disabled module

Which one is the content-module?

William H. Olesen commented 8 July 2016 at 19:32

I managed to remove errors caused by a couple of submodules in "VB to Drupal", which I somehow must have managed not to uninstall correctly. Installed and uninstalled the module again - that fixed the problem.

However, I still get an error concerning a "Content"-module:

"User warning: The following module is missing from the file system: content. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/vhosts/enigma.williamolesen.dk/httpdocs/includes/bootstrap.inc)."

I can't seem to find it when looking/searching in the DB in Phpmyadmin, as suggested elsewhere.

The previously mentioned Find/Clean missing modules-modules can't find Content either.

Anyone else experiencing this particular problem?

Sounds like a leftover from cck 6

bobburns commented 8 July 2016 at 20:45

"Content" (module) . . . sounds like a leftover from cck 6 - check the system table closely

No luck

William H. Olesen commented 8 July 2016 at 22:20

The site was started on Drupal 7 and I didn't recall ever having installed CCK, but I installed it anyway and uninstalled it - no success.

I have been going through the System-table very carefully and searched for "content" in the DB, but no luck. No sole module named just "content".

Same here

scareyclott commented 9 July 2016 at 09:34

I have got rid of all the others by re install or php myadmin command but cant find 'content' anywhere?

Scott

Me also

mr.barneylodge@gmail.com commented 10 July 2016 at 20:43

I too cannot track down the content module

Still looking

scareyclott commented 10 July 2016 at 22:29

I'm still looking mrbarneylodge. Curious one, must be something, somewhere or it wouldn't be getting picked up

Temporary fix

mr.barneylodge@gmail.com commented 11 July 2016 at 05:12

I have used the disable messages module and used the expression below to disable this particular message

^.*The following module is missing from the file system.+content.+.*\.

That works for now

scareyclott commented 11 July 2016 at 07:37

Thanks mrbarneylodge that has worked for now

Module loading core include

misjao commented 12 July 2016 at 08:15

We've had the same problem, it was one of our custom modules, loading a file from core:

module_load_include('inc', 'content', 'includes/password');

Yes, me too! Just spent

JCL324

he/him

English

Portland, OR

commented 6 October 2016 at 23:28

Yes, me too! Just spent several hours debugging and found it was a module_load_include() call with a file that had been removed. So it's not all just database issues.

JCL

A likely candidate is

caspianroach commented 13 July 2016 at 05:37

A likely candidate is Ubercart. See https://www.drupal.org/node/2763555

Yes! Thank you thank you

liezie_D commented 24 August 2016 at 12:06

Yes! Thank you thank you thank you!
Upgrading ubercart resolved the issue for me.

I have upgrate 4 site to 7.50

lykkebjerg commented 8 July 2016 at 21:01

I have upgrate 4 site to 7.50 2 site is start to ask after views export but it whase fixt after system update but to site i get this error liste. I will wait whit the last 170 site.

I maby have 1-2 site i have removed a module before uninstall so slease make a fix for this.

User warning: The following module is missing from the file system: ad_views. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: botcha. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: content. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: elysia_cron. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: emfield. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: emimage. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: fieldgroup. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: media_image_flotsam. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).
User warning: The following module is missing from the file system: remember_me. In order to fix this, put the module back in its original location. For more information, see the documentation page. i _drupal_trigger_error_with_delayed_logging() (linje 1128 af /var/www/clients/client8/web108/web/includes/bootstrap.inc).

How did you delete the

joshbgosh10592 commented 9 July 2016 at 17:06

How did you delete the affected row? Everything in there looks like I really shouldn't touch it...

Sorry wrong place

carlodimartino commented 11 July 2016 at 11:03

Sorry wrong place

Works!

carlodimartino commented 11 July 2016 at 11:04

Thanks. Works well. I had a lot of warnings on a site that had been upgraded from D6. All fixed by searching and deleting the rows in the `system` table.

Issue on very old site

hruodland commented 9 July 2016 at 10:53

I have quite an old site, originally on Drupal 4, and modules reported missing include several that I believe were formerly in core, including archive, drupal, page, and story (likely some others as well, although I didn't look to see what core included back then). If others notice the same thing the upgrade procedure between versions of Drupal may not always have removed everything it should have.

I should mention that the DELETE from system where name='module_name' AND type = 'module'; form of command got ride of all the error messages.

No way to know which module

tgeller commented 8 July 2016 at 22:28

So here's part of the error I'm getting:

User warning: The following module is missing from the file system: relation_endpoint. In order to fix this, put the module back in its original location.

Uhh... *what* module? There's none called relation_endpoint, and (AFAICS) no way to figure out which module, current or passed, it belongs to.

I have to agree with earlier statements: This error message needs work, or should be tossed out. It causes more harm than good.

---
Tom Geller * tomgeller.com * Oberlin, Ohio
See my lynda.com videos about Drupal

Tip

tgeller commented 8 July 2016 at 22:31

Having said that, the following SQL line worked:

DELETE from system where name='relation_endpoint' AND type = 'module';

BUT! If you do that while the module's still installed, you're screwed.

So again -- bad error message, no donut.

---
Tom Geller * tomgeller.com * Oberlin, Ohio
See my lynda.com videos about Drupal

But not everytime though

William H. Olesen commented 8 July 2016 at 23:01

I tried doing the same thing with the problem I'm having.

I did:

DELETE from system where name='content' AND type = 'module';

But there simply is no "content" module or submodule to be found.

So I totally agree that this error message needs some work.

The problem has no measureable effect on my site otherwise, but nobody likes red messages on their Status report :)

So, this helped one error for

joshbgosh10592 commented 9 July 2016 at 18:48

So, this helped one error for me, for "admin_theme", but I'm now having an error below. I thought Date was core? Wouldn't deleting that row kill core?
User warning: The following module is missing from the file system: date. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1229 of /home/irwin/www/www/includes/bootstrap.inc).

The "system" table isn't the only one

nullkernel commented 3 August 2016 at 00:48

I kept getting this error message for "relation_endpoint" - even after deleting from the "system" table. Turns out there were a couple of entries left over in field_config and field_config_instance. I didn't know that entries in those tables could cause this error to be triggered.

Running the following commands allowed me to finally get rid of the error.

drush sqlq "DELETE FROM field_config WHERE module = 'relation_endpoint';";
drush sqlq "DELETE FROM field_config_instance WHERE data LIKE '%relation_endpoint%'";

Thx! Had the same problem and

dystopianblue commented 5 August 2016 at 14:15

Thx! Had the same problem and running those 2 queries appear to do the trick.

Update script to fix the problem

DamienMcKenna

NH, USA

commented 9 July 2016 at 01:00

I ran into this on a site that had about 15 feature modules which had been rebuilt & renamed over time. Here's the update script I used to fix the problem:

/**
 * Delete {system} records for long-lost modules. This is necessary as of Drupal
 * core v7.50 which gives a warning about missing module files.
 */
function MYMODULE_update_7100() {
  $modules = array(
    'old_module1',
    'old_module2',
    'old_module3',
  );
  db_delete('system')
    ->condition('name', $modules, 'IN')
    ->execute();
}

Just add that to a custom module's .install file, update the array of module names that the messages said were missing, rename the "MYMODULE" part to match the name of the custom module and change the "7100" to the next number in the sequence (starting at 7100 for a 7.x-1.x module, 7200 for a 7.x-2.x module, etc).

After running that I don't have any more errors.

--
Damien McKenna | Mediacurrent

Thanks Damien, big help.

Jeff Burnz commented 9 July 2016 at 01:33

Thanks Damien, big help.

Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.

Modul?

PeterX-dupe commented 9 July 2016 at 11:52

Hello Damien,
Tip for Modul?
best regards Peter

Waiting for 7.51

CM63 commented 9 July 2016 at 18:01

Ok, thanks Damien, but we shouldn’t have to do this hardware working. I think this release has a big problem. I am waiting for a 7.51 one :-)

Ok, for those who have removed a module without uninstalling it, there is no doubt, but, at the moment, it not the problem...

I don't think waiting for a

jeroen.b commented 10 July 2016 at 16:55

I don't think waiting for a new version will fix your problem. There is no way to automatically fix this.
These errors were introduced by bad programming or bad workflows on the maintainer's side (not uninstalling modules before removing them for example). It's not that hard to fix these issues so I don't get all these negative comments, this warning is here to actually improve the performance of the site. If this warning message wasn't there, you wouldn't even know there was a problem.

Think of it like this Jeroen.

crystaldawn commented 10 July 2016 at 16:59

Think of it like this Jeroen. Does the warning for the modules that need to be updated spam your screen with 50 warnings, one for each module? Of course it doesnt. That would just be plain dumb. The best way to handle this is to NOT have any warning messages at all and simply show it in the already existing STATUS page. That's really the best answer here if this feature is to stay put.

You do know this is a

jeroen.b commented 10 July 2016 at 17:07

You do know this is a development warning right? It does not show on properly configured websites.
And yes, I do think this should trigger a warning message as it indicates an actual problem. The fact that you get 50 messages indicates that you have a major problem with your website.

I'm sorry you have to spent time improving your website, but it's for the best.

What is the difference

crystaldawn commented 10 July 2016 at 17:19

What is the difference between these two warning messages? Let's test your UX/UI prowess shall we?

Type 1
(user views status page for some reason or another, users always find their way here someday, trust me I know, I've had plenty of calls regarding msgs on the status page)
WARNING: You have 17 missing modules! Please refer to this page (insert link to this page here) to learn how to fix this issue

Type 2
(user views website that shows warnings, its a dev site and the client is QA'ing it, probably the same reason they would check status page above, for QA purposes)
User warning: The following module is missing from the file system: commerce_cart. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_checkout. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_customer. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_file. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_line_item. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_order. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_payment. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
PHP Warning: Use of undefined constant title
User warning: The following module is missing from the file system: commerce_price. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_product. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: commerce_tax. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/apollobrickco/public_html/includes/bootstrap.inc).

Now tell me which warning message here is more important? Look closely young stallion :)

Aww, you didnt reply to this

crystaldawn commented 10 July 2016 at 17:43

Aww, you didnt reply to this one. I hid a more important PHP warning in there amongst all that garbage:

PHP Warning: Use of undefined constant title

Thats is a real warning with spamming :)

I made a module to help with this

labboy0276 commented 12 July 2016 at 16:18

I just made this module to help everyone get through this: https://www.drupal.org/project/module_missing_message_fixer

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Quick and clean

criscom

Graz, Austria

commented 13 July 2016 at 13:16

Thanks for this module. It is much quicker than going into the database and perform the sql commands and also very clean. Your module helped save a lot of time. Thanks!

Unfortunately, your module is

Anthony Pero commented 23 July 2016 at 17:18

Unfortunately, your module is saying nothing is missing, but I am still getting the warning that I'm missing vertical_tabs_example module. Which I think should be in core? I've never installed Vertical Tabs on this site, and its not showing up in my list of modules.

For some reason, this error message is only showing up when i navigate to admin/structure/context/add.

Anthony Pero
Project Lead
Virtuosic Media
http://www.virtuosic.me/

Culprit

philsward commented 14 November 2016 at 06:48

@Anthony Pero If you're using Contextual View modes alongside Context, it appears to be the culprit causing your vertical_tabs_example error.

Works like a charm!

philalonso commented 8 August 2016 at 17:55

Thanks, John. Your module worked like a charm for me.

User warning: The following

jenna1 commented 9 July 2016 at 18:44

User warning: The following module is missing from the file system: views_view_field. In order to fix this, put the module back in its original location. For more information, see the documentation page.

User warning: The following module is missing from the file system: views_append. In order to fix this, put the module back in its original location. For more information, see the documentation page.

DELETE from system where name='views_append' AND type = 'module';

and

DELETE from system where name='views_view_field' AND type = 'module';

works perfect, many thanks @tgeller

'contrib' subfolder

peterhebert commented 9 July 2016 at 20:58

This warning is also being triggered for modules that were installed to a 'contrib' subfolder within sites/all/modules. It would be great if this scenario could be added as a path to look for modules when performing this check, as this is a common practise to have 'contrib' and 'custom' folders to better organize your modules.

Noticed the same, occurred

izmeez commented 23 July 2016 at 18:12

Noticed the same, occurred where a sub-directory "contrib" was used for modules. Registry_rebuild appears to have solved the problem and the warnings are not returning after subsequent flushing of caches.

Registry_rebuild does not solve problem

izmeez commented 24 July 2016 at 16:34

I was mistaken, registry_rebuild does not solve the problem.
I found the trigger is to simply run the available updates report and the warnings are there.
Neither the missing_module or module_missing_message_fixer report any problems.
The site was built using a subfolder sites/all/modules/contrib
Is this an unexpected result?
I shall search for an issue or open one.

Possible related active issue

izmeez commented 24 July 2016 at 16:44

I have added our findings to what appears to be a related active issue, #2765117: Profiles directory distros, and "The following module is missing from the file system..." warnings

dl before disable

peterhebert commented 9 July 2016 at 22:44

This actually works better if you download the module first:

drush dl module_name && drush dis module_name && drush pm-uninstall module_name

Information for those who

guruken1 commented 10 July 2016 at 03:11

Information for those who updated to Drupal 6.x to 7.x. Load modules from "The following module is missing from the file system ..." version 7.x or 6.x (not activate) - better 7.x. In /admin /modules /uninstall will remove the old modules.

Attention CCK! To remove the Content, Text, Comment, AJAX Comments, Comment Notify, Comment Access, Fieldgroup, Forum, Option Widgets, Node Reference, Number etc. - Is required to download the latest Release of the CCK to use Drupal 6.x to the original location (maybe: /modules).

Scrap material from D5

newswatch commented 10 July 2016 at 05:47

I had leftovers even from a Drupal 5 version! Most of them obviously don't have D7 versions. Even many D6 modules don't have D7 versions. So, the idea of restoring the module basically doesn't work.

The idea of cleaning up the database certainly is good. But the Missing Module didn't show up anything on another site that I haven't upgraded yet. The Schema module however shows up a lot of extra stuff.

-----------------------------
Subir Ghosh
www.subirghosh.in

I am going back to 7.44

bglogo commented 10 July 2016 at 12:22

I upgraded D7.44 site to D7.50 and received more than 30 warnings "The following module is missing from the file system."

Some messages are for Drupal 6 modules, for others I don't know which version has been installed, the third is not clear at all what were these modules (unknown names). Some of these sites were not made by me and do not know their history, and what modules have been installed/uninstalled.

And I will have to upgrade more than 70 website! Terrible!

You should not edit the database on production site. So I have to duplicate and edit development copy of each of more than 70 sites, and then reinstall.

At least some weeks redundant work.

I'm going back to 7.44 and will wait 7.51 or when this unnecessary problem will be corrected.

Did you read the change

jeroen.b commented 10 July 2016 at 17:02

Did you read the change record? This problem also exists in older versions of Drupal. The only thing Drupal 7.50 changes it that it actually shows you there is a problem. I advice you not to downgrade and actually fix the problem.
If you are looking for a quick method, check @DamienMcKenna's comment.

Here is a question. Why was

crystaldawn commented 10 July 2016 at 17:05

Here is a question. Why was this feature added when it's covered by a contrib module already? Should the contrib module not be a part of core? Whats the reasoning for ignoring it? I am talking about this here: https://www.drupal.org/project/clean_missing_modules which already addresses this problem brilliantly without all the warning non-sense.

This is not a feature. This

jeroen.b commented 10 July 2016 at 17:17

This is not a feature. This is a change in bootstrap to report problems that have always been in there but are only shown since the change. If this is in a contrib module, developers would never know of the problems unless they install the module. But the module sure is a great help to get rid of the warnings.

I think you dont understand

crystaldawn commented 10 July 2016 at 17:31

I think you dont understand the issue at hand. Usually when a contrib module exists that has the same exact feature set as a feature being proposed for core, it is added to core instead of making a new feature completely and then that module is depreciated with a msg saying that it's no longer necessary for versions 7.?? >. In many cases the contrib module is then changed slightly to suit being in core. That was not done in this case. The module has already been vetted and has a great UI/UX already. Something the core warning feature that was added does not yet have but will soon as this thread gets even longer with complaints ;)

BTW, that module doesnt get rid of anything. It only tells you which modules should be cleaned out. It does the EXACT same thing that this new warning system for core does. Currently there is no module that will clean these warnings automatically yet, mainly because it really isnt possible. Maybe only 70% of them could be cleaned by using standard methods. The rest have to be done by hand by a qualified individual.

Some remedy oher than typing phpmyadmin commands

CM63 commented 10 July 2016 at 18:09

Hello,

I just do not want to tape PhpMyAdmin commands, I would like a remedy like this one : (re)install a module and unisntall it and remove it, or the contrary : uninstall a module, remove it, and reinstalling it.

Is there such a remedy? Thanks for help.

i agree

Misterloup commented 11 July 2016 at 09:26

hello
for many people error is in boostrap : for me and i got about 50red warning=> "User warning : The following module is missing from the file system: content. In order to fix this, put the module back in its original location. For more information, see the documentation page. dans _drupal_trigger_error_with_delayed_logging() (ligne 1128 dans /home/vetosent/www/includes/bootstrap.inc)."

i think it comes from my thema which is "COLOR GLASS" by CMSbots.com, and which is boostrap based;
it's not an error of my configuration;

is there a method for not showing these warning in the panel control?

[i have changed the file "include/boostrap.inc" with the older of drupal core 7.44 and the problem deasapered , excepted that in the admin menu it says drupal core 7.44,; when i go in the section of the updates the drupal core is 7.50
So, i changed the name in this file (include/boostrap.inc 7.44) from drupal 7.44 to drupal 7.50 and all is ok...
but what about drupal 7.51 ,]

thank you all

Beware

mr.barneylodge@gmail.com commented 11 July 2016 at 10:02

I found that If I used the previous version of bootstrap.inc, I could not manually check for updated modules

I can see the method to the madness

Road Kill commented 11 July 2016 at 14:54

This has created a nightmare of a problem for me as the names of some of the offending modules go by different names than the names listed in the errors.

Like simple countdown no such module exists but the error message is telling me that simple_countdown is missing.
I can understand why this has been done but hell some advanced warning would have been great.

Their should have been an option built in with this update to remove any ghost modules from the database simple as that.

Yikes

cgeorge29 commented 11 July 2016 at 16:58

I have to admit, I am not pleased with this update either. I understand the need for a clean tidy site, I try to keep my sites in excellent health. However this update threw some crazy module errors that I know I properly uninstalled ages ago.

Not to mention all my efforts to remove them, via reinstalling and uninstalling.. again, to trying to rid them from the phpMyAdmin with commands are still not effective. My biggest offender is Commerce. That sucker wont go away!

Right now the my only option is to reinstall the directory and leave the module off... that is the only way I can get these errors to semi-resolve on my client site. I dont like this solution, but I cant seem to find anything else to work.

Really would have liked an option to manage these errors over longer duration rather than have clients freaking out when they work in the back-end of their own sites.

If anyone comes up with a good system to remove modules that refuse to go... please say so! I hate the clutter of unused modules in my directory just to appease a false error.

Thank you.

Are you using AT-Commerce theme

april26 commented 12 July 2016 at 08:06

The AT-Commerce theme itself causes issues - see the theme page for a new release.

There are 10 kinds of people in the world, those who understand binary and those who don't!
InterComm South Africa (www.intercomm.co.za)

This is missing from the opening post

pendaco commented 16 August 2016 at 09:15

This is missing from the opening post but seems to pop-up for some people;

- Check your field_config and field_config_instance tables (see here)
- Check your installed theme(s) and search for any hooks that might call those modules (see here)

The opening post only talks about "because many modules do important cleanup tasks during the disable/uninstall process, and this solution will result in those being skipped." but doesn't mention calls from within a theme and only mentions the system table.

P.s. Make sure to back-up before deleting anything manually.

Contrib modules in Profiles folder

amytswan commented 11 July 2016 at 18:08

I realize we may have a bit of an edge case here, but I’m feeling fairly confident I’m not alone… our site uses distribution profiles and our contrib modules are in the `profiles` folder rather than `sites/all`. All disabled submodules cause this warning. Deleting their entry in the system table has no affect. The entry is replaced on Registry Rebuild and the warning repeats. Is anyone else experiencing this and if so, were you able to find a solution?

Cache clear error, not registry rebuild

amytswan commented 11 July 2016 at 18:27

Update: the errors are triggered upon the first cache clear after rebuilding the registry.

Yes, we're experiencing the

logicp commented 18 August 2016 at 15:40

Yes, we're experiencing the exact same behaviour.

Looking into this now and will post about my results.

Removing module name from system table worked for me

WayneDyck commented 11 July 2016 at 23:25

For what it's worth, the six errors I saw on our site were custom modules made using Features. The modules were originally pull requests from members on our team and I remember renaming the modules to align with a more consistent naming convention. Executing the,

drush sql-query "DELETE from system where name='module_name' AND type = 'module';"

SQL statement with each of the apparent missing modules removed the warning messages for our site.

This happens when you have

ljgra commented 12 July 2016 at 02:36

This happens when you have upgraded from Drupal 6, to 7 and up. The "missing Content..." error was from previous D6's CCK file. You may need to reupload to your modules folder those previous Drupal 6 modules you removed before.

Some errors:
>> token_actions: found under token drupal 6. Download this module from drupal site, place token_actions.info, token_actions.module and token_actions.test in one folder, zip then upload and extract to your module folder.

Then go to your admin>>modules, click the Uninstall Tab and uninstall all modules listed there. Some error may occur when uninstalling all at once because of some module/s. Reupdate your site and see if this helps (sometimes solves the problem). The continue unstalling unused modules from your admin.

This problem is occurring for

coolhandlukek2 commented 12 July 2016 at 08:19

This problem is occurring for me too after a 7.50 upgrade with modules stored in a /contrib directory

Keep up with the good work

uno commented 12 July 2016 at 08:30

I have been a Drupal user and a true fan for more than eight years now, started with D6, upgraded to D7, and build a large number of sites, tried and used hundreds of modules, including some of my own. Some of them were poorly made, and junk left behind always worried me.

One of my sites, upgraded to D7 has more than 18.000 nodes and 200 MB just in field_data_body + field_data_comment_body. With thousands of daily users, every millisecond spared, every bit of peace of mind is more than welcomed, no matter the amount of work required.

I will remain a true follower and my confidence in Drupal can only be stronger after 7.50 missing module report. A little bit more work, yes, but the benefit of knowing that there is no garbage floating around is what is keeping me with Drupal.

Keep up with the good work people, I will try to do the same on my side.

--
... I mind

Neither a matter of D6 nor misplaced module

CM63 commented 12 July 2016 at 08:41

Hello,

No, I think this problem is neither a matter of D6 nor a misplaced module. It is a real bug that need be fixed for the next release.
And modifying the code by hand or typing a command in PhpMyAdmin is certainly not a good solution. You will get the bug back with the next release.
And specially for those who have a big site, or many of them.

You are correct

manyk commented 12 July 2016 at 09:10

The bug is in the module(s) who doesn't implement a clean uninstall process.
All that remains is for the maintainers to produce a better code or for users to clean the mess with the help of various hacks or even fix the module by themselves.

Handling missing installation profiles

drubb

he/him

German

Sindelfingen

commented 12 July 2016 at 11:26

In case the missing module isn't a module but a Drupal installation profile, it's not enough to remove the corresponding row in the system table, it will be restored on the next request. Here's how to fix this, e.g. for a missing profile 'drupalcenter' (often faced by german users):

drush vset install_profile standard
drush sql-query "DELETE from system WHERE name='drupalcenter' AND type = 'module';"

So the first step is activating the core 'standard' profile, before removing the missing profile.

Please be careful with drush vset install_profile

amytswan commented 12 July 2016 at 18:52

Heya @drubb, just wanted to give you and others working on this issue a quick heads up: If you have modules inside your profile like I do, i.e. profiles/[distro-name]/modules, running the drush vset install_profile standard command is volatile. Your site will no longer no where to look for the files, and will break. I speak from experience having tried it. The solution for getting the site back again is to go into the variable db table, look for the install_profile variable, and reset the variable back to your distro-name (you'll likely need to write it like this: s:11:"distro-name"; (s = string, and the number following = the number of chars in the string).

Very Helpful!

hershey.k commented 20 July 2016 at 19:05

This helped me. Thank you!!

How to do without drush

wglombig commented 3 August 2016 at 17:27

I am a German user. So I see the same problem with "drupalcenter". So far I have not used drush yet. Is there a way to achieve this without using drush?

Solution without drush

maki3000 commented 28 November 2016 at 12:41

Hello wglombig!
This may come a little late, but here's a description to solve the problem without drush:
http://www.drupalcenter.de/node/55978
(This is in German)

I have put some commands

mikkmiggur commented 12 July 2016 at 13:53

I have put some commands together and have one line command to clean up database from deleted modules.
That drush sql-query is for those module whitch drush can't download. Mostly for custom modules.
module_name='write_module_name_here' && drush dl $module_name && drush dis $module_name && drush pm-uninstall $module_name -y && drush sql-query "DELETE from system where name='$module_name' AND type = 'module';"

Bug caused by "Azexo composer"

Londova commented 12 July 2016 at 15:33

In my case non of previous methods worked (I didn't try the method described by mikkmiggur).
While deactivating all media modules (because of error-missing module "media_wysiwyg"), I find that the problem was caused by "Azexo composer" module. I uninstalled the module, run the Cron and clear the Cache. Now is fine.

This feature is welcome as it helps to identify the bugs.

Once I updated to Drupal 7.50

albertski commented 12 July 2016 at 16:03

Once I updated to Drupal 7.50 I started seeing the error when running drush cc all:

The following module is missing from the file system: <em class="placeholder">infinite_scroll</em>. In order to fix this, put   [warning]
the module back in its original location. For more information, see <a href="https://www.drupal.org/node/2487215">the
documentation page</a>. bootstrap.inc:1128

Turns out that the GD Infinite Scroll module had a bug which was fixed in this patch.

So in my case it was a bug in the module that was causing the error and Drupal 7.50 helped to find it.

I made a module to help with this

labboy0276 commented 12 July 2016 at 16:19

I just made this module to help everyone get through this: https://www.drupal.org/project/module_missing_message_fixer

Hopefully this elevates some sadness out there.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Great!

ranitz commented 12 July 2016 at 22:13

Thank you, just tested it and it works great. Big time saver :)

fixer module

jimweber commented 13 July 2016 at 00:03

Works great!

No luck

rufferto@mac.com commented 13 July 2016 at 00:53

It tells me "No missing modules detected." yet I still see a bunch of messages. In some cases I remember uninstalling the modules in question.

I would be curious as to what

labboy0276 commented 13 July 2016 at 01:46

I would be curious to what your setup is. This module uses the same error mechanism that basically generates the message itself.

Can you post an issue here: https://www.drupal.org/project/issues/module_missing_message_fixer with as much info as you can and the messages you are getting, etc. Also if the site is a migration from earlier version of drupal, etc.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

i wait

Misterloup commented 13 July 2016 at 11:38

hello,
thank you for this module; but i will wait for the next drupal core 7.51, and if the problem remain i try your module ; i have already downloaded it...
i'm afraid it's dangerous!!;-)

[my warnings were for about all my installed modules :"User warning : The following module is missing from the file system: content. In order to fix this, put the module back in its original location. For more information, see the documentation page. dans _drupal_trigger_error_with_delayed_logging() (ligne 1128 dans /home/vetosent/www/includes/bootstrap.inc)."]

thank you

I sincerely doubt they will

labboy0276 commented 13 July 2016 at 12:58

I sincerely doubt they will change anything in the next release as this issue is not a bug. It is an added feature to help with performance. The reason you have these messages is due to the fact your system table has ghost entries. This is caused by either improperly uninstalling modules and / or modules still trying to call non existent modules in their code (as seen in ubercart and module_filter). The only way to address is to clean up the system table. There is no danger in this per se.

Edit: Your error is due to ubercart as mentioned above: https://www.drupal.org/node/2763555 I would install this patch and it should help you.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

it work's

Misterloup commented 15 July 2016 at 03:56

hello
the labboy's module works for me too.
thank you

Great module! For me it was a

criscom

Graz, Austria

commented 13 July 2016 at 13:28

Great module! For me it was a quick and comprehensive solution to get rid of the error messages. Awesome!

Thank you!

leistiko_texvet commented 13 July 2016 at 15:24

Missing Module Message Fixer did a great job for me. Thank you very much. I had (literally) 50+ errors to address (I inherited this site; don't judge me! :) ).

Were I empowered to do so, I'd recommend installing and using it as the first step for everyone.

Thanks again!

Thank you very much!

bglogo commented 17 July 2016 at 09:09

Excellent module, saving me a lot of time. But not everyone who has this problem with the upgrade to Drupal 7.50 will easily find this solution. It would be good if the system error message, coming after this upgrade, contains a link to current discussion and to the module, which you have done.

Or in the Release notes, or in the Readme file. I don't know how, but it should be easier for users to find this module. And it would be best if this fixer option is embedded in the system.

Great!!!

phofab commented 23 July 2016 at 03:42

I can only say great!! It worked for me on 4 Sites. Not being a programmer I waded through this thread with fear.Thank you very much for taking the time to resolve this issue.

The modules missing were CK Editor and wysiwyg_spellcheck, which hadn't been installed.

Great !

brulain commented 23 August 2016 at 07:14

Thanks a lot for this pretty module : it does the job perfectly !

Thank you, the fixer module

pengi commented 21 September 2016 at 05:36

Thank you, the fixer module cleared up the list of missing modules very neatly!

What I don’t understand is

Grabby commented 12 July 2016 at 21:29

What I don’t understand is how do I get

“User warning: The following module is missing from the file system: content. In order to fix this, put the module back in its original location.”

when I started a spanking brand new site in 7.43, upgraded it to 7.44 with no problem, then got the above on going to 7.50 and only added modules along the way, and didn’t remove any?

content, cck?

ranitz commented 12 July 2016 at 22:26

content might be cck, kind of obsolete in D7. Did you install cck? https://www.drupal.org/project/cck

Found the bastard, the

caspianroach commented 13 July 2016 at 04:22

Found the bastard, the culprit for me was the Ubercart module which was ported from Drupal6 and it seems like some leftovers from it stayed in the code. See https://www.drupal.org/node/2763555

Ok for you but not for us others

CM63 commented 13 July 2016 at 06:57

@Caspianroach : ok for you, but not for us others, who have never migrate from D6 nor removed a module without uninstalling it.

I've never touched Drupal6

caspianroach commented 13 July 2016 at 07:41

I've never touched Drupal6 either. Ubercart for Drupal 7 was ported from D6, so even if you never touched 6 you will still have these issues if you have Ubercart installed.

@caspianroach you are

Grabby commented 13 July 2016 at 08:14

@caspianroach you are absolutely correct. After I upgraded from 7.43 to 7.44 I installed Ubercart 7.x-3.9. Even though I didn’t disable or remove any modules I got the warning. Upgrading Ubercart to 7.x-3.x-dev released on July 11th fixed the problem!

I agree

CM63 commented 17 July 2016 at 08:16

@Grabby : I completely agree with you, if you have the message even if you have not install any module, it is not normal, and would confirm that it is a bug in the release. Without noticing that : what is that module "content" ?? :-)
If I have time I'll try to create a site from the 7.50 to see if we have the message or not.

PS : I now desagree myself , see below VV

@Grabby

CM63 commented 17 July 2016 at 08:14

Hello,

The fact that the 7.43 and 7.44 didn't signal the message before was a bug that has been fixed in the 7.50. Try the following:
- install the module that is signalled to be misplaced , and uninstall it just afterwards, if you wish,
- if the module is right designed to uninstall itself properly, that would fixed the problem,
- if not, or if the module no longer exists, just try the SQL command exposed below.

Best regards.

Module filter

joonapenttila commented 13 July 2016 at 08:45

Hi,
I don't rly know is this bug or not, but:
User warning: The following module is missing from the file system: module_filter. In order to fix this, put the module back in its original location. For more information, see the documentation page. funktiossa _drupal_trigger_error_with_delayed_logging() (rivi 1128 tiedostossa /var/www/drupal/includes/bootstrap.inc).

We don't even have whole module on your system and still whining it.

Same

Wil B. Samson commented 19 July 2016 at 14:58

We are experiencing the same error - we have never had Module Filter installed and following the steps above (installing, uninstalling, removing) doesn't remove the error.

Reinstall and do not uninstall

CM63 commented 19 July 2016 at 16:59

This means that this module does not have a proper unintalling process. Just reinstall the module, and don't uninstall, keep it in. It is not necessary to activate the module.

Never Installed

Wil B. Samson commented 19 July 2016 at 17:04

@CM63 but should this occur for a module that I've never had installed? This isn't a "reinstall" scenario. It actually seems to be an issue with the Adminimal theme outlined here.

Modules badly uninstalled in the past

CM63 commented 19 July 2016 at 18:04

Yes because it is modules that had been badly uninstalled in the past, I suppose, in the core itself, by the developpers, or in the release itself. I have that message about the module "Libraries" that I had never installed. I just installed it and the message disappeared. I don't unstall it because, may be, the module has not a proper uninstalling process (it does not erase that key in the database that we are taking about above).
If you create a new site now with the 7.50 release (that I just did for another site) the message doesn’t appear.

Pantheon

Wil B. Samson commented 19 July 2016 at 22:34

Interesting... we're on Pantheon so it may be somewhere in the history of their distribution. I built the site from the ground up so I'm positive it's never been added (by me at least) - I too had the "Libraries" warning but it cleared on a reinstall and proper uninstall. One thing to note about the link I mentioned above, it's still possible that the Adminimal admin theme is the culprit for the Module Filter error specifically - when I deactivate the theme, the error disappears.

I may have to spin up a new 7.50 and test the Adminimal theme to see.

7.50 and Adminimal Issue

Wil B. Samson commented 20 July 2016 at 15:02

I just spun up a clean 7.50 install and added the Adminimal admin theme... it immediately popped the error for Module_Filter only. It's clear that somewhere in Pantheon's distribution or the Adminimal theme construction, a miss-configuration or poor uninstall has occurred.

This issue is specific to that relationship (7.50 and Adminimal).

Module filter

joonapenttila commented 13 July 2016 at 08:45

We don't even have whole module on your system and still whining it.

Issue fixed

joonapenttila commented 13 July 2016 at 11:17

Module_filter issue
https://www.drupal.org/node/2763581

Thanks!

Wil B. Samson commented 19 July 2016 at 15:01

Thanks for the link - this certainly eases my stress about it.

Just install and remove

CM63 commented 19 July 2016 at 17:03

Hello,

If the 7.50 signals you the absence of some module that you have never installed, just install it , and just uninstall(1) it afterwards if you like. And the problem would be solved. It is not necessary to activate the module.

If that module no longer exists, use the method typing the SQL command exposed in some posts above.

See you.

(1) Except if uninstalling the module get the message back. In this case, install it but don't uninstall it afterwards. This means that the module does not have a proper unistalling process. Keep it in without activating it.

Fix for modules that were renamed?

DSquaredB commented 13 July 2016 at 19:11

Is there a fix for warning messages because a module was renamed? In my case it's the Features Tools module. Although it's not used on my production sites, it is on several of my dev sites. At some point the module was renamed from features_tools to ftools so I am getting the warning message that features_tools isn't available.

The fix is the same

labboy0276 commented 13 July 2016 at 19:31

The fix is the same regardless of the cause. It is still a ghost entry in your system table. You can use https://www.drupal.org/project/module_missing_message_fixer or do DELETE FROM system WHERE name="features_tools";

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

How to fix a module that no longer exists

VectorNM commented 13 July 2016 at 19:15

Hello,

I only had 4 of these errors show after updating to 7.50. One of the modules, Video Resources (which I have never heard of before), threw this error. How would I go about fixing this error message if the module no longer exists?

Thanks

Try this

labboy0276 commented 13 July 2016 at 19:32

You can try https://www.drupal.org/project/module_missing_message_fixer to fix your messages.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Hi there, thanks for your

johnrey tanquinco commented 14 July 2016 at 08:18

Hi there, thanks for your link, i've actually tried it myself...getting rid of the content error message... But im getting "No Missing Modules Found!!!" as a result/list in your module, though I know it still appears in the /admin/reports/status. Thanks!
"

Hello,

labboy0276 commented 14 July 2016 at 12:42

Hello,

Quick questions:

Do you have ubercart installed?

What is the message in the status report?

If you can run drush can you run this and paste the results here:
drush sql-query "SELECT filename FROM system WHERE name ='content';"

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Status Report, same as the

johnrey tanquinco commented 15 July 2016 at 04:26

Status Report, same as the others:
User warning: The following module is missing from the file system: content. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /home/****/www/****/www/includes/bootstrap.inc).

Result running your drush:
Query failed. [error]

Ive also tried this command:
drush sql-query "DELETE from system where name='content' AND type = 'module';"
Result: Query failed. [error]

Well, one of the solution suggested to me, though not recommended is turning off the warnings under admin/config/development/logging as I may miss unrelated issues/errors.

As I can notice, theres no module named as 'content'. It may be just associated to other module like cck.

OK

labboy0276 commented 15 July 2016 at 03:25

Do you have ubercart installed?

Try this set of commands then:
drush sql-cli then when you are at your sql prompt, try SELECT filename FROM system WHERE name ='content';

Curious to see what the output is, if not you can just delete it.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Yes, i have ubercart

johnrey tanquinco commented 15 July 2016 at 05:44

Yes, i have ubercart installed...

Result on query:
Empty set (0.00 sec)

Welll, i've actually tried to dig in the database....and look for the name "content" under system table... there wasn't. It was just associated in cck and ctools.
I remove cck and content_migrate(cck) from database. Unfortunately, after the cc, error message still exists.

Get the patch

labboy0276 commented 15 July 2016 at 12:44

The module I made should of pointed you to this patch https://www.drupal.org/node/2763555

Add that patch and this will fix your issue.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

After doing this command:

johnrey tanquinco commented 16 July 2016 at 08:04

After doing this command: curl https://www.drupal.org/files/issues/2763555-4.patch | patch -p1 under mysite.com/sites/all/modules/
im getting this result:

can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/uc_product/uc_product.module b/uc_product/uc_product.module
|index a052ebf..e0fd1a0 100644
|--- a/uc_product/uc_product.module
|+++ b/uc_product/uc_product.module
--------------------------
File to patch:

and also tried it under mysite.com/modules/
result was:
patch: **** write error : No space left on device

Wrong path

DamienMcKenna

NH, USA

commented 16 July 2016 at 10:20

@Johnrey: You have to be *inside* the ubercart directory for it to work.

--
Damien McKenna | Mediacurrent

Thank you so much...!

johnrey tanquinco commented 18 July 2016 at 05:05

Thanks guys... Issue solved using patch file.

Isn't this what system_rebuild_module_data() was supposed to do?

Dave Reid

he/him

English

Nebraska USA

commented 14 July 2016 at 16:05

I thought that system_rebuild_module_data() would automatically remove any modules from the system table that do not exist in the file system. Is that no longer happening? I would think that running update.php or just simply visiting the admin/modules page would be enough to trigger that function and stop the warnings from happening. Is that not the case?

Good question, it appears it

labboy0276 commented 14 July 2016 at 16:33

Good question, it appears it should clean up records as seen in this function:

https://api.drupal.org/api/drupal/modules%21system%21system.module/funct...

Which is called from here:

https://api.drupal.org/api/drupal/modules%21system%21system.module/funct...

Which as you know is called in places like you said. So it is odd.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

system_rebuild_module_data()

David_Rothstein commented 14 July 2016 at 18:29

system_rebuild_module_data() only removes a nonexistent module from the system table if the module is uninstalled. Otherwise it leaves it in place.

That is intentional, I assume, because if it removed them in other situations the information on the module state would be lost forever, which would lead to major problems if you ever tried to add back the module and turn it on again. (It also could lead to some really nasty problems if part of the filesystem ever went unavailable due to some kind of temporary "blip" - it would cause Drupal to permanently forget which modules were installed, compared to now where Drupal should be able to recover from that scenario quite nicely.)

I thought that system

Kimanas commented 3 August 2017 at 09:43

I thought that system_secockpit_module_data() would automatically remove any modules from the system table that do not exist in the file system. Is that no longer happening? I would think that running update.php or just simply visiting the admin/modules page would be enough to trigger that function and stop the warnings from happening. Is that not the case?

yes,I followed your system rebuild module data,sloved the problem,thx.

Missing "content" module error

bobburns commented 14 July 2016 at 21:45

If you have Ubercart installed check => https://www.drupal.org/files/issues/2763555-4.patch

replacement file

DrupalDavie commented 15 July 2016 at 15:58

Is there anyway to simply provide a corrected, replacement uc_product.module file for download/upload? I'm not clear on where to apply the patch within the uc_product.module file. I can find the

module_load_include('inc, 'content', 'includes/content.crud');

line only once, under function uc_product_uc_store_status.

I am not using a product kit and cannot find the function uc_product_kit_uc_store_status line in the file.

Try this

labboy0276 commented 15 July 2016 at 16:11

cd into the module directory on your cli, then run:

curl https://www.drupal.org/files/issues/2763555-4.patch | patch -p1

It will patch it for you, or if you want to keep the file:

wget https://www.drupal.org/files/issues/2763555-4.patch
patch -p1 < 2763555-4.patch

That is the normal way to patch files in Drupal. See this article for more info: https://www.drupal.org/patch/apply

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

delete rows in table field_config

vic7 commented 15 July 2016 at 17:29

DELETE from field_config WHERE module='[name module]'

The solution

CM63 commented 15 July 2016 at 17:44

Yes you are right : if the signalled module no longer exists, type this command DELETE in the SQL database. But if the signalled module still exists : just install it , and uninstall it just afterwards. It is not necessary to activate it. The message will disappear.

See you.

One thing I've noticed is

David_Rothstein commented 16 July 2016 at 21:39

One thing I've noticed is that even if your site is configured not to display PHP warnings to the screen, Drupal will still display them on the screen during update.php. So these messages are the first thing many people will see when updating their site to Drupal 7.50, even if they are not accustomed to ever seeing PHP warnings on the screen. Maybe that is why there are a number of people who have been so alarmed by these new messages...

The above behavior has nothing to do with the new warnings added in Drupal 7.50 (it's general behavior that Drupal does with any messages) but I don't think it makes much sense so I filed an issue to fix it: #2767663: Drupal always displays notice/warning/error messages on the screen during update.php, even when the site is configured not to

How can I get that list back?

cpk commented 16 July 2016 at 23:14

I did my update of Drupal 7 using drush, and I got a list of "module is missing" errors like everyone else. I'll try to address the 20 modules that were missing, but I'd like to know if there's a way to test again so that I can tell if what I did was successful. Does anyone know how to do that?

Clearing the site's caches

David_Rothstein commented 16 July 2016 at 23:17

Clearing the site's caches will likely surface many of the warning messages (although not 100% guaranteed to surface all of them).

That didn't work.

cpk commented 19 July 2016 at 20:28

I cleared the cache; no errors. I did an update (drush up); no errors. I used the Drupal GUI to clear the cache; no errors. I'd like to fix the problem if my system has references to modules that are missing, but I don't know how to reproduce the errors that are discussed here. Without being able to reproduce the error messages, there's no way to be sure you've corrected the underlying problem (even if you do follow the recommended steps).

Well done

CM63 commented 17 July 2016 at 08:22

Just check that you have not the message any longer.

Normally the message concerned modules that you didn't use. So after installing them, you can uninstall them. If the modules are well configured to uninstall themselves properly, you would not have the message any longer. If you still have the message for some modules, just try the SQL command exposed in posts above.

"Libraries" is the name of a module

CM63 commented 17 July 2016 at 21:08

Hello,

Just one thing : "Libraries" is the name of a module (and not a synonymous for "module"), and it seems like this module was not correctly uninstalled in the past releases. So , if you have the message for this module, like I had, just install it, and the message will disappear . It is not necessary to activate the module.

The so called "libraries" module is (or was) for installing third party libraries in Drupal.

Missing theme jquery_update

m.OK commented 17 July 2016 at 22:53

After Upgrade a new site, startet on 7.44, to 7.5 I get "User warning: The following theme is missing from the file system: jquery_update. …", That Message confuses me. Jquery_update is not a theme. Any Idea what went wrong?

Probably due to #2762793:

David_Rothstein commented 18 July 2016 at 03:34

Probably due to #2762793: Modules are listed as missing themes in Drupal 7.50, triggers user warnings. (assuming this site uses the Omega theme).

You are right, it is Problem

m.OK commented 20 July 2016 at 08:21

You are right, it is Problem with the Omega-Theme. Thanks for the link, found a solution there.

Just install the module

CM63 commented 18 July 2016 at 08:05

Hello m.OK,

It is not a theme, it is a module that happens to be badly uninstalled in the past. Up to now we were not informed about such a thing, this had been fixed in the 7.50 release : now we are informed when a module has been badly uninstalled (a key had not been erased in the databased).

Just try installing that module jquery_update and the message will disappear . It is not necessary to activate the module.

If that module no longer exists, try to erase the key by hand in the database : look for "DELETE" "SQL" in the discussion.

Error messages

fabius commented 19 July 2016 at 19:19

I have several "errors" on one site. The first is a missing module called "demo_profile". I tried the special module but it won't install. Perhaps it's a tar? I tried modifying "update.php" - no change.

Will this be fixed by the next update? If so I prefer to wait for personal reasons.

I tried two approaches:
I pasted the code into update.php right after the initial "PHP". Is that right?

I also installed the custom module for fixing the user warnings. That really helped. After enabling I clicked Permissions, Configure and it immediately found and displayed the modules in question. They're gone.

Thanks guys and gals,

Just install the module

CM63 commented 19 July 2016 at 08:02

Hello,

Just try to install that module "demo_profile" and the message will disappear . If the module no longer exists, just suppress the key by hand in the database by typing the SQL commands as explained above.

Random Warnings

RAFA3L commented 19 July 2016 at 17:17

I get a lot of random warnings, after refresh the warnings are gone, but appear randomly again after back to the same page (front or internal)

These are the modules with warnings and all are properly installed and working before and after the update to 7.50, but the warnings still there.

addressfield
date
compact_forms
ckeditor
search_krumo
user
views
logintoboggan
field
views_slideshow
simpleads
node

EDIT: uninstalling one module the warnings disappear

EDIT 2: the random warnings continue, less than before, but suddenly appear

DELETE from field_config

vic7 commented 19 July 2016 at 06:06

DELETE from field_config WHERE module='[name module]'

Do not delete by hand

CM63 commented 19 July 2016 at 08:08

Some of these modules are very important, such as node, user or date. So it is not a good idea to delete them by hand.

Just install the modules

CM63 commented 19 July 2016 at 08:06

Hello,

Just install all theses modules and activate them, and the message will disappear . Some of them are quite important , however, such as node or date.

For which modules?

CM63 commented 19 July 2016 at 18:13

Have you the message for all these modules in your list or only some of them now?
Did you reinstall all the modules of the list? That is the simplest solution if the module still exists.
You have to do that "key erasing process in the database" (that we are speaking about above) only if the module no longer exists.

Please erase this message

CM63 commented 19 July 2016 at 18:12

Please erase this message.

Error when installing a new module with Drush

andileco commented 19 July 2016 at 18:12

I installed https://www.drupal.org/project/module_missing_message_fixer, which fixed existing errors.

However, I installed a new module (had never used this module before) using:

drush en viewsfield

and got this error in my terminal:

user@ip:/.../drupal/htdocs$ drush en viewfield
viewfield was not found.                                                [warning]
The following projects provide some or all of the extensions not             [ok]
found:
viewfield
Would you like to download them? (y/n): y
Project viewfield (7.x-2.0) downloaded to                               [success]
/.../drupal/htdocs/sites/all/modules/viewfield.
APC-Remote : APC all requested flushes done.                            [success]
The following module has moved within the file system: <em              [warning]
class="placeholder">viewfield</em>. In order to fix this, clear caches
or put the module back in its original location. For more information,
see <a href="https://www.drupal.org/node/2487215">the documentation
page</a>. bootstrap.inc:1128
The following extensions will be enabled: viewfield
Do you really want to continue? (y/n): y
viewfield was enabled successfully.

(I had actually seen this error when installing module_missing_message_fixer, too).

This seems like a bug, right?

Success

CM63 commented 19 July 2016 at 18:18

I don't think so. It says that it has not found the module in the default repository, but it has found it elsewhere itself. I think it is ok.

I just feel like the message:

andileco commented 19 July 2016 at 18:29

I just feel like the message:

The following module has moved within the file system: <em              [warning]
class="placeholder">viewfield</em>. In order to fix this, clear caches
or put the module back in its original location. For more information,
see <a href="https://www.drupal.org/node/2487215">the documentation
page</a>. bootstrap.inc:1128

is not needed, as the module is being downloaded for the first time, and the only change in location is during the process of the Drush command (it hasn't even been enabled once at that point)....

I just tried it myself on a

David_Rothstein commented 20 July 2016 at 03:08

I just tried it myself on a site that had never downloaded that module before and the warning message did not appear for me.

If you try it on a fresh install, do you still see it then?

I think it's very likely that the module was previously used on this site (maybe not by you, but perhaps by someone else?) and then deleted without being properly uninstalled...

I guess it's possible for

andileco commented 20 July 2016 at 04:25

I guess it's possible for that one. But I got the same warning when I ran "drush en module_missing_message_fixer" - and this module is brand new. I'm the only one who installs modules on this site. I'll look for the message next time I install a module.

Same issue and tried almost all the options

Sohal Khatwani commented 21 July 2016 at 01:51

I moved some of our modules from the sites folder to profiles folder so that it is maintained as a distro. The site works fine and does not seem to have any errors. Status report looks good and even running an update.php gives no errors. However, in Drush when I try to do a registry rebuild I get the message at the end. This happens for around 25 modules. I have tried the module missing message fixer and other options. I know one of the recommendations is to move the module back to the sites/all folder but that I believe I should not have to do that if I have done a registry rebuild?

The following module has moved within the file system: class="placeholder">bundle_copy. In order to fix this, clear
caches or put the module back in its original location. For more
information, see the
documentation page. bootstrap.inc:1128

You are not alone

amytswan commented 21 July 2016 at 02:10

Hi @Sohal Khatwani! If I understand your comment correctly, it sounds like we're having a similar issue. I submitted an ticket to the Drupal Core 7.50 issue queue, in case that's helpful. There isn't a proposed solution as of yet, but hopefully it'll get addressed soon: https://www.drupal.org/node/2765117

Thank You

Sohal Khatwani commented 21 July 2016 at 02:15

Hi @amyvs. I went through your It does sound like the same issue. Hoping for a resolution soon.

Until now I still getting the

RAFA3L commented 21 July 2016 at 17:09

Until now I still getting the same random warning from these modules, is really random, I can't determine a pattern, even after a Flush all cache there is no warning (but sometime yes) or just navigating some pages (backend or frontend) is unpredictable when the warning appear. All this is in a current project on development process, so in an entire day of work the warnings maybe appear 10 times

addressfield
date
compact_forms
ckeditor
search_krumo
user
views
logintoboggan
field
views_slideshow
simpleads
node

What was the solution for me

dpacassi

English

Zürich, Switzerland

commented 22 July 2016 at 09:17

So, after updating Drupal to 7.50, I started receiving the "The following module is missing from the file system..." for a module (telephone) that I uninstalled a couple weeks ago.
Since the module also wasn't listed on the system table, I started debugging the bootstrap.inc file and traced down the error to the field_read_fields() function.

Long story short:
While the module and its fields were uninstalled successful, some field configuration of that module still existed!
If you run following SQL and get any results, that may be the source of your warnings!

SELECT *
FROM field_config
WHERE deleted = 1

In my case, I just deleted those entries, and tada... the warnings were gone.
Hope I'm able to help out a couple of you guys...

yes, same here. field_read

donquixote commented 20 October 2016 at 22:34

yes, same here. field_read_fields() does not check if module is disabled or missing.

See #2820939: field_read

donquixote commented 20 October 2016 at 22:46

See #2820939: field_read_fields() does not check whether a module is disabled or missing.

Be carefull

CM63 commented 22 July 2016 at 09:53

Hello,

Of course deleting the key by hand in the database does work, but I would use that only if uninstalling the module does not remove the message.
Once again, this message is not a bug in the 7.50, rather it is a bug in the uninstalling process of some modules. Indeed, there is a lot of them, I aggree, but it's like that.

The following module-disabled

UksusoFF commented 23 July 2016 at 09:43

The following module-disabled is missing from the file system
What does it mean? Module files exists and correct uninstalled. It's only disabled.

More precision please

CM63 commented 23 July 2016 at 12:49

Hello UksusoFF,

Could you please post the exact message, your post seams to be inconsistent, I don't understand (if the files exists that would mean that the module is not correctly uninstalled , and if it is disabled that would mean that it is installed ??). Thanks.

Full message:

UksusoFF commented 23 July 2016 at 13:27

Full message:

User warning: The following module-disabled is missing from the file system: domain_vbo. In order to fix this, put the module-disabled back in its original location. For more information, see the documentation page. в функции _drupal_trigger_error_with_delayed_logging() (строка 1128 в файле /includes/bootstrap.inc).

Module uninstalled via admin/modules/uninstall, but not removed from filesystem.

Reinstall it

CM63 commented 23 July 2016 at 16:29

So just install the module domain_vbo , and see if the message disappears.
After that, try to uninstall it again, and if the message comes bask, try the Module Missing Message Fixer.

Omg, some month not received

UksusoFF commented 30 October 2016 at 19:05

Omg, some month not received this message. But now it's return back:

User warning: The following module is missing from the file system: module_filter. For information about how to fix this, see the documentation page. в функции _drupal_trigger_error_with_delayed_logging() (строка 1128 в файле /includes/bootstrap.inc).

But only install NEW adminimal theme. Not disable. Not remove any other modules.
Any method for complete disable this intrusive check?

Answer is No, and thats by design

joseph.olstad

French

commented 31 October 2016 at 00:41

The short answer is no, you cannot remove this check, and this is a good thing. Prior to release 7.50 drupal administrators had no warning message when enabled or once-installed modules suddenly vanished from the filesystem.

So, scenario, lets say your friend Igor Vladisov is your dev-ops partner and he had a bit too much vodka at lunch, fell asleep on his keyboard and accidentally deleted some files from your sites/all/modules folder , he wakes up a few minutes later, forgot about this, didn't realize he'd done anything , then the next day you come into the office and ya, no idea but some new problem came up. Well before 7.50 you'd have no idea, but since Drupal 7.50 , when you run updb you'll get a warning message that you have a missing module.

Another case: lets say you're using a module that has sub modules, well, lets say there was a new version of that module and one of the submodules was renamed or removed, well, you had no idea, but ya, this record stays around in the system table and drupal will search for this missing module, eating up cycles ,, also, left over schema information is there because a proper uninstall was not made, so to fix this, you put the missing module back (hopefully the right version) and then you can uninstall it and allow it to do a proper uninstall.

This is a very helpful feature.

This is a very helpful

UksusoFF commented 31 October 2016 at 06:41

This is a very helpful feature.
Yes i agree, but now not have any wrong deleted modules. Error anyway shows :(

Can you obtain a stack trace?

donquixote commented 31 October 2016 at 06:46

Can you obtain a stack trace?

How can i get it?

UksusoFF commented 5 November 2016 at 16:09

How can i get it?

ok, yes change record, you may need a module update or two

joseph.olstad

French

commented 31 October 2016 at 14:08

See this change record

Like donquixote says, try getting a backtrace, this will tell us which module needs updating/fixing

the other option is to search through your sites contrib modules for this:

For developers

The drupal_get_filename() API function now has a new $trigger_error parameter, which determines whether a PHP warning should be triggered if the file being searched for is missing or moved in the filesystem.

The default value is TRUE since (as noted above) an unexpected missing file usually indicates a problem that either developers or site builders need to solve, but you should set this to FALSE if you are deliberately using this function to determine whether a module or theme is missing (this is an unusual use case).

see the change record for the full explanation

Update all your modules

juankvillegas commented 27 July 2016 at 16:41

I have found that a lot of modules have updated their code to avoid this type of messages. So my suggestion is that before to start digging for a solution for a specific message, just update all the modules used in your website and almost all of the warnings, if not all of them, will disappear.

Juan Villegas
micoworker
Diseño y Desarrollo Web

I agree

CM63 commented 27 July 2016 at 17:28

I completely agree.

With themes

JennyGB commented 28 July 2016 at 12:16

Hello,

I use several sites, using different databases but same code.
I have an issue with themes...

A site X (who don't use zen) shows errors about some sub-theme used by an other site Y... Others sites doesn't show this error.

Any idea ?

Disabled modules show as missing even though uninstalled

izmeez commented 3 August 2016 at 17:40

With update to drupal 7.50 missing module warning are appearing for many modules that are present but have been disabled. They are not showing as needing to be uninstalled.

The modules are in a sub-directory sites/all/modules/contrib the same as modules that are enabled and not showing as warnings.

Examining the system table shows the filename path is correct, the status is "0" consistent with not enabled, and schema_version shows as "-1" consistent with not installed.

Neither module_missing_message_fixer or missing_module identify any problems and registry_rebuild does not fix the warnings.

The warnings can be triggered by running available updates report.

Any suggestions as to what to try next would be appreciated.

I am tempted to open an issue for drupal 7 core but wonder if something more obvious is being overlooked.

Thanks.

Read this thread

labboy0276 commented 3 August 2016 at 18:12

Read all the comments on this thread, there are numerous suggestions.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

@labboy0276 Why waste your

izmeez commented 3 August 2016 at 19:02

@labboy0276 Why waste your time with a reply that is not helpful or focused.

Yes, having read all the comments in this thread, some more than once. Including 5 by yourself that are simply promoting the module you wrote which I did in fact try and have provided feedback on the results encountered. Thought you might be interested and have something more specific to offer rather than such a wild assumption that people don't try to make use of the comments already offered.

I was hoping for some further guidance that might help me and possibly others.

Thanks.

Sorry

labboy0276 commented 3 August 2016 at 19:35

Yes I suggested you read the comments because numerous people on here are posting the same issues over and over. Self promotion of my module was not was not the intention. It was to help people posting from what I mentioned above. That is all. Moving on.

In your case, this is what I would do:

Search the code base for drupal_get_path("WITH YOUR MISSING MODULE NAME"

This can trigger the warning as well, also try the same above with single quotes as well.

Good luck

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Thanks

izmeez commented 3 August 2016 at 20:07

Thanks for the suggestion. Grep returned no results with double or single quotes.

Ok

labboy0276 commented 4 August 2016 at 13:25

The only other thing I can think of is the path is wrong for the modules in the system table. Other then that, there is no compelling reason to not uninstall a disabled module. You could either uninstall them or manually remove the entries from the system table.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Ok

labboy0276 commented 4 August 2016 at 13:25

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Thanks again

izmeez commented 4 August 2016 at 15:39

Thanks again. I am just compelled to resolve why these things happen. That's how bugs sometimes get identified.

The cleanup_tool module offered earlier also found no errors.
I modified the system table removing the line for one of the disabled modules and cleared the cache but not unexpectedly, since the module is still present and not enabled, the warning returned.
I moved the module to the traditional sites/all/modules folder and still the warning returns.

I don't know if I am the only one with the error. I am tempted to setup a fresh drupal 7.50 install and add a contrib module but not enable it to see if the warning occurs.

yes

labboy0276 commented 4 August 2016 at 16:11

there has to be a module looking for the module that is missing. That happened on one site i worked on. the drupal_get_path was the solution for me. Soemthing at bootstrap is looking for the module in question it seems and causing the error.

John Ouellet
Sales Engineering Manager
https://thinktandem.io/

Fresh install D7.50 ok

izmeez commented 4 August 2016 at 19:37

Did a fresh install of D7.50 and left a module not enabled in the modules or the modules/contrib directory and there is no problem.

Looks like I have some work cut out for me to identify the module that is causing the conflict.

Sorry about using so much bandwidth. I'll see what I can find.

Thanks.

The patch_status module causing my grief

izmeez commented 4 August 2016 at 20:12

ok, I have isolated my problem to one module, the patch_status module.
I'll move on to exploring specific issues there.

I had this error appear

petergus commented 5 August 2016 at 18:01

I had this error appear listing a few scss files as the culprit. I updated SASSY and the libraries, and was then able to track down the line with the extra offending bracket in one scss file (not one listed in the error!)

a terrible design decision

omarsidd commented 10 August 2016 at 07:39

It's a terrible design decision.

Creating a whole lot of warnings for older sites? (just because they had modules removed without an "uninstall"). Not just warnings. Persistent warnings. Bright warnings. Placed where normally serious issues go (and no, despite all the rationalization by others in this thread, if it's been fine for 40-odd releases AND it didn''t warrant an emergency fix? Then no, it's not serious).

Drupal system admins often aren't the only ones with backend access. This sort of thing (an unexpected, mysterious, persistent warning) induces panic amongst content admins who see the status report, and who think something is badly broken.

This sort of decision has an air "I have never run websites of any variety or scale" about it. Yeah, just go back to do cleanup on each old site? For what actual benefit realized for time spent? Returning to the way things were in the previous release. That's really not a goal that's worth wasting everybody cycle's on. Nor in fielding questions about the strange new error. Creating disruption for a lot of people without specific benefit is amateurish.

It shouldn't be

CM63 commented 10 August 2016 at 08:04

Hello,

Do you really have lots of old sites where people other than admin have access to the back-office? If it is the case, it is a bad design choice, definition of roles.

Software or community

bglogo commented 10 August 2016 at 08:47

I see strange persistence to defend disputed here novelty "The following module is missing from the file system. Friends, Drupal is not only software that has to be perfect. It's more than that - Drupal is a community of users that need to work easily with it.

Including the beginner users still do not know how to install and uninstall modules correctly (like me 8 years ago). Including freelancer web designers like me who work well with HTML and CSS, but are not programmers. Including people who do not know how to work with Drush or to edit MySQL databases.

After I updated several dozens of the sites to 7.50 I see that these messages are useful and it is not difficult to solve the problems, at least in the majority of cases.

However, I totally agree with omarsidd - "Creating disruption for a lot of people without specific benefit is amateurish".

Not from the perspective of perfect software, but from the point of view of the community and attracting new customers, facilitating the work of the system. From this point of view, this innovation is a big mistake.

Thanks but still seeing one last module: "content"

tomarnold2 commented 10 August 2016 at 21:39

Great article. Thank you! I used the module for removing the missing module complaints and it worked very well.

However, one warning message continues to pop-up for me:
User warning: The following module is missing from the file system: content.

To fix this I figured I'd just install the content module then properly uninstall it. Trouble is, I cannot find a drupal project for content. So then I thought maybe it was a typo somewhere, as suggested as the last resort in your article (maybe they meant "context" instead of "content"). So I did a grep for all uses of module_load_include() and searched for the use of "content". No luck.

Any other thoughts? Thank you!
Tom

Maybe Ubercart

juankvillegas commented 11 August 2016 at 01:05

I had that same error and Ubercart was the guilty one.

Anyway, if you are not using Ubercart, just update all the modules you are using and there is a great chance that the error disappears. This is because as this warnings are affecting everybody, all the module developers, at least the responsible ones, are updating their modules to avoid this.

Juan Villegas
micoworker
Diseño y Desarrollo Web

Thanks!

tomarnold2 commented 12 August 2016 at 20:59

Thank you, Juan. One more reason to stay on top of keeping my modules updated. ;-)

Same here - updating Ubercart

William H. Olesen commented 12 August 2016 at 22:43

Same here - updating Ubercart to 7.x-3.10 did the trick on the content. thingy

The following module is missing from the file system: content

mindbet commented 17 August 2016 at 02:13

I was able to get rid of this message by disabling the google_analytics_reports module, version 7.x-3.0.

I suspect it is this line:

module_load_include('inc', 'content', 'includes/module');

in the file google_analytics_reports.install

There is an update for google_analytics_reports 7.x-3.1 that does not have this code.

Hope this helps.

Update:

See https://www.drupal.org/node/2762675

Drupal 7 solution #1 worked for me

rayjames commented 11 August 2016 at 17:55

The module https://www.drupal.org/project/module_missing_message_fixer worked for me. Continuing forward. Thanks for the easy to use module labboy0276 and Kalamuna. You rock!!

Error On Installed and Active Module

zlinedavid89 commented 12 August 2016 at 20:57

Here's a situation I haven't seen brought up yet: This error is appearing in reference to a module that is installed and active. I currently have a fresh install of D7.5 (never upgraded from a previous version). The module it is referencing is a custom module, but it is installed and otherwise working properly. It is referring to a file that it says is missing, but is in the directory being referenced. I've attempted multiple cache clears, but it still persists.

Even creating new custom module produce this warning

rei commented 13 August 2016 at 03:32

I create new custom module test123 and put in sites/all/modules/test123.
visiting the module list (/admin/modules) produce this warning:
User warning: The following module has moved within the file system: test123. In order to fix this, clear caches or put the module back in its original location. For more information
this is definitely a bug.

I've seen this too... not

juankvillegas commented 16 August 2016 at 02:41

I've seen this too... not only with custom modules but with any module just added to the modules folder. The first time I load the modules page the warning is shoen... then it never appears again.

Juan Villegas
micoworker
Diseño y Desarrollo Web

same here

scotwith1t

Birmingham, AL

commented 18 August 2016 at 20:56

happens when creating new feature modules as well. as soon as you put them in place and enable, they've never been in any other location before, but this message pops up.

still not fixed!

serkan_isin commented 17 August 2016 at 07:32

User warning: _drupal_trigger_error_with_delayed_logging() (/home/www/public_html/includes/bootstrap.inc dosyasının 1128 satırı) The following module has moved within the file system: views_export. In order to fix this, clear caches or put the module back in its original location. For more information, see the documentation page..

Any suggestions? views_export is its location and thats the only error could not be fixed yet!

Error message of views_export still resides.

jorisx commented 30 January 2017 at 07:07

All caches cleared and still getting the message about "views_export"

Http://www.reloadmedia.com

Yee Gads, What a Mess

leoklein commented 17 August 2016 at 18:43

Going back to 7.44.

mmm... No!

juankvillegas commented 17 August 2016 at 19:12

That's not the solution. Eventually there will be a security update in Drupal Core and you will need to install it. Or maybe you have a new project and you should use the latest Drupal available (yes, yes... I still work with D7).

I agree with everybody that this was an awful decision... but it is done... now we must help module developers to identify the lines in their code that are generating these warning... write patches... give Drupal Core team ideas for a good fix in Drupal 7.51 (like remove the visible warnings and keep them in watchdog).

I personally have received a lot from Drupal in the past 7 years and haven't given back enough... this is a good time for all of us to return something and help to solve this issue ASAP.

Juan Villegas
micoworker
Diseño y Desarrollo Web

already possible in Drupal 7.50

David_Rothstein commented 18 August 2016 at 04:45

give Drupal Core team ideas for a good fix in Drupal 7.51 (like remove the visible warnings and keep them in watchdog).

In Drupal 7.50 the warnings are already in watchdog (and not visible elsewhere). Just make sure your site is configured not to display PHP messages to the screen, as it really should be already, and as described here (which was linked from the above documentation, the 7.50 release announcement, etc).

Or is your concern that these are showing up on development sites (that deliberately display warnings on the screen) and therefore getting in the way of other things? If so, would it help if this were a notice rather than a warning?

And yes, going back to Drupal 7.44 doesn't make much sense to me... These are just warning messages in the site logs. Drupal 7.44 had actual performance problems in those places instead.

It is not that simple

juankvillegas commented 18 August 2016 at 15:59

Just make sure your site is configured not to display PHP messages to the screen

Yes, and it is now in my "To production" check list... but clearly it was not in that check list before... and seeing all the complains about this issue, we can say that those warnings aren't disabled in a lot of websites.

So... maybe avoiding those warnings in the screen, even for websites that haven't disabled the errors, and just sending them directly to the watchdog could be an "acceptable" solution for me.

I think a good solution would be to have the warnings only on watchdog for websites updated from Drupal 7.44 or before. But keep the current behavior (screen and watchdog) for new websites.

Juan Villegas
micoworker
Diseño y Desarrollo Web

Differentiate between missing disabled and enabled modules

hs@henrikstrindberg.se commented 23 August 2016 at 08:17

A notice is a good idea:

A notice for disabled but not uninstalled modules that are missing.
A warning for enabled module that are missing.

Here's a patch

David_Rothstein commented 18 January 2017 at 20:42

I created #2844716: "Missing/moved modules" PHP warnings should be PHP notices instead with a patch to move this from a warning to a notice.

@hstrindb, I agree it makes sense to keep it as a warning in the case of a missing enabled module, but it might require larger code changes to be able to detect that case at the appropriate time. So for simplicity, the patch I posted always makes it a notice for now. (In my opinion that is still acceptable, even if not ideal.)

Ok. Back to 7.44 —how do I do that?

cgfx commented 10 September 2016 at 03:34

I just got a ton of these messages on a sandbox site I'm trying to set up, all from the regular backups from a live site which, curiously, doesn't emit any the same errors. (If it matters, I used the Restore feature of Backup & Restore, which sometimes works, but doesn't usually not work this badly.)

Right now, everything is a horrible mess, and, well, this is on the front page/every page:

<blockquote>Error message

User warning: The following module is missing from the file system: block_class. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: browscap. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: coffee. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: colorbox. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: context. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: context_layouts. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: context_ui. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: ctools. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: ctools_access_ruleset. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: ctools_custom_content. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_all_day. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_api. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_context. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_popup. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_repeat_field. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_tools. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_views. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: easy_social. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: easy_social_pinterest. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: entity. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: entity_token. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: file_entity. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: fontyourface. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: fontyourface_ui. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: fontyourface_wysiwyg. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: font_reference. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: googleanalytics. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: httpbl. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: icon. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: icon_field. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: icon_filter. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: icon_menu. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: imagecache_token. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: imagefield_crop. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: less. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: libraries. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: link. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: media. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: media_internet. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: media_wysiwyg. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_context. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_facebook. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_favicons. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_google_plus. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_mobile. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_opengraph. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_panels. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_twitter_cards. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_verification. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: metatag_views. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: mollom. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: node_reference. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: oauth_common. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: oauth_common_providerui. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: panels. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: panels_ipe. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: panels_mini. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: qpa. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: qpcache. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: querypath. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: references. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: shorten. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: shurly. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: shurly_service. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: smartcrop. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: statistics_counter. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: stylizer. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: term_depth. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: token. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: transliteration. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: twitter_post. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: user_reference. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: user_restrictions_ui. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: variable. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: views_content. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: views_ui. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: wysiwyg. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: block_class_styles. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: date_repeat. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: fontsquirrel. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: google_fonts_api. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: local_fonts. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: select_or_other. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: typekit_api. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: twitter. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: user_restrictions. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: views. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: panels_node. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: page_manager. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).
User warning: The following module is missing from the file system: icon_block. In order to fix this, put the module back in its original location. For more information, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (line 1128 of /var/www/html/includes/bootstrap.inc).</blockquote>

I really needed to not spend a huge amount of time on this. I just wanted to upload some genuine content so I could preview what a new theme might look like. Now all of that has to wait while I try to figure this mess out.

So. How do you go back to 7.44? Not certain this will solve my issue, but it might. It's not a production site, so there's no risk.

It's likely that when the

David_Rothstein commented 10 September 2016 at 04:22

It's likely that when the site was copied from production to the sandbox, all (or many?) of the contrib modules didn't come along with it. Probably that means the sandbox copy of the site is broken in other ways too... the messages you're seeing are a symptom, not a cause.

But if it's somehow not broken in other ways and you just want to hide these messages locally, you can configure the site so the messages aren't displayed on the screen (as described in the documentation above). Copying the instructions here:

As an administrator, navigate to Home » Administration » Configuration » Development » Logging and errors. Set the "Error messages to display" option to "None."

As for going back to 7.44, that doesn't sound like the right thing to do here.

I tried that, except that

cgfx commented 10 September 2016 at 08:00

I tried that, except that doesn't seem to make the bafflement go completely away:

Error message
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.
The file could not be created.

Apparently, the file could not be created. (Whatever that is.)

I'm finding that Backup and Migrate doesn't backup and/or restore everything it ought. It seems like a great tool, but in practice, really random as to whether or not it works. Not sure what to rely on. I used rsync from the live site instead, and then cleared the caches.

It must be configured

juankvillegas commented 10 September 2016 at 10:30

Backup and Migrate actually is a great and very stable tool (I'm not related at all with the module developers), but it must be configured. By default, there are no scheduled backups configured and the default configuration only backups the database, not the project files.

And... about your "The file could not be created." message. Check your sites/default/files folder permissions (maybe it is not "default" but a specific project folder). If your are working on localhost, you may change that folder and subfolders to 777 and probably everything will work.

Juan Villegas
micoworker
Diseño y Desarrollo Web

Juan is correct, Backup And

crystaldawn commented 10 September 2016 at 16:58

Juan is correct, Backup And Migrate is fairly useless in it's "default" settings. You must configure it to back up everything by selecting the "Advanced" tabs. Otherwise, you're going to be very sad when it comes time to restore and you're missing critical data. But even clicking "Advanced Backup" isnt really enough. You still need to open the other options hidden in the "Entire Site" and possibly the "PUBLIC FILES DIRECTORY BACKUP OPTIONS" fieldsets.

I have configured the

cgfx commented 10 September 2016 at 18:43

I have configured the advanced tab's options, and have scheduled "entire site" and database-only backups (both on the localhost and on NodeSquirrel). The initial migration was from one of these backups, entered via the interface. (Though it never seems to get files from sites/default/files.) Don't think that's the issue.

As I said, sometimes it works (with the OS X Server machine I used to sandbox with)—sometimes it doesn't (yesterday on an Ubuntu server install). My impression is that ours is a relatively small, largely standard site (an archive is about 188 MB compressed), so I don't know what the holdup could be.

I also checked permissions of where files are stored. All of the permissions are set to www-data www-data, no variation.

Anyway, using rsync pretty much allows my project to move forward. (On to Theming, new territory for me.)

Adminimal theme D7 issue

justinlevi commented 19 August 2016 at 18:04

yeah, I just got this with a fresh D7 install and adminimal_theme as well.

Report a bug

CM63 commented 23 August 2016 at 08:29

Hello,

If really, if it is a fresh D7.50, it can be seen as a real bug of the 7.50, you may consider reporting a bug to the git.
I would be surprised if it has not been already done, because you are not the first one. Once again , we are speaking about shutting a 7.50 instance from nil, not an upgrade from the 7.44 .

Error message on NEW module download

el_reverend commented 22 August 2016 at 00:23

I get the following error message on a new dl of a module. I have not had that module installed and hated to test it. WTF! Now I have to check the site with a new live db and then deploy code HOPING it does cause a check on prod? Thanks for that helpful message.... :|

The following module has moved within the file system: <em class="placeholder">commerce_popular_products</em>. In order to fix this, clear caches[warning]
or put the module back in its original location. For more information, see <a href="https://www.drupal.org/node/2487215">the documentation
page</a>. bootstrap.inc:1128

Quick fix

Maurice M. commented 23 August 2016 at 07:51

I didn't have time to fix these issues. I got errors about modules I don't even have in my project. So I just installed the modules without enabling them. The errors are gone now... Not the best method I know.. Hope it helps someone.

Ho yes it is the best (or the first) thing to do

CM63 commented 23 August 2016 at 08:19

Hello,

Ho sure it is, almost the first thing to do, if not the best. The "bug" does not come from Drupal but from old modules that had been badly uninstalled in the past, in the development files themselves, even if you had never installed those modules yourself. So if installing them, without activating them, fix the problem, you have nothing else to do. If you like you may try uninstalling them, see if the message comes back, if so, install again, and don't touch anything more.

See you

Does this cover all cases of these notices appearing?

logicp commented 24 August 2016 at 13:06

As far as I can tell, these notices display themselves even upon enabling a new module (without uninstalling).

You don't need to enable it

juankvillegas commented 24 August 2016 at 13:27

Just add a new module to the modules folder, then go to the modules list and there it is the warning even when you haven't enabled it.

Juan Villegas
micoworker
Diseño y Desarrollo Web

Logs on missing files from files/ directory

manasiv commented 25 August 2016 at 11:16

Seeing this message on missing files from the files directory as well. Is there an option to disable this check?

It is different

juankvillegas commented 25 August 2016 at 12:52

Missing files give you other type of warnings. It is not related with this issue. It is maybe an image that doesn't exist, or a CSS or JS file that is really missing and some module is needing it.

Can you paste here the error you are seeing?

Juan Villegas
micoworker
Diseño y Desarrollo Web

You're right, this happens

logicp commented 30 August 2016 at 12:41

You're right, this happens even just by having a new module. Is there agreement that this is a bug?

Deleted!

waqarit commented 29 August 2016 at 07:40

Deleted!

jquery_ui missing?

roderickgadellaabsl commented 29 August 2016 at 10:26

Hi,

I updated to 7.50 and everything seemed fine (after I used the Missing Module Message Fixer. But after using the site for a ~week I found the following issue on one of the pages (it's a custom block module):

The following module is missing from the file system: jquery_ui

Which is weird because jquery_ui comes built-in with Drupal 7. Missing Module Message Fixer doesn't find it (says "no missing modules found") and when I do a manual search in the database (SELECT * FROM system WHERE name = 'jquery_ui') I get zero results. I even checked it (semi-)manually by selecting all modules and searching for jquery_ui. It's nowhere to be found.

For completeness, I do have the jQuery Update module and jquery ui actually works because I have a functional datepicker.

Solved!

roderickgadellaabsl commented 30 August 2016 at 08:44

I had some old code in the module that added the ui.datepicker css file manually but add_library() already does that. So the add_css() method pointed to a module that drupal couldn't find ("jquery_ui"). Before 7.50 this simply didn't cause an error.

Missing profile error with 7.50 upgrade

Ireto Okorodudu commented 31 August 2016 at 09:46

I too like many others got annoying error messages with the new 7.50 upgrade. The Missing Module Message Fixer did clear all the errors except one relating to a missing profile. The solution I used was to cheat. I simply copied the standard profile and renamed it to the name of the missing profile and renamed the .info file. It worked perfectly. The missing profile was in fact a custom profile which had been supplied to us by a 3rd party. Unfortunately we could not get in contact with them. The only thing is that when upgrading in the future we will have to remember to copy across the profile folder.

I believe this is exactly

logicp commented 7 September 2016 at 16:33

I believe this is exactly what is happening in my situation. Unfortunately, we don't have the option of renaming the profile.

Is there any movement on this issue? Have we determined that there are bugs accompanying this new 'feature'?

If your site is missing its

David_Rothstein commented 9 September 2016 at 17:21

If your site is missing its install profile, that's a separate and older problem - nothing to do with Drupal 7.50. See #1170362: Install profile is disabled for lots of different reasons and core doesn't allow for that for more information on that (although that issue mostly focuses on sites that have their install profile disabled rather than disappeared from the filesystem entirely).

Drupal 7.50 does trigger warnings in this scenario that would not have been triggered before though.

Excuse the confusion if I

logicp commented 9 September 2016 at 18:12

Excuse the confusion if I caused any, my site has its install profiles configured correctly and was using the appropriate one (in my case it's a wetkit site).

Terrible design decision,

Welsby commented 7 September 2016 at 16:15

Terrible design decision, this will result in users who can't spend considerable time fixing this low priority problem, to mentally blank out the error message region.

Why could this not have been added in the status report screen alongside the other suggestions?

At least allow us to disable in a future version please.

You can already configure

David_Rothstein commented 9 September 2016 at 17:25

You can already configure these messages to go to the logs only (just like any other notice/warning), as described in the documentation above and elsewhere. Is there a reason that doesn't work for you?

Putting something about this on the status report page could make sense, but the issue can be triggered at random times and there's no foolproof way to proactively check for it on a site... so the status report would not be able to always get it right without a lot of effort.

David, while "logging" may

crystaldawn commented 9 September 2016 at 18:28

David, while "logging" may be out of scope for the "Status" page, there is another feature in Drupal that does this already which the status page could easily Link to or Leverage in someway with next to no effort at all. That is the watchdog table and it's filtering capabilities (which you already mentioned, but didnt really connect the dots on how that could be leveraged into status page). Why not just add a small 2 line thing to the status page that checks to see if any entries exist in watchdog, and if so, provide Links back to this page as well as the actual Watchdog entries themselves. Seems to make sense to me. No need for these to clutter up drush or the warning/error space.

That would hardly take "a lot of effort" :) The only thing left to think about would be how would we want to clear those. The most logical answer to that is to again use the watchdog clear feature. It's not ideal, but it would at least function until better solutions on how to clear it could be worked on. I think the idea should be to completely eradicate the current warning method and simply log it to watchdog and then let a contrib module deal with slapping it on the status page. Once module is working great, bring it into core.

That would not work with

David_Rothstein commented 9 September 2016 at 19:35

That would not work with Syslog which many people use for logging.

Switching these to plain watchdog messages (with or without something accompanying that on the status report page) is certainly possible, but when I suggested that before I think the consensus in response was that development sites need a louder warning than that (particularly for developers to catch mistakes in their code right away, in the case where that triggers it, but for individual sites too). Not sure if the consensus on that has changed in the meantime.

Module Missing Message Fixer Module

mfuller526 commented 15 September 2016 at 19:14

This works! Module missing message fixer module

Missing message fixer module was the solution

ressa commented 26 September 2016 at 14:20

The Module missing message fixer module fixed it for me as well. I had some old and (I thought correctly) un-installed modules lingering in the database. It's good to know they are now removed, so that Drupal doesn't have to scan the entire file system for them at every page load.

A big Thank you! to the Drupal core team for this initiative, highlighting this potentially resource-hogging issue to all us Drupal users.