Updating to 7.50 breaks the tests:
The following module is missing from the file system: panopoly_demo. [error]
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/travis/build/panopoly/drupal-7/drupal/includes/bootstrap.inc).
The following module is missing from the file system: panopoly_news. [error]
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/travis/build/panopoly/drupal-7/drupal/includes/bootstrap.inc).
The following module is missing from the file system: panopoly_faq. [error]
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/travis/build/panopoly/drupal-7/drupal/includes/bootstrap.inc).
Installation exits with a non-zero error code so it errors out, although, it does seem as though it actually succeeded in installing!
See https://travis-ci.org/panopoly/panopoly/jobs/144435388
Original issue summary
Last week, Drupal 7.50 was released:
https://www.drupal.org/project/drupal/releases/7.50
It's a non-security release, so we usually wait for a bit to avoid problems (which saved us in the past ;-)). The fallout appears to be minimal - the only thing I can find is:
#2762705: Slick view and Drupal 7.50 new issue
It's potentially annoying, but actually a good thing to know about so, I'm not worried. :-)
Comment | File | Size | Author |
---|---|---|---|
#26 | panopoly_search-apps-d750-2765427-26.patch | 484 bytes | dsnopek |
#21 | panopoly_core-apps-d750-2765427-21.patch | 427 bytes | dsnopek |
Comments
Comment #3
dsnopekCommitted!
Comment #5
dsnopekUpdating to 7.50 breaks the tests:
Installation exits with a non-zero error code so it errors out, although, it does seem as though it actually succeeded in installing!
See https://travis-ci.org/panopoly/panopoly/jobs/144435388
Comment #6
dsnopekHere's the patch.
Comment #7
humansky CreditAttribution: humansky as a volunteer commented@dsnopek, how soon can we expect a fix for this? The reason I ask, we released an update to our distro (including 7.50) on our stage environment today and I experienced this issue when running `drush updb`. Do you think I need to rollback before our changes goes to production next week? How critical are these warnings? Also, let me know if you need any help.
Comment #8
praveen_91 CreditAttribution: praveen_91 commentedyou can use this module https://www.drupal.org/project/missing_module for remove or disable your missing module
after install module check your drupal report goto admin/reports/status , and find out "Check for missing modules in filesystem" then you can remove or disable your missing module using clicks
thanks.
Comment #9
dsnopek@humansky: Since this isn't a security update (just bug fixes and features) and I don't have a client who needs 7.50, this is really a low priority for me. As far as I know, the warnings don't actually hurt anything in a running site, but they do break our tests and we can't have broken tests because it could hide other problems. As far as whether you need to rollback, that really depends on testing of your application - if you don't see any issues, it could be fine? That said, we still haven't been able to run the Panopoly test suite because of these problems.
Comment #10
humansky CreditAttribution: humansky as a volunteer commented@dsnopek, @prabin91's recommendation for using "missing_module" worked like a charm. So I don't think I need to roll back to 7.44. We should be good for now. If anything, perhaps "missing_module" should be part of Panopoly Core and part of the upgrade process. But that might be overkill, since you've always been really good at cleaning up unused modules with hook_update_N.
Comment #11
praveen_91 CreditAttribution: praveen_91 commentedyes i agree with @humansky
Comment #12
dscoop CreditAttribution: dscoop at Cooper Webdesign commentedDoes anyone know if these issues gets fixed in 7.51? After update to 7.50 I also get the same error. I also experience that some of my old custom themes doesnt work now.
Comment #13
Jon Nunan CreditAttribution: Jon Nunan at Flight Centre Travel Group commentedI don't think adding missing_module is the answer here.
I did some poking around and it seems to be a problem with how the 'apps' module generates its apps manifest.
In particular this line (apps.manifest.inc:527):
The module_invoke is looking for the modules from the app server that aren't present. In pre 7.50 world the $info would just be set to an empty array, but now using module_invoke like that throws an error as Drupal attempts to load a file that isn't there. I'll keep looking but I think the fix will be for the app module.
Edit: added a patch here: https://www.drupal.org/node/2753413#comment-11655937
Comment #14
dsnopekThanks, your apps patch looks good! If you can make a patch to panopoly_core.make that adds that patch to panopoly I'll kick off a test build. :-) Otherwise, I'll get around to setting that up myself when I have time.
Comment #15
Jon Nunan CreditAttribution: Jon Nunan at Flight Centre Travel Group commentedI forked and tried it myself, unfortunately it fails. I think there is more to do in the apps patch but haven't had a chance to debug yet.
Comment #16
dsnopekHere's another issue that might be related:
#2765117: Profiles directory distros, and "The following module is missing from the file system..." warnings
Comment #17
delacosta456 CreditAttribution: delacosta456 commentedhi
i dowloaded the dev version of Panopoly and have seen that the latest version of Drupal in , is 7.44 .
Now the module interface is keeping notifying me about security release and that i shoukd manually update to 7.52.
I would like to know if i should wait or update
thansks
Comment #18
dsnopekSince Drupal 7.52 is a security update, I'm going to push this forward (in #2828241: Upgrade to Drupal 7.52) even though it breaks the tests and installation via Drush. Re-working this issue to be about fixing those issues, since the upgrade is going forward anyway.
Comment #19
dsnopekReplaced issue summary with info from comment #5
Comment #20
dsnopekHere's a new patch to test the apps patch
Comment #21
dsnopekGah, stupid type-o
Comment #22
dsnopekHrm. The patch reduces the number of errors down to just 1:
But we're still getting the error for panopoly_demo. Maybe the difference is that we actually attempt to enable it during installation?
Comment #23
delacosta456 CreditAttribution: delacosta456 commentedhi dsnopek and all guys
thanks for your hard work and keeping us update.
Still on Panopolly with D7 7.44.(offline in dev off course) .. we will be expecting the stable upgrade .
thanks
Comment #24
dsnopekComment #25
dsnopekHere's the most important part of a stack trace of this issue:
What's going on is a circular dependency that involves search_api.
'apps' is calling
system_rebuild_module_data()
which will eventually write the new information about 'panopoly_demo' to the 'system' table. However, before it gets to that point,hook_system_info_alter()
is called, andsearch_api_system_info_alter()
tries to discover if the module implementshook_search_api_item_type_info()
which leads todrupal_get_filename('module', 'panopoly_demo')
-- and that's what's triggering the error, because there is no information about 'panopoly_demo' on the 'system' table. Aftersystem_rebuild_module_data()
completes, the 'system' table will be updated, so subsequent calls will work, but the error is registered anyway, breaking drush.I'm trying to determine if what 'search_api' is doing is actually valid, and it's something 'apps' needs to account for, or if we need to update 'search_api' to only check for the hook if the module is enabled or something like that.
Comment #26
dsnopekHere's a patch that modifies search_api - gonna try it on Travis
EDIT: Here's the Travis build: https://travis-ci.org/panopoly/panopoly/jobs/185555341
Comment #27
dsnopekWoohoo! Travis is passing :-) Committed! Thanks, Everyone!
Comment #28
dsnopekComment #29
delacosta456 CreditAttribution: delacosta456 commentedhi dsnopek
Thanks for the hard work
I just successfully upgrade from Panopoly dev (with Drupal 7.44) to Panopoly 1.41 (Drupal 7.52).