-
Notifications
You must be signed in to change notification settings - Fork 176
Reporting issues
Miriam Zusin edited this page Apr 20, 2017
·
3 revisions
Going to create an issue ticket? Please follow the guidelines described in this document.
Please include the following information in your bug report:
- Please search to see if such bug request already exists. If a request is found, please +1 that one.
- Create reproducible test case with a live example. Make use of jsFiddle, jsBin, or Codepen to share your test cases.
- Please include steps to reproduce the bug.
- Include the following information:
- Do you use client side or server side version of jPList?
- Provide the details about server side language and database in case of server side jPList (for example, php version and php error logs).
- Browser name and version.
- Browser console errors if any.
- jPList core version.
- jPList controls/bundles versions.
- All other appropriate info.
- Please search to see if your feature request already exists. If a request is found, please +1 that one.
- Please make sure you explain the reason this enhancement or feature would benefit the majority of jPList users.
- A screenshot, mockup or wireframe is welcome.