|
3 | 3 | > _**This document contains common problems and their solutions.**_<br> |
4 | 4 | > Please ensure your issue isn't listed here, before opening a new ticket. |
5 | 5 | > |
6 | | -> _If you come across an issue not listed below, consider adding it, to help other users._ |
| 6 | +> _Found something not listed here? Consider adding it, to help other users._ |
7 | 7 |
|
8 | 8 | ### Contents |
9 | 9 | - [Refused to Connect in Web Content View](#refused-to-connect-in-modal-or-workspace-view) |
|
30 | 30 | - [Status Checks Failing](#status-checks-failing) |
31 | 31 | - [Diagnosing Widget Errors](#widget-errors) |
32 | 32 | - [Fixing Widget CORS Errors](#widget-cors-errors) |
| 33 | +- [Widget Shows Error Incorrectly](#widget-shows-error-incorrectly) |
33 | 34 | - [Weather Forecast Widget 401](#weather-forecast-widget-401) |
34 | 35 | - [Font Awesome Icons not Displaying](#font-awesome-icons-not-displaying) |
35 | 36 | - [Copy to Clipboard not Working](#copy-to-clipboard-not-working) |
36 | 37 | - [How to Reset Local Settings](#how-to-reset-local-settings) |
| 38 | +- [How to make a bug report](#how-to-make-a-bug-report) |
37 | 39 | - [How-To Open Browser Console](#how-to-open-browser-console) |
38 | 40 | - [Git Contributions not Displaying](#git-contributions-not-displaying) |
39 | 41 |
|
@@ -421,6 +423,15 @@ For testing purposes, you can use an addon, which will disable the CORS checks. |
421 | 423 |
|
422 | 424 | --- |
423 | 425 |
|
| 426 | +## Widget Shows Error Incorrectly |
| 427 | +
|
| 428 | +When there's an error fetching or displaying a widgets data, then it will be highlighted in yellow, and a message displayed on the UI. |
| 429 | +
|
| 430 | +In some instances, this is a false positive, and the widget is actually functioning correctly. |
| 431 | +If this is the case, you can disable the UI error message of a given widget by setting: `ignoreErrors: true` |
| 432 | +
|
| 433 | +--- |
| 434 | +
|
424 | 435 | ## Weather Forecast Widget 401 |
425 | 436 |
|
426 | 437 | [Weather widget](/docs/widgets.md#weather-forecast) is working fine, but you are getting a `401` for the [Weather Forecast widget](/docs/widgets.md#weather-forecast), then this is most likely an OWM API key issue. |
@@ -473,6 +484,47 @@ For a full list of all data that may be cached, see the [Privacy Docs](/docs/pri |
473 | 484 |
|
474 | 485 | --- |
475 | 486 |
|
| 487 | +## How to make a bug report |
| 488 | +
|
| 489 | +#### Step 1 - Where to open issues |
| 490 | +
|
| 491 | +You will need a GitHub account in order to raise a ticket. You can then [click here](https://github.com/Lissy93/dashy/issues/new?assignees=lissy93&labels=%F0%9F%90%9B+Bug&template=bug.yml&title=%5BBUG%5D+%3Ctitle%3E) to open a new bug report. |
| 492 | +
|
| 493 | +#### Step 2 - Checking it's not already covered |
| 494 | +
|
| 495 | +Before submitting, please check that: |
| 496 | +- A similar ticket has not previously been opened |
| 497 | +- The issue is not covered in the [troubleshooting guide](https://github.com/Lissy93/dashy/blob/master/docs/troubleshooting.md) or [docs](https://github.com/Lissy93/dashy/tree/master/docs#readme) |
| 498 | +
|
| 499 | +#### Step 3 - Describe the Issue |
| 500 | +
|
| 501 | +Your ticket will likely be dealt with more effectively if you can explain the issue clearly, and provide all relevant supporting material. |
| 502 | +
|
| 503 | +Complete the fields, asking for your environment info and version of Dashy. |
| 504 | +Then describe the issue, briefly explaining the steps to reproduce, expected outcome and actual outcome. |
| 505 | +
|
| 506 | +#### Step 4 - Provide Supporting Info |
| 507 | +
|
| 508 | +Where relevant please also include: |
| 509 | +
|
| 510 | +- A screenshot of the issue |
| 511 | +- The relevant parts of your config file |
| 512 | +- Logs |
| 513 | + - If client-side issue, then include the browser logs ([see how](#how-to-open-browser-console)) |
| 514 | + - If server-side / during deployment, include the terminal output |
| 515 | +
|
| 516 | +_Take care to redact any personal info, (like IP addresses, auth hashes or API keys)_ |
| 517 | +
|
| 518 | +#### Step 5 - Fix Released |
| 519 | +
|
| 520 | +A maintainer will aim to respond within 48 hours. |
| 521 | +The timeframe for resolving your issue, will vary depending on severity of the bug and the complexity of the fix. |
| 522 | +You will be notified on your ticket, when a fix has been released. |
| 523 | +
|
| 524 | +Finally, be sure to remain respectful to other users and project maintainers, in line with the [Contributor Covenant Code of Conduct](https://github.com/Lissy93/dashy/blob/master/.github/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct). |
| 525 | +
|
| 526 | +--- |
| 527 | +
|
476 | 528 | ## How-To Open Browser Console |
477 | 529 | When raising a bug, one crucial piece of info needed is the browser's console output. This will help the developer diagnose and fix the issue. |
478 | 530 |
|
|
0 commit comments