Select to view content in your preferred language

Issues upgrading Flexviewer 3.1 (uncompiled)

8430
48
Jump to solution
12-18-2012 10:05 AM
by Anonymous User
Not applicable
Original User: btelliot

Hi All,

I've been upgrading our in-house web mapping application from flexviewer 3.0 to 3.1, and I've encountered a small problem.

The first time I load the Flexviewer application in the web browser, the User Interface doesn't load properly.  If I refresh using the F5 button, it loads properly.

Here is a screenshot of the issue:
First load:
[ATTACH=CONFIG]20039[/ATTACH]

After refresh (F5)
[ATTACH=CONFIG]20040[/ATTACH]

Any help on the matter would be appreciated.

Cheers,

Brett
0 Kudos
48 Replies
by Anonymous User
Not applicable
Original User: ecrsteve

I have been having the same problem in 3.1 (same list of toc object runtime errors) but not because of pop-ups.  I have a geoprocessing widget that automatically adds a dynamic map service layer into the viewer, and the MapSwitcher and LayerList widgets worked normally in Viewer 3.0.  But in Viewer 3.1 the added map service wouldn't fully appear in either MapSwitcher or LayerList.  The map service has about 50 sublayers.  I used Robert's solution and it worked for me.  Thanks to everyone who tracked this problem down.  It had been a real pain for me.
0 Kudos
by Anonymous User
Not applicable
Original User: btelliot

Hi Everyone,

Thank you so much for recognizing and troubleshooting this issue.  I've been working with ESRI Canada's Tech Support for the past 2 months which has been a nightmare to get them to even recognize that there is an issue.

I heard back from them today, saying this bug has now officially been logged by ESRI. 


The issue is logged as:
NIM088904: The header controller widget does not load properly when using tag popups in the main config.xml file.

Here is the link to the bug description:
http://support.esri.com/en/bugs/nimbus/TklNMDg4OTA0

According to the bug description, this issue is fixed in the next release of the Flex Viewer.  I will try to find out the release date for version 3.2.  You will notice in the description that it references the workaround suggested by Robert Scheitlin from the forum you provided.  It also references the bug Mattias Ekstrom posted on github (https://github.com/Esri/arcgis-viewer-flex/issues/28).


Thank you Robert, Mattias, and everyone else that helped out.

Cheers,

Brett
0 Kudos
BjornSvensson
Esri Regular Contributor
Just wanted to follow up and let you know that this has been fixed and will be part of the 3.2 release (see GitHub Issue #28 - popups in 3.1 causes problem on application startup).

FYI: if you want to see what other viewer code changes made it into 3.2, look at the closed and verified issues for 3.2:
https://github.com/Esri/arcgis-viewer-flex/issues?labels=verified&milestone=1&state=closed
0 Kudos
by Anonymous User
Not applicable
Original User: klarson27

Looking forward to a fix.


Have you yet implemented the fix? Please avise.
0 Kudos
MichaelVolz
Esteemed Contributor
I was hoping the forum old timer archie p would have an answer to this question.
0 Kudos
by Anonymous User
Not applicable
Original User: gonzalc5

Is anyone else having the same issue even after upgrading to 3.2? It appeared to be working at first, but now my sublayer popups are causing it to not load my widgets all over again.

Thanks
Christina
0 Kudos
AndyCowx1
Emerging Contributor
I have the issue using the compiled version 3.1

Is there anything I can do other than comment out the popups ? (I can't implement Roberts changes given that I'm not working with source, right ?)

Can anyone verify if 3.2 fixes it ?
0 Kudos
by Anonymous User
Not applicable
Original User: btelliot

I have the issue using the compiled version 3.1

Is there anything I can do other than comment out the popups ? (I can't implement Roberts changes given that I'm not working with source, right ?)

Can anyone verify if 3.2 fixes it ?


Yes,  3.2 fixes the issue.
0 Kudos
AndyCowx1
Emerging Contributor
I have the issue using the compiled version 3.1

Is there anything I can do other than comment out the popups ? (I can't implement Roberts changes given that I'm not working with source, right ?)

Can anyone verify if 3.2 fixes it ?


Not sure if anyone has tried changing the layer type to "feature" ? Seems to fix the issue for me (at least on initial testing)
0 Kudos