Hello dear colleagues.

Yesterday I updated a Drupal 8 site to 5.35.1. Afterwards many of menu URLs become replaced/injected with a "civicrm/a/#" string, for example domain.tld/civicrm/a/#/mailing/new or domain.tld/civicrm/a#/status; and the UI returns a blank page, not a white screen, but a page with no CiviCRM body content (see attached image).

Once this occurs the CiviCRM menu system is no longer active (clicking on any other CiviCRM menu does nothing).

I have also now done a net new composer based install (new o/s path and new DB) this time on Drupal 9 CiviCRM 5.35.1, and precisely the same problem occurs.

This is a CPanel Centos VPS server.

Your kind help is most appreciated.

'blank screen'

  • Check the browser console for javascript errors. – Demerit Apr 5 at 23:00
  • Yup, an error: GET domain.tld/sites/default/files/civicrm/persist/contribute/dyn/… net::ERR_ABORTED 404 Similar files are present, but not the one called for: ./sites/default/files/civicrm/persist/contribute/dyn/ contains these files angular-modules.734b336b53a89d35f086d1ec2725ff98.json angular-modules.a457cd187bd83f4d364e75f64e31a4fa.js angular-modules.fad2cb417fc3a1d78b05c08b3b425667.json crm-menubar.f296fb9639f644da7a6b92ebafc965ef.css index.html – Dave Gould Apr 5 at 23:31
  • The sought after file angular-modules.257675892968fd001e376109006e4b65.js does not exist on the server o/s anywhere. So one has to think this is not due only to a misdirected resource URL. – Dave Gould Apr 6 at 0:22
  • I have set file permissions as root with these scripts, then flushed caches, reset resource URL's etc. The problem persists. cd /home/domain/www-cmnty-drupal/web chown -R domain:nobody . find . -type d -exec chmod u=rwx,g=rx,o= '{}' \; find . -type f -exec chmod u=rw,g=r,o= '{}' \; cd /home/domain/www-cmnty-drupal/web/sites find . -type d -name files -exec chmod ug=rwx,o= '{}' \; for d in ./*/files do find $d -type d -exec chmod ug=rwx,o= '{}' \; find $d -type f -exec chmod ug=rw,o= '{}' \; done – Dave Gould Apr 6 at 3:21

I have repeated the new install, this time including this:

composer config extra.enable-patching true

The site now completely renders UI contents, such as the new mailing page or the status page.

So then, going to the troubled upgrade site, having first configured the install with these composer configurations:

composer config extra.enable-patching true

composer config minimum-stability dev

composer config prefer-stable true

composer require civicrm/civicrm-asset-plugin

composer require civicrm/civicrm-{core,packages,drupal-8}

and then again:

composer update

composer civicrm:publish

The upgrade site is now working.

  • Ah - that’s in the instructions :-) I figured you were troubleshooting beyond the instructions! – KarinG - Semper IT Apr 6 at 21:31

This typically helps with angular caching issues -> [it's a cache clear of sorts] Administer -> System Settings -> Asset Caching -> Disable

If that worked -> toggle back to -> Auto

Sometimes I have to re-run composer civicrm:publish (some bower assets - only some - most were there) - were just not there post upgrade.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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