Is there a similar way of debugging the Geocortex web viewer to the one used with the html5 viewer? i.e. use dev=true and check devtools in the browser. From what I can see, this approach does not work with the web viewer.
From what I can see, any "dev=true" or "debug=true" parameter is removed from the URL on load. The debugging in dev tools in the sandbox is better, but still not on par with the html5 viewer. Any suggestions? :)
-
Hi Brede,
Currently the only logs available for Geocortex Web are through the browser's console. We have plans in the future to add this type of functionality; I added your name to the list of interested parties.
Thanks, Stefan
0 -
Great Stefan, thanks for a quick reply! :)
0 -
@Stefan Schweigert? , please add my name to the interested party list. Thanks Richard.
0 -
Thought I'd jump in and clarify a couple of points.
- There is a debug=true URL parameter for Geocortex Web (GXW). It currently has two specific behaviors. It doesn't cache workflows at runtime (useful if you are iteratively editing a workflow and want to see it in GXW without having to reload the app). It adds additional logging information to the console log (not yet as complete as we intend it to be).
- We don't have any current plans to create a dedicated/standalone log file; rather we intend to continue to enhance the content that is provided in the console log and available using the browser's development tools.
A short note there about what you were troubleshooting, trying to determine from the console log and what was missing would help us capture additional notes for our user stories intended to enhance that content.
0 -
@Stefan Schweigert? or @Cam Barnard? ,
Do you all have an update on this?
Debug=true is good for the cacheing of the workflows, but that extra console logging information would be pretty useful.
Thanks,
Nelson
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
5 commentaires