You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+23-10Lines changed: 23 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,29 +10,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
10
10
- New command `note` will add a system message to your thread logs. This is useful for noting the context of a conversation.
11
11
12
12
# v2.8.1
13
+
13
14
### Fixed
14
-
- Fixed bug where thread logs were getting duplicated when using the contact command.
15
+
- Fixed bug where thread logs were getting duplicated when using the `contact` command.
16
+
- Fixed bug where the wrong key was used for logs which caused some `log` command log links to point to an HTTP 404 Not Found.
17
+
- A minor oversight from commit 1ba74d9.
15
18
16
19
# v2.8.0
20
+
17
21
### Changed
18
-
- Major improvement in thread log viewing.
19
-
- Log links are now rendered in html instead of plain text.
22
+
- Major improvement in viewing thread logs.
23
+
- Log links are now rendered in HTML instead of plain text.
20
24
21
25
# v2.7.2
22
26
23
27
### Added
24
28
-`config options` command to see a list of valid config variables that you can modify.
25
29
26
30
### Security
27
-
Thread channels will now default to being private (@everyone's read message perms set to false) if the thread creation category could not be resolved. This will save you from some trouble if for whatever reason your configuration gets messed up 🌚
31
+
Thread channels will now default to being private (`@everyone`'s read message perms set to `false`).
32
+
- If the thread creation category could not be resolved.
33
+
- This will save you from some trouble if for whatever reason your configuration gets messed up.
28
34
29
35
# v2.7.1
30
36
31
37
### Changed
32
38
33
-
- All reference to "modmail"/"Mod Mail"/"ModMail" are changed to "Modmail".
39
+
- All reference to "modmail" / "Mod Mail" / "ModMail" are changed to "Modmail".
34
40
-`log_channel_id` is now part of the config upon `setup`.
35
-
- Added the ability to set where tickets are created using the `main_category_id` configuration option.
41
+
- Added the ability to set where threads are created using the `main_category_id` configuration option.
42
+
43
+
### Important Note
44
+
45
+
- If your Modmail bot was set up a long time ago, you may experience an issue where messages were sent outside of the category.
46
+
- To fix this, set `main_category_id` to the ID of the Modmail category.
47
+
36
48
# v2.7.0
37
49
38
50
### Changed
@@ -52,19 +64,19 @@ Fixed log URLs for self-hosting users.
52
64
# v2.6.1
53
65
54
66
### Fixed
55
-
-API BASE URL
67
+
-Replaced the testing `API_BASE_URL` with the actual URL.
56
68
57
69
# v2.6.0
58
70
59
71
Mostly internal changes. Some are slightly breaking. Keep a lookout for broken features and report them on our server.
60
72
61
73
### Added
62
-
-`threads` is now a default alias to `logs`
74
+
-`threads` is now a default alias to `logs`.
63
75
64
76
### Changed
65
77
- Log URLs are moved to their own collection.
66
78
- Log URLs are now `https://logs.modmail.tk/LOGKEY`, no more numbers before the log key.
67
-
- We still support the numbers so as to not break everyone's URLs so quickly but both work atm :p
79
+
- We still support the numbers so as to not break everyone's URLs so quickly but both work at the moment.
68
80
- This is a huge change to the backend logging and there might be migration errors. If so, please contact us at our [discord server](https://discord.gg/2fMbf2N)
69
81
70
82
# v2.5.2
@@ -79,7 +91,8 @@ Non breaking internal changes.
79
91
80
92
### Background
81
93
Bots hosted by Heroku restart at least once every 27 hours.
82
-
During this period, local caches are deleted, which results in the inability to set the scheduled close time to longer than 24 hours. This update resolves this issue. [PR #135](https://github.com/kyb3r/modmail/pull/135)
94
+
During this period, local caches are deleted, which results in the inability to set the scheduled close time to longer than 24 hours. This update resolves this issue.
0 commit comments