Folder.Browser HTML Page Issue (OTCS ticket 2940924)

Question from customer:

"I’m trying to get folder.browser.html of the csui-style-override-kit-16.0.3/pages to work on my instance.

However, I end up with loads of console errors precisely due to the fact that all the REST API URL’s is ending up with the Network communication failed error except for the authentication part.

The same also happens with the app.html. However, I seem to be just getting the header to load in this case.

Attached are the screen caps of the same error from the console of IE for reference."

OverrideStyleKit_Error.png

Find more posts tagged with

Comments

Ferdinand Prantl

I see "Edge" in the top right corner of your screenshot. Am I right, that you use Edge, and not IE11?

Could you have a look, why the network calls went wrong? Either in Network Panel of the Developer Tools, or in Fiddler. Do the responses contain an error messages? Are they valid JSON?

There is a warning, that session storage was not available. I am not aware of any setting, which would disable it. I remember, that I faced similar problem, that some JavaScript features were disabled, if pages were opened from the local file system (file:///...) and not open from a web server (http://...) How did you open the page? Could you try to open it from a local web server too? If you don't have any Apache or Tomcat running, you can go to the csui-style-override-kit directory and start a simple web server using you local development environment:

1. Using Python

  python -m SimpleHTTPServer 7777

2. Using Node.js

  npm install -g http-server  http-server -p 7777

And then just open http://localhost:7777/pages/folder.browser.html.

The JavaScript error at the end probably comes from FolderBrowserWidget, which was not ready, that so much goes wrong ;-) We shoudl fix it to make it more robust. But at first, we should concentrate on the errors above.

Pramod Mohandas

Thank you for your inputs.

I’m running the scripts on IE11, not on Edge.

I did try to run the html files the conventional way i.e. by running the npm start in the root page (without the local server configuration). However it had failed due to obvious reasons that it couldn’t find the necessary files to compile and run them. Hence, I assumed that this does not need the help of npm per se to begin with and so the pages were tried to render directly from the local FS. There wasn’t any special mention about that anywhere that I seem to remember.

Now everything works perfectly !

Ferdinand Prantl

Thanks for letting us know!

We didn't include package.json with "npm start" as we did in the SDK. Some people felt, that it would be too much, because web designers probably have some local server anyway.

We'll emphasize it in the documentation and consuder some easy way like "npm start" again. Currently we suggest a local web server in the ReadMe, but do not say, that otherwise it will not work:

You should open the HTML pages using a local web server, where you would create a virtual directory pointing to the root directory of this kit. You can open "pages/app.html", for example, to see the landing page of the authenticated user.

Pramod Mohandas

Absolutely. A footnote of this sort would definitely help anyone looking to use the CSUI style override kit for customization. J