AnsweredAssumed Answered

Going to Existing_{PDF Name} in upgraded Sugar 7.6 causes browser error

Question asked by Richard Coleman on Jan 11, 2016
Latest reply on Jan 14, 2016 by Richard Coleman

I can't seem to find anyone else who has had this issue, and hoping someone here can help.


We've recently started upgrading sites from 6.5 to 7.6 and as part of that, the previous PDFs from 6.5 have carried over in the correct format as per the following help document:


However, I get invalid response errors when attempting to go to the links that previously worked, i.e:



Firefox just returns an error 500, but Chrome proivides the following:


Failed to load resource: net::ERR_INVALID_RESPONSE http://localhost:800/site/index.php?module=Quotes&record=bffcc70f-a584-8995-79b0-566abd780721&action=sugarpdf&sugarpdf=…


FATAL[2016-1-11 12:0:31]: Uncaught SecurityError: Blocked a frame with origin "http://localhost:800" from accessing a cross-origin frame. at http://localhost:800/site/cache/javascript/base/components_51fe3898265e8a9a2cfbc43aac999ded.js on line 2740e.augment.ConsoleWriter.write @ sidecar.min.js?v=QX1PgjHxZnlDUiOVZ57yPQ:40

components_51fe3898265e8a9a2cfbc43aac999ded.js:2740             sidecar.min.js?v=QX1PgjHxZnlDUiOVZ57yPQ:40


Uncaught SecurityError: Blocked a frame with origin "http://localhost:800" from accessing a frame with origin "null".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of "data". Protocols must match.


Is this an inherent bug in 7.6? Or have I just not set something somewhere?