WAB-DE Application Missing Buttons when Published

[Anonymous User]

I have a Web AppBuilder Dev Edition 2.13 Foldable Template app that includes Select and Layer List tools. The widgets work fine in the WAB-DE GUI and local host, but when I publish to to the webshare then the check boxes in the select tool dissapear, as do the Search Button and layer description icons (three little dots to the right) in the Layer List. The elevation Profile tool is also missing the 'download' button. This is a button config issue I am not sure how to resolve it.

Is this a proxy issue? I have replicated the issue in v2.14 with same result in a new template based app with only those two tools. What could be causing this?

Thanks!

A

[RobertScheitlin__GISP]

You should check your browsers web console and you will likely see that you have some woff and woff2 mime type error. This is because your web server has not been setup for those mime type and you just need to fix that. I have addressed this issue in several previous threads and you can find the link to directions to setup those or you can do a quick Google search too.

[Anonymous User]

Thank you Robert. I don't have any errors in the console but I will look for your previous threads per your recommendation for addressing the MIME error and post an update here. This does appear to be a CSS lost in translation issue... thank you for the guidance.

[RobertScheitlin__GISP]

Sorry I meant to say your browsers network tab, not web console. You will likely find some 40x errors there dealing with woff and woff2 files

[Anonymous User]

I checked and there are no errors on the network tab either... I did discover that the app is loading correctly in Firefox; yet in Chrome and Edge it is working only in the development server, but it is not loading the widget's css correctly (no buttons) in the publication server (apache). Can I override the application mime type registration in the index.html somehow?

(I wasn't able to find references to your previous threads on the issue... nor do i have access to the server config files.)

Thank you for your time!

[RobertScheitlin__GISP]

Andra,

   Strange. Is this app where I can get access to test it?

[Anonymous User]

Kind of you to offer Robert! No, it is not accessible externally. The app is on the intranet, which may be part of the problem... I think I might set up a proxy to see if that helps.

A

[RobertScheitlin__GISP]

That would not make sense that it works in Firefox if it is a proxy issue though. So you are sure in Chrome when you open the network tab and scroll through the network requests there are no red line with with 403 or 404 errors?

[KenBuja]

There might be some security issues, since Chrome does enforce rules differently than Firefox.

[Anonymous User]

Its all OK with 200's except for a couple of 304 and 307 for text/plain types and the css font family Ubuntu... I sorted by status to verify and there are no 403 or 404 errors. 

I would rather not use a proxy if it is unnecessary. It works like a charm in firefox. I also tested the web server config that removed and replaced the fonts MIME/type registrations, but had no change on the publication server. I am stumped? 

I could host it externally for testing or send you the app in a ZIP for testing if you thinks it a worthwhile investigation and you are up for it!