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; } } }

Widget.js Network Calls- Now appended with ?wab_dv=..

GeoNZ

We have a custom search widget which calls additional libraries in its widget.js using jimu/loaderplugins to load jQuery and terraformer.

Looking at the network calls when the app is initiating the widgets in an older WAB dev edition app (v1.3) compared with a newer one (v2.5), the calls to Widget.js have now been appended with ?wab_dev=2.5 (i.e. the deployVersion as listed in the env.js of the application).

This is causing issues with the loading of these extra libraries (access is denied and the widget fails to startup). Commenting out the deployVersion line in env.js throws an error.

Is there a way to disable that? Or alternatively, is there a updated method for loading additional libraries (in order) from the widget?

Regards

Find more posts tagged with

Accepted answers

GeoNZ

That part worked (i.e. removed the deploy version from the outgoing calls) but didn't resolve loading of the 3rd party libraries.

I've subsequently traced the error to version 3.23 of the JS API. Reverting env.js to point to version 3.20 of the API removes all errors- We host our API locally so I'm unsure if it is a bad install of 3.23 or something in version 3.23 generally.

All comments

RobertScheitlin__GISP

NZ GeoCAD,

The deploy version is added to the url in the env.js appendDeployversion function. Just comment out 5-9.

<SPAN class="keyword token">function</SPAN> <SPAN class="token function">appendDeployVersion</SPAN><SPAN class="punctuation token">(</SPAN>url<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">if</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="regex token">/^http(s)?:\/\//</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="token function">test</SPAN><SPAN class="punctuation token">(</SPAN>url<SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">||</SPAN> <SPAN class="regex token">/^\/proxy\.js/</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="token function">test</SPAN><SPAN class="punctuation token">(</SPAN>url<SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">||</SPAN> <SPAN class="regex token">/^\/\//</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="token function">test</SPAN><SPAN class="punctuation token">(</SPAN>url<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">return</SPAN> url<SPAN class="punctuation token">;</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="punctuation token">}</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="comment token">// if(url.indexOf('?') > -1){</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="comment token">//&nbsp;&nbsp; url = url + '&wab_dv=' + deployVersion;</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="comment token">// }else{</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="comment token">//&nbsp;&nbsp; url = url + '?wab_dv=' + deployVersion;</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="comment token">// }</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">return</SPAN> url<SPAN class="punctuation token">;</SPAN>
&nbsp; <SPAN class="punctuation token">}</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

GeoNZ

Thanks Robert- That helped, but didn't solve my problem unfortunately. I think its related to how the external libraries are loaded with jimu/loaderplugins so will keep searching.

RobertScheitlin__GISP

So your saying the deploy version is still getting added to your third part libraries?

GeoNZ

That part worked (i.e. removed the deploy version from the outgoing calls) but didn't resolve loading of the 3rd party libraries.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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