CiviCRM Community Forums (archive)

When a logged in CiviCRM user selects View or Edit for a Subscription form, the new window is blank, and the error message is "Network Error: Unable to reach the server. Please refresh this page in your browser and try again." See the attached screen clip.

We encountered this error first in 4.5.2 and now in 4.5.3.  It happens in Firefox, IE, Chrome; on Vista and Windows 7, on a multitude of different computers in different cities in Canada. I am in another city, so can't actually sit down with the users experiencing the problem. On my computers - Windows 8.1, Vista, an iPhone (Safari) and an old Android phone - as well as other computers that I have tried this on (public library, my wife's) I never get the problem.

I can sign on as one of the other users, and I still don't get the problem. They can sign on as me, and they still get the problem.

The easiest way to get to the problem is to login (it's a Drupal site), go to CiviCRM, click on any contact who has a subscription (we're a magazine), then click on either the View or Edit link associated with a subscription. Immediately, the new window pops up blank, with the error message.

There are a number of "Network Error" threads here, but none of them seem quite like this. If you can point me to one that is like this, or can suggest some more testing we can do to help narrow this down, thank-you. There is nothing in the error message to suggest it's an Ajax issue, but some of the other threads point to Ajax. I don't know how to test this.

All help is welcome. This is a show stopper - we can't conduct business at the moment. Thank-you.

Coleman - Thank-you so much for your quick reply. Please tell me which browser you would like us to use, and the steps required to use the console, I will get someone to duplicate the error for us. (I can't produce the error on any of my machines.)

Here is an error message. I have replaced the actual domain name and user with "mydomain" and "myuser". Hope that's okay.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://crmws.mydomain.ca/index.php?q=civicrm/contact/view/membership&action=view&reset=1&cid=4&id=2789&context=membership&selectedChild=member&snippet=json. This can be fixed by moving the resource to the same domain or enabling CORS.

Looking into the same origin policy and cross origin requests, I think I understand what that's about, in general, but certainly not specifically. Nor can I figure out how it plays out when one bunch of computers and phones and browsers area able to process these View and Edit requests and another other set of clients encounter the blank windows and "Network Error" messages.

In the forums I did see a note, probably from you, Coleman, talking about ensuring consistency between "admin/system settings/directories" and "admin/system settings/resource urls'. Ours are inconsistent, as shown here. Which should be changed? Will it make a difference?

settings.civicrm.php contains a base url of http://crmws.mydomain.ca/'

"admin/system settings/directories" looks like this:

• Temporary Files - /home/myuser/crmws/sites/default/files/civicrm/upload/
• Images - /home/myuser/crmws/sites/default/files/civicrm/persist/contribute/
• Custom Files - /home/myuser/crmws/sites/default/files/civicrm/custom/
• Custom Templates - /home/myuser/crmws/sites/default/files/civicrm/templates custom/
• Custom PHP Path Directory    - blank
• CiviCRM Extensions Directory - blank

"admin/system settings/resource urls" looks like this:

• CiviCRM Resource URL - http://crmws.mydomain.ca/sites/all/modules/civicrm
• Image Upload URL - http://crmws.mydomain.ca/sites/default/files/civicrm/persist/contribute/
• Custom css URL - blank
• Extension Resource URL - blank

   

Thanks again. Arthur

If I understand, you are suggesting that the error message - "Cross-Origin Request Blocked: The Same Origin Policy ..." is probably unrelated to what's in the administration configuration settings which I noted above? I don't think we'll have any http://www ... instances because CiviCRM is configured as a subdomain already (crmws.mydomain.ca) we wouldn't have put a www in front of that because it's too unwieldy.

Is there anything in the error message that you can use to point us to a possibly source of the problem, or the next step in diagnosing the problem?

Thanks.

Problem solved. Somewhat embarrassing, because in the end it proved to be so simple: users for whom it worked were working in the URL http://crmws.mydomain..., and users for whom it did not work (blank screen, error message) were working in the URL http://www.crmws.mydomain .... Thanks, Coleman, for the advice.