Skip to content

Commit 516afba

Browse files
committed
fix: Troubleshooting steps
1 parent 71d7714 commit 516afba

File tree

1 file changed

+15
-8
lines changed

1 file changed

+15
-8
lines changed

docs/en/getting-started/troubleshooting.md

+15-8
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
11
# Troubleshooting
22

3-
Like any software, Zettlr might cause problem from time to time. This page contains instructions on how to resolve many of these issues. We have years of experience, and as such the options listed below should work in most cases.
3+
Like any software, Zettlr might cause problems from time to time. This page contains instructions on how to resolve many of these issues, and also how to help the developers fix your issues faster, should they occur. We have years of experience, and as such the options listed below should work in most cases.
44

55
!!! note
66

7-
Please attempt the steps listed here and consult [the FAQ](../reference/faq.md) first if you encounter any problems. If these steps do not solve your issue, please [ask our community](get-involved.md/#general-resources). If our community cannot help you as well, please open an issue on GitHub.
7+
Please attempt the steps listed here and consult [the FAQ](../reference/faq.md) first if you encounter any problems. If these steps do not solve your issue, please [ask our community](get-involved.md/#general-resources). If our community cannot help you as well, please open an issue on GitHub. Read the instructions below to find out how to provide all information we need.
88

99
## 1. Try Turning it Off and On Again
1010

1111
Many problems can be solved by simply quitting Zettlr and restarting it. Sometimes, a restart of your computer might help, too.
1212

1313
!!! note
1414

15-
If you can reliably reproduce the problem, that is: the problem _always_ appears after you perform a specific action, this indicates that you've found a replicable bug. In that case, please provide us with a these steps when you open an issue.
15+
If you can reliably reproduce the problem, that is: the problem _always_ appears after you perform a specific action, this indicates that you've found a replicable bug. In that case, please provide us with these steps when you open an issue.
1616

1717
## 2. Install the Most Recent Version
1818

19-
Many issues are fixed in newer versions. If you encounter an issue, make sure you have the most recent version installed.
19+
Many issues are fixed in newer versions. If you encounter an issue, make sure you have the most recent version installed. To do so, go to "Help" → "Check for updates" and see if the app detects a new update. If you used a package manager to install Zettlr, use that one to update the app. You can always find the [most recent release on GitHub](https://github.com/Zettlr/Zettlr/releases).
2020

2121
## 3. Try Clearing the Cache
2222

@@ -57,19 +57,26 @@ If you want to completely reset your local Zettlr installation, follow these ste
5757

5858
## 5. Ask the Community for Help
5959

60-
If none of the above steps seem to help, you can ask the community. Sometimes, someone else has encountered a similar problem and might be able to help you. The community is active both on [Discord](https://discord.gg/PcfS3DM9Xj) and on the [Zettlr subreddit](https://www.reddit.com/r/Zettlr).
60+
If none of the above steps seem to help, you can ask the community. Sometimes, someone else has encountered a similar problem and might be able to help you. The community is active both on [Discord](https://go.zettlr.com/discord) and on the [Zettlr subreddit](https://www.reddit.com/r/Zettlr).
6161

6262
## 6. Open a GitHub Issue
6363

64-
If the community couldn't help you, or if it seems to be an actual bug, please open an issue on GitHub. Make sure to include as much information as possible so that we can quickly address the issue.
64+
If the community couldn't help you, or if it seems to be an actual bug, please open an issue on GitHub. Make sure to include as much information as possible so that we can quickly address the issue. [Click here to open the form](https://github.com/Zettlr/Zettlr/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml) (GitHub account required). The form will ask the most important questions up front.
65+
66+
Make sure to include:
67+
68+
* A concise description of what happens, and what you expect to happen
69+
* How can you trigger this issue? Be precise here so that we can reproduce the issue on our side
70+
* Include screenshots or entire screencasts to demonstrate the issue. Very often, images "say more than a thousand words."
71+
* Also provide log entries. You can find the logs by enabling the debug mode, then selecting "Develop" → "Open logs"
6572

6673
!!! note
6774

68-
If you open an issue on GitHub, make sure you receive notifications. We have follow-up questions almost always regarding your issue. The faster you respond, the faster we can fix your issue. If no one responds to your issue, this might indicate that we are not sure how to help you. In this case, it might help to rephrase the issue or add additional information.
75+
If you open an issue on GitHub, make sure you receive notifications. We usually have follow-up questions regarding your issue. The faster you respond, the faster we can fix your issue. If no one responds to your issue, this might indicate that we are not sure how to help you. In this case, it might help to rephrase the issue or add additional information.
6976

7077
## 7. Revert to a previous version
7178

72-
Sometimes, an issue can hinder your productivity. Some users decide to revert to a previous version until we are able to fix the issue. We do not recommend this, as it can cause a host of other problems, so apply your judgment.
79+
Sometimes, an issue can hinder your productivity. Some users decide to revert to a previous version until we are able to fix the issue. We do not recommend this, as it can cause a host of other problems, so do this at your own risk.
7380

7481
!!! warning
7582

0 commit comments

Comments
 (0)