Webpage Widget-showing in preview but not on display

  • 1
  • Question
  • Updated 3 years ago
I have a customer that is hosting a site on there own server and when I input the address on the
webpage widget the website does not display properly.  But when I type in the address in chrome it works and it even works when it's in the preview window.
Photo of Alim Vellani

Alim Vellani

  • 260 Points 250 badge 2x thumb

Posted 3 years ago

  • 1
Photo of Shea

Shea, Official Rep

  • 5,188 Points 5k badge 2x thumb
Hi Alim, 

Could you please let me know what the URL is and the name of the presentation in Rise Vision. I'll take a look.

Thanks,
Shea
Photo of Alim Vellani

Alim Vellani

  • 260 Points 250 badge 2x thumb
Photo of Shea

Shea, Official Rep

  • 5,188 Points 5k badge 2x thumb
Hi Alim,

I just wanted to let you know we deployed an update that should solve the problem you were experiencing. Can you please let me know if it works now? 

Thanks,
Shea
Photo of Shea

Shea, Official Rep

  • 5,188 Points 5k badge 2x thumb
Hi Alim,

It looks like it is something on your end. In the console I see the error:

"Failed to clear temp storage: It was determined that certain files are unsafe for access within a Web application, or that too many calls are being made on file resources. SecurityError "

You can read more on the error here: https://developer.mozilla.org/en-US/docs/Web/API/FileError 

Unfortunately there is nothing we can do to resolve this, you'll have to speak with your customers developers . 

If you have any questions please let me know.

Thanks,
Shea

(Edited)
Photo of Shea

Shea, Official Rep

  • 5,188 Points 5k badge 2x thumb
Just to add to what I said earlier. This is from our developers: 

Our Web Page Widget appends a cache buster to the end of the URL provided to the Widget so that it will always load/reload latest version of the website. It appears that the cachebuster is causing a problem when applied to the URL for the <iframe> to load because the URL does a redirect to an authentication url (.aspx).  Unfortunately there is no workaround because the cachebuster is necessary.

Let me know if you have any questions.

Thanks,
Shea