From Documentation

(Difference between revisions)
Jump to: navigation, search
(Get JavaScript Error)
(Provide ZK AU Request/Response Details)
Line 52: Line 52:
=== Provide ZK AU Request/Response Details ===
=== Provide ZK AU Request/Response Details ===
-
 
+
# open developer tool before start to reproduce your issue
-
:Snapshot the ''error'', ''request'' and ''response'' with Browser. Remember to''' turn on''' js debug in your zk.xml
+
# do the steps to reproduce your bug
-
<source type="xml">
+
# [https://developers.google.com/web/tools/chrome-devtools/network/reference#save-as-har Save all network requests to a HAR file in Chrome]
-
<client-config>
+
#: Save request details as HAR in Firefox
-
<debug-js>true</debug-js>
+
[[File:save-har-firefox.png]]
-
</client-config>
+
-
</source>
+
-
<!--
+
-
Open the developer tool (pressing F12) of your browser and snapshot the following images, then send to us.
+
-
 
+
-
{| border="1px" | width="100%" | cellspacing="0"
+
-
|-
+
-
!style="width:100px"|
+
-
!|
+
-
|-
+
-
| Server side error
+
-
|
+
-
'''1. Request'''
+
-
 
+
-
[[File:ZK_MeetRpoblem_FF01.png]]
+
-
----
+
-
 
+
-
'''2. Response'''
+
-
 
+
-
[[File:ZK_MeetRpoblem_FF02.png]]
+
-
|-
+
-
|Client side error
+
-
|
+
-
[[File:ZK_MeetRpoblem_FF03.png]]
+
-
----
+
-
 
+
-
*Click the link (the blue text) then go to the line of error.
+
-
[[File:ZK_MeetRpoblem_FF04.png]]
+
-
|}
+
-
 
+
-
== If you cannot reproduce it with Firefox ==
+
-
 
+
-
-->
+
-
 
+
-
Please follow the instructions below and provide the support team with corresponding debug information.
+
-
==== Chrome ====
+
-
*Enable "Developer tools" by F12
+
-
{| border="1px" | width="100%" | cellspacing="0"
+
-
|-
+
-
!style="width:100px"|
+
-
!|
+
-
|-
+
-
| Server side error
+
-
|
+
-
'''1. Request'''
+
-
 
+
-
[[File:ZK_MeetRpoblem_Chrome01.png]]
+
-
----
+
-
 
+
-
'''2. Response'''
+
-
 
+
-
[[File:ZK_MeetRpoblem_Chrome02.png]]
+
-
|-
+
-
|Client side error
+
-
|
+
-
 
+
-
*Click the error icon in the lower right corner.
+
-
*Click the link (test.zul:22) then go to the line where the error occurred.
+
-
[[File:ZK_MeetRpoblem_Chrome03.png]]
+
-
 
+
-
|}
+
-
 
+
-
==== IE ====
+
-
*With IE8 or later, enable "Developer tools" by F12
+
-
{| border="1px" | width="100%" | cellspacing="0"
+
-
|-
+
-
!style="width:100px"|
+
-
!|
+
-
|-
+
-
| Client side error
+
-
|
+
-
[[File:ZK_MeetRpoblem_IE01.png]]
+
-
|}
+
*Change '''Document mode''' to emulate IE6,7 if the issue happens only in these versions
*Change '''Document mode''' to emulate IE6,7 if the issue happens only in these versions

Revision as of 02:36, 21 May 2020






Contents

Getting prompt and efficient support from ZK

When you run into an issue in ZK, following this document can help you to provide the support team with sufficient data, thus speeding up the investigation and get prompt and efficient feedback. Here is a sample screenshot of an error. However, with only a screenshot, it is difficult for us to find enough clues and provide timely support. Instead of providing a screenshot, please follow the tips and instructions below when submitting your issue.

ZK MeetRpoblem01.png

Provide Sufficient information

Providing sufficient information helps us support you more efficiently.

The Sufficient Information Includes:

  1. the complete server-side error or the client-side error if any (read #Get JavaScript Error)
  2. complete exception stack trace (if any)
  3. A reproducible sample (please read #Tips for creating a reproducible sample
  4. Precise and clear steps to reproduce the issue
  5. ZK version and edition
    e.g. ZK 9.0.1 PE
  6. Browser and its version
    e.g. Firefox 60
  7. If it is hard to create a sample, you can provide an URL so that the support team can access it. When providing this URL, remember to turn on the js debug in your zk.xml.
  8. Application servers (e.g. JBoss 6, if it's necessary).
  9. If your case happens only in your specific environment, it is recommended to request an online meeting or provide a virtual machine as a copy of your actual environment,

Tips for creating a reproducible sample

You can:

  1. Use zkfiddle
  2. Zip your maven project with pom.xml and include necessary source code
  3. Provide zul and its related Java source
  4. Provide a public URL that we can visit


  • Clone the original zul with the issue, remove irrelevant components
  • You could move your Java codes (mostly event listeners) into <zscript>
  • Replace your database data with static sample data in order to run without a database.

Get JavaScript Error

You can check if there is any JavaScript error by opening the developer tool. For example, the chrome developer tool/ Console tab

Chrome-js-error.png

You can extract the error message by:

  • select and copy the whole text or
  • right-click, select "Save as..."

If you cannot provide a reproducible sample

Then you can choose the following alternatives:

Provide a Public URL of Your Web Application

Provide an URL so that the support team can access it. When providing this URL, remember to turn on the js debug in your zk.xml.

Provide ZK AU Request/Response Details

  1. open developer tool before start to reproduce your issue
  2. do the steps to reproduce your bug
  3. Save all network requests to a HAR file in Chrome
    Save request details as HAR in Firefox

Save-har-firefox.png

  • Change Document mode to emulate IE6,7 if the issue happens only in these versions

ZK MeetRpoblem IE02.png

Quirks Mode: IE6
Internet Explorer 7 Standards: IE7

How to Run a Sample Maven Project

In order to narrow down the problem and eliminate differences caused by different environments, we often send you a sample maven project that tries to simulate and reproduce your issue. To run the project, you need to download maven and setup first.

  1. Run your command line interface
  2. switch to the sample project's root folder that has a pom.xml
  3. Start jetty server with the command below
    mvn jetty:run
  4. Visit the project's pages with your browser

If you don't know the zul's path or if the path is incorrect, just visit http://localhost:8080. A browser will show a link with the correct context path:

JettyRoot.png

Click the link and it will list folders then you can navigate to find the zul.

ListFolder.png

How to get Browser Performance Profile

If you are running into a performance issue, you can first check out Step by Step Trouble Shooting and do a first step analysis using browser's developer tools.

By Chrome developer tool

By Firefox developer tool

By Edge developer tool



Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.