nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WAB - Attribute Table error in Chrome/Firefox

GarrettMcBride

I was hoping someone could help me with a problem in Web Appbuilder. We are using the latest version of WAB (downloaded yesterday). We have forced SSL and everything seems to be working properly (attached). We also have a proxy that we have been using for the past 7 years and everything works great. When loading a web map on IE everything works great, loads fast, attribute table works. When loading the same page on Chrome or Firefox it hangs for about a minute and a half before removing the attribute widget. Once it removes the attribute table it loads immediately in both browsers. I deployed a test page without the attribute table and as expected the page loads securely and super fast. I am trying to figure out what is causing the attribute widget to give Chrome and firefox an SSL Protocol error. Any help would be greatly appreciated!

chrome.png

ssl.png

Trouver plus de publications taguées avec

Accepted answers

All comments

GarrettMcBride

Robert,

So we made a little headway. Once I removed the identify widget (2.1), then everything begins to work. Strange, because something in the identify widget is causing the attribute table to fail in Chrome/Firefox. That's unfortunate because we really like the identify functionality. I verified all excluded services are mapped correctly via https. Any ideas?

Thanks,

Kade (Garrett)

RobertScheitlin__GISP

Garrett,

That is worth a shot (trying the older version). If you look up the ssl error that you get some of the google'd possible issues are that the firewall is blocking this file (something to possibly look into). What bugs me about about that is that other widgets manifest.json files come through fine. You may want to edit the manifest.json and remove the comma featureActions portion (just for testing).

GarrettMcBride

Do you think I should try using an older version of the attribute widget? Right now i am using the latest 2.1. I'm sure that's not a best practice, but i will try anything. I even loaded WAB on my desktop to see if something was wrong with the configuration on the server. Published a new page from my desktop and had the same exact errors.

GarrettMcBride

Hi Robert,

Thank you for the quick response. Our developer and I are looking into this. Weird this is only happening in Chrome and Firefox. The manifest.json file is in the directory as it should be. I even renamed the original and copied out a fresh version of the file with the same issue. We are going to keep searching to make sure nothing is pointing to internal resources.

Thanks,

Kade McBride

RobertScheitlin__GISP

Garrett,

It is only the manifest.json that is having an issue returning. I can get the Widget.js, config.json, etc without issue. Are you sure the manifest.json file exists on the server? I may have become corrupt some how.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.