discord-tickets/portal

The web application for Discord Tickets settings, archives, feedback, and more.

portal's Issues

[BUG] Roles are in ID (creation) order, not cusotm hierachy

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

No response

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS:
- Node:
- NPM:
- Bot: 4.0.3

Anything else?

Not really a bug but it would make more sense if they were in the order the user is accustomed to.

[BUG] Category `customTopic` resets

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The field can become blank, causing an unexpected value in the database. When a user tries to create a ticket after this has happened, there is a fatal error that isn't logged but causes a memory leak. The bot becomes completely unresponsive until it runs out of memory and crashes.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS:
- Node:
- NPM:
- Bot: 4.0.3

Anything else?

No response

[BUG] Blocklist roles in general settings are not coloured like for categories

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

No response

Expected Behavior

Colour

Steps To Reproduce

No response

Environment

- OS:
- Node:
- NPM:
- Bot: 4.0.0

Anything else?

No response

[BUG] Refreshing the New Category Page Causes a 500 Internal Server Error

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When you go to create a new category, if you refresh the category creation page, it will cause a HTTP 500 error.

Expected Behavior

The page should reload without problem and maybe save your changes

Steps To Reproduce

Open an instance of the Portal on Discord Tickets (such as the public test instance)
Navigate to a server
Go to create a new category
Refresh the page

Environment

- OS: Debian (presumably 11) (through Docker on Pterodactyl)
- Node: 18.5.0
- NPM: 18.0.0 (also presumably, Pterodactyl doesn't show the version of NodeJS 18 being used)
- Bot: 4.0.0-beta.10

Anything else?

An error gets logged in the console, a screenshot of it is below:

[BUG] Navigating directly to a category in the settings panel results in a 500 error

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Going to /settings/:guild/categories and clicking on a category is fine because all of the processing to load the new page is done client-side, but going directly to /settings/:guild/categories/:category fails with an HTTP 500 error code.

(node:14324) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
 23/03/23 21:06:06  [NOTICE] Discord Tickets v4.0.0-beta.9 on Node.js v19.0.1 (win32)
 23/03/23 21:06:06  [NOTICE] An error was not caught
 23/03/23 21:06:06  [WARN] Uncaught SyntaxError
 23/03/23 21:06:06  [ERROR] C:\Users\Isaac\Documents\Projects\DiscordTickets\bot\node_modules\.pnpm\@[email protected]\node_modules\@skyra\discord-components-core\loader\index.js:3
export * from '../dist/esm/polyfills/index.js';
^^^^^^

SyntaxError: Unexpected token 'export'
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1088:15)
    at Module._compile (node:internal/modules/cjs/loader:1123:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Module._load (node:internal/modules/cjs/loader:878:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS: Windows 11
- Node: 
- NPM:
- Bot:

Anything else?

No response

[BUG] Question value smaller than minium length freeze bot / website (panel)

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

If question value is smaller than minimum length and you create ticket on that category bot freeze

Expected Behavior

Steps To Reproduce

Create new question
Fill required information.
Set minium length to 20
Set value to 123
Submit
Create ticket on that category and bot / panel freeze

Environment

- OS: ubuntu
- Node: 18+
- NPM: - (filling later)
- Bot: latest dev

Anything else?

User should fill form to required length

Guild `autoClose` input is required but shouldn't be

portal/src/routes/settings/[guild]/general/+page.svelte

Line 119 in ce9e091

<input type="text" class="form-input input" bind:value={settings.autoClose} required />