I installed D8 first then Civi and it seems like it is working if I manually put the url comonents after the http://focal-civi.domain.org/civicrm/{manually-add} but the menu is not showing up.

Anyone have any hints?

No Menu

  • Do you have any errors in the browser dev-tools console? What do you have in civicrm.settings.php for $civicrm_root and overrides for $civicrm_paths - does it match your actual paths?
    – Demerit
    Jul 11, 2020 at 17:20
  • I'll check those settings and logs and report back. Of note, if I use the RoundEarth as the core then it works but if I use the Drupal-Reco Base then it doesn't.
    – HeneryH
    Jul 12, 2020 at 0:46
  • Oh man, there are a lot of errors when I click the CiviCRM menu..,.,. A lot. Trying to figure out how to post it...
    – HeneryH
    Jul 26, 2020 at 3:36
  • Here is a google doc with the error log docs.google.com/document/d/…
    – HeneryH
    Jul 26, 2020 at 3:43
  • You can also edit your original question and paste there but what it looks like is each of those resources is returning drupal's error page (hence the text/html). If you visit one of the links do you see the actual error? Or in drupal watchdog?
    – Demerit
    Jul 26, 2020 at 4:24

4 Answers 4


I think I just responded to you on GitLab. From what you described there I think you may need to:

composer civicrm:publish

to populate web/libraries

  • I tried that with no help. I can get the menu to work loading Civi on top of a standard D8 install but at least two distributions (Lightning and Varbase) cause the menu to stop working. It looks like the menu pops up for a very short time then the standard Drupal Toolbar slides up over top of it.
    – HeneryH
    Jul 26, 2020 at 3:33
  • This helped me populate the /web/libraries/civicrm folder. First, you have to make it writable for the user running the group. Thanks +1
    – salah-1
    Nov 1, 2021 at 14:10

This problem was (I think) related to a permission problem with the plug-in not having permissions to copy the libraries from a parent directory to the doc-root directory.

Solved for me. Hope this helps someone else.


Also for me (in addition to directory permissions) is the fact that some distributions use different names for their docroot directory.

Core uses ./web Varbase uses ./docroot OpenSocial uses ./html

This can be accounted for if you add this to the composer.json in the extras section

 "civicrm-asset": {
     "path": "***docroot***/libraries/civicrm",
     "url": "/libraries/civicrm"

I had something similar on a Backdrop site and it turned out to be caused by the way I had set up the directory structure.

I was trying to get fancy using a symlink and the server was using the symlink as the website's document root, but in the civicrm.settings.php I was pointing to the other directory. Changing the settings file to also point to the symlink solved it.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.