Answers.Body: <p>Can you make sure the directory path defined for $civicrm_root of your site matches with DocumentRoot mentioned in your apache2/nginx conf setting. They should match with each other.</p>
  
  <p>The other option is to set 'CiviCRM Resource URL' in Resource url setting to <a href="http://www.mysite.org/public_html/wp-content/plugins/civicrm/civicrm/" rel="nofollow noreferrer">http://www.mysite.org/public_html/wp-content/plugins/civicrm/civicrm/</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T06:52:26.003Z
Answers.Text: DocumentRoot: /home/user_name/www/mysite.org/public_html
  
  $civicrm_root: /home/user_name/www/mysite.org/public_html/wp-content/plugins/civicrm/civicrm/
  
  So that looks OK, no?
  
  The resource URL setting is read-only.
Answers.UserDisplayName: mc_burger
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T08:49:00.587Z
Answers.Text: OK, adjusted the settings.php file so that I could change the resource URL -- set it as suggested here and then updated the paths. Same result (i.e., still showing a 404 error).
Answers.UserDisplayName: mc_burger
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T10:41:29.560Z
Answers.Text: I'm thinking it may make sense to wipe out everything in plugins & uploads, install CiviCRM as a new plugin, and then restore the db. Would this work? Or is it pointless, as I can't really imagine the resource paths getting any clearer than they are? Maybe I'm barking up the wrong tree, here.
  
  Or I revert to 5.19, with the scary security warning? A bit lost . . .
Answers.UserDisplayName: mc_burger
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-14T10:52:35.133Z
Answers.Text: For comparison, the menu .css that's not found (404): Request URL:https://mysite.org/home/user/www/mysite.org/public_html/wp-content/uploads/civicrm/persist/contribute/dyn/crm-menubar.51fcaccee502d3f65ba2d9b8166e391b.css
  
  VS
  
  
  The rest of everything else, loading from the plugin directory: Request URL:https://mysite.org/wp-content/plugins/civicrm/civicrm/css/civicrm.css?r=VGCMB
  
  Shouldn't these be the same paths, up to /plugins or /uploads?
Answers.UserDisplayName: mc_burger
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-13T13:25:04.920Z
Answers.LastActivityDate: 2019-12-13T13:25:04.920Z
Answers.UserDisplayName: Pradeep Nayak
Answers.Body: <p>The definition of $civicrm_root was indeed the problem; in my settings.php (which had been working for a while) the path used Siteground username (as does DocumentRoot), whereas this should be replaced by the generic 'customer.'</p>
  
  <p>How I got there: </p>
  
  <p>It was obvious that something was wrong with the Resource URL, but I couldn't figure it out (as the comments should make clear). So I reverted to 5.19.2, made a full-site backup, and then uninstalled CiviCRM completely: plugins/civicrm, uploads/civicrm, and the db. Then ran a fresh install to autogenerate a new settings.php file, which I downloaded.</p>
  
  <p>Then I restored the full-site backup &amp; ran the CiviCRM update as normal, except that I put the newly-generated settings.php file in place before upgrading the db. This worked, fortunately, and the only difference between the settings files was the one described above.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-15T07:37:38.457Z
Answers.LastActivityDate: 2019-12-15T07:53:12.727Z
Answers.LastEditDate: 2019-12-15T07:53:12.727Z
Answers.UserDisplayName: mc_burger
Body: <ul>
  <li>Wordpress 5.3.1 (on Siteground)</li>
  <li>[upgrading from CiviCRM 5.19.2 to] CiviCRM 5.20.1/2</li>
  </ul>
  
  <p>Apart from a (quite lengthy) list of templates that might be affected by the db upgrade, this process goes as expected. But upon reloading, I lose the CiviCRM menus and get, instead, the weird mile-long mess at the bottom of the page. </p>
  
  <p>I can confirm a 404 error on the crm-menubar css, and I can also see that the path to that file has changed from the previous installation. The previous path had been:</p>
  
  <blockquote>
    <p>www.mysite.org/public_html/wp-content/uploads/civicrm/persist/contribute/dyn/crm-menubar.blahblah.css</p>
  </blockquote>
  
  <p>in version 5.20.2, it is:</p>
  
  <blockquote>
    <p>www.mysite.org/home/user_directory/www/mysite.org/public_html/wp-content/uploads/civicrm/persist/contribute/dyn/crm-menubar.blahblah.css</p>
  </blockquote>
  
  <p>So I've changed the $civicrm_root (in the settings file) to:</p>
  
  <blockquote>
    <p>/home/user_directory/www/mysite.org/public_html/wp-content/plugins/civicrm/civicrm/</p>
  </blockquote>
  
  <p>But I'm still getting the 404. </p>
  
  <p>I have:</p>
  
  <ul>
  <li>double checked the directory permissions (though it isn't clear why these might have changed)</li>
  <li>cleaned up the caches and updated the paths</li>
  <li>read about a whole lot of similar cases, here</li>
  </ul>
  
  <p>This isn't (yet) a crisis or anything, but I do keep reverting back to the previous version, as it's a lot pleasanter to deal with (though the security warnings are working as they should, and I'd really like to get this patch).</p>
  
  <p>I suspect that this is related to resource URLs, but I'm not sure what additional steps to take.</p>
  
Tags: <wordpress><upgrade><menu><resource-urls>
Title: Menus disappear on update to 5.20.2 (Wordpress)
ThreadText: # Menus disappear on update to 5.20.2 (Wordpress)
  
  (Asked by: username_0 on 2019-12-13)
  
  * Wordpress 5.3.1 (on Siteground)
  * [upgrading from CiviCRM 5.19.2 to] CiviCRM 5.20.1/2
  
  Apart from a (quite lengthy) list of templates that might be affected by the db upgrade, this process goes as expected. But upon reloading, I lose the CiviCRM menus and get, instead, the weird mile-long mess at the bottom of the page.
  
  I can confirm a 404 error on the crm-menubar css, and I can also see that the path to that file has changed from the previous installation. The previous path had been:
  
  > www.mysite.org/public\_html/wp-content/uploads/civicrm/persist/contribute/dyn/crm-menubar.blahblah.css
  
  in version 5.20.2, it is:
  
  > www.mysite.org/home/user\_directory/www/mysite.org/public\_html/wp-content/uploads/civicrm/persist/contribute/dyn/crm-menubar.blahblah.css
  
  So I've changed the $civicrm\_root (in the settings file) to:
  
  > /home/user\_directory/www/mysite.org/public\_html/wp-content/plugins/civicrm/civicrm/
  
  But I'm still getting the 404.
  
  I have:
  
  * double checked the directory permissions (though it isn't clear why these might have changed)
  * cleaned up the caches and updated the paths
  * read about a whole lot of similar cases, here
  
  This isn't (yet) a crisis or anything, but I do keep reverting back to the previous version, as it's a lot pleasanter to deal with (though the security warnings are working as they should, and I'd really like to get this patch).
  
  I suspect that this is related to resource URLs, but I'm not sure what additional steps to take.
  
  **Tags:** wordpress, upgrade, menu, resource-urls
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2019-12-15. Score: 4 | Accepted answer
  
  The definition of $civicrm\_root was indeed the problem; in my settings.php (which had been working for a while) the path used Siteground username (as does DocumentRoot), whereas this should be replaced by the generic 'customer.'
  
  How I got there:
  
  It was obvious that something was wrong with the Resource URL, but I couldn't figure it out (as the comments should make clear). So I reverted to 5.19.2, made a full-site backup, and then uninstalled CiviCRM completely: plugins/civicrm, uploads/civicrm, and the db. Then ran a fresh install to autogenerate a new settings.php file, which I downloaded.
  
  Then I restored the full-site backup & ran the CiviCRM update as normal, except that I put the newly-generated settings.php file in place before upgrading the db. This worked, fortunately, and the only difference between the settings files was the one described above.
  
  
  ---
  
  ### Answer by username_1 on 2019-12-13. Score: 1
  
  Can you make sure the directory path defined for $civicrm\_root of your site matches with DocumentRoot mentioned in your apache2/nginx conf setting. They should match with each other.
  
  The other option is to set 'CiviCRM Resource URL' in Resource url setting to <http://www.mysite.org/public_html/wp-content/plugins/civicrm/civicrm/>
  
  > **Comments:**
  > **username_0**: DocumentRoot: /home/user_name/www/mysite.org/public_html  $civicrm_root: /home/user_name/www/mysite.org/public_html/wp-content/plugins/civicrm/civicrm/  So that looks OK, no?  The resource URL setting is read-only.  
  > **username_0**: OK, adjusted the settings.php file so that I could change the resource URL -- set it as suggested here and then updated the paths. Same result (i.e., still showing a 404 error).  
  > **username_0**: I'm thinking it may make sense to wipe out everything in plugins & uploads, install CiviCRM as a new plugin, and then restore the db. Would this work? Or is it pointless, as I can't really imagine the resource paths getting any clearer than they are? Maybe I'm barking up the wrong tree, here.  Or I revert to 5.19, with the scary security warning? A bit lost . . .  
  > **username_0**: For comparison, the menu .css that's not found (404): Request URL:https://mysite.org/home/user/www/mysite.org/public_html/wp-content/uploads/civicrm/persist/contribute/dyn/crm-menubar.51fcaccee502d3f65ba2d9b8166e391b.css  VS   The rest of everything else, loading from the plugin directory: Request URL:https://mysite.org/wp-content/plugins/civicrm/civicrm/css/civicrm.css?r=VGCMB  Shouldn't these be the same paths, up to /plugins or /uploads?  
  
  ---
  
  