admin-fe issueshttps://git.pleroma.social/pleroma/admin-fe/-/issues2024-03-01T16:15:48Zhttps://git.pleroma.social/pleroma/admin-fe/-/issues/230Bug: MRF keyword wrong placeholder text2024-03-01T16:15:48ZNicholas ConradBug: MRF keyword wrong placeholder textThe placeholder text says "instance: reason" when it should say "pattern: replacement"![Screenshot_20240301_071459_Brave](/uploads/634ce9e8262322554ff524a6883b87a5/Screenshot_20240301_071459_Brave.jpg)The placeholder text says "instance: reason" when it should say "pattern: replacement"![Screenshot_20240301_071459_Brave](/uploads/634ce9e8262322554ff524a6883b87a5/Screenshot_20240301_071459_Brave.jpg)https://git.pleroma.social/pleroma/admin-fe/-/issues/227Ability to point to custom repository URL (AGPLv3 compliance)2023-11-09T13:23:23ZHaelwennAbility to point to custom repository URL (AGPLv3 compliance)https://git.pleroma.social/pleroma/admin-fe/-/issues/226Improve Frontend Management2023-11-09T02:13:20ZHaelwennImprove Frontend ManagementSee <https://git.pleroma.social/pleroma/pleroma.social/-/merge_requests/95>, notably AdminFE should be able to select at least different branches if not develop + releases.See <https://git.pleroma.social/pleroma/pleroma.social/-/merge_requests/95>, notably AdminFE should be able to select at least different branches if not develop + releases.https://git.pleroma.social/pleroma/admin-fe/-/issues/225Moderator only has 'deactivate account' option while deal with pending regist...2023-01-03T22:06:55ZYating ZhanModerator only has 'deactivate account' option while deal with pending registerationPlease see the picture.
The moderator can do nothing other than refuse the registration.
![image](/uploads/718d0bc6a504879420104f1e9192af85/image.png)Please see the picture.
The moderator can do nothing other than refuse the registration.
![image](/uploads/718d0bc6a504879420104f1e9192af85/image.png)https://git.pleroma.social/pleroma/admin-fe/-/issues/223Stable release links to developer documentation2022-12-07T00:06:05ZJames CridlandStable release links to developer documentationThe stable release is linking to the developer branch documentation.
This means [incorrect documentation is visible](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3361#note_96475) for features that don't exist in the stabl...The stable release is linking to the developer branch documentation.
This means [incorrect documentation is visible](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3361#note_96475) for features that don't exist in the stable release. Admins are then confused as to why the features don't exist, and spend more than three hours trying to research the issue. Ask me how I know.
[Here are the two links to the wrong documentation](https://git.pleroma.social/search?search=docs-develop.pleroma.social&nav_source=navbar&project_id=422&group_id=3&search_code=true&repository_ref=stable)
To replicate:
* Visit `(tld)/pleroma/admin/#/settings/instance`
* "see documentation", the link in the top right corner, goes to https://docs-develop.pleroma.social/backend/administration/CLI_tasks/config/https://git.pleroma.social/pleroma/admin-fe/-/issues/222'Request failed with status code 500 - [object Object]' toast message on ever...2023-08-22T15:35:39ZMorris Silvya'Request failed with status code 500 - [object Object]' toast message on every page in Pleroma/AdminI'm not sure what setting I clicked but navigating to any page on the Admin page is showing the 'Request failed with status code 500 - [object Object]' toast message.
I followed the steps outlined here: https://soapbox.pub/install/ and...I'm not sure what setting I clicked but navigating to any page on the Admin page is showing the 'Request failed with status code 500 - [object Object]' toast message.
I followed the steps outlined here: https://soapbox.pub/install/ and it's installed on Ubuntu.
Attaching the video, which better describes the issue. I am logged in as Admin.
Apologies for posting it on the pleroma-support page. Wasn't aware that there was this separate one for admin-fe.
![Request_failed_with_status_code_500_-__object_Object_](/uploads/220c43aacf34d26da65a54a7b5a4f01e/Request_failed_with_status_code_500_-__object_Object_.mp4)https://git.pleroma.social/pleroma/admin-fe/-/issues/221Identify missing copyright notices / licences for REUSE compliance2022-11-27T02:52:15ZHaelwennIdentify missing copyright notices / licences for REUSE complianceSee: https://git.pleroma.social/pleroma/admin-fe/-/merge_requests/291See: https://git.pleroma.social/pleroma/admin-fe/-/merge_requests/291https://git.pleroma.social/pleroma/admin-fe/-/issues/220Be able to unset admin_token2022-11-16T18:45:20ZDave TapleyBe able to unset admin_tokenOnce you set an admin token here, there is no way to unset it (except by manually removing from `config` table in DB):
![Screen_Shot_2022-11-16_at_11.44.48_AM](/uploads/e33455c3f07e5d60d3b179c75b1056e2/Screen_Shot_2022-11-16_at_11.44.48...Once you set an admin token here, there is no way to unset it (except by manually removing from `config` table in DB):
![Screen_Shot_2022-11-16_at_11.44.48_AM](/uploads/e33455c3f07e5d60d3b179c75b1056e2/Screen_Shot_2022-11-16_at_11.44.48_AM.png)https://git.pleroma.social/pleroma/admin-fe/-/issues/216Allow to set status as sensitive or change visibility without a prior report2022-10-14T16:44:57ZHaelwennAllow to set status as sensitive or change visibility without a prior reportShould also make sure there is a moderation log entry for it.Should also make sure there is a moderation log entry for it.https://git.pleroma.social/pleroma/admin-fe/-/issues/215Fix performance on status loading2022-10-14T16:43:49ZHaelwennFix performance on status loadingLoading the statuses is horribly slow and seems to use a *lot* of memory.Loading the statuses is horribly slow and seems to use a *lot* of memory.https://git.pleroma.social/pleroma/admin-fe/-/issues/213Refactor: Maybe remove function `hasPermission`2022-12-18T09:40:22ZIljaRefactor: Maybe remove function `hasPermission``src/permission.js` has a function
```javascript
function hasPermission(roles, permissionRoles) {
if (roles.indexOf('admin') >= 0) return true // admin permission passed directly
if (!permissionRoles) return true
return roles.some...`src/permission.js` has a function
```javascript
function hasPermission(roles, permissionRoles) {
if (roles.indexOf('admin') >= 0) return true // admin permission passed directly
if (!permissionRoles) return true
return roles.some(role => permissionRoles.indexOf(role) >= 0)
}
```
In practice this seems to always return true because the only place I see the function being called has `to.meta.roles` for `permissionRoles`. And none of the routes have `meta.roles`.
AFAICT this is used to return 401 for calls to the BE that a user shouldn't be able to do. But imo it should be up to the BE to determine what is allowed or not, not the FE.
So basically, I believe this function and everything that uses it and the 401 routes can/should all be removed.https://git.pleroma.social/pleroma/admin-fe/-/issues/208Dependency Dashboard2024-03-29T09:10:40Zrenovate-botDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Rate-Limited
These updates are currently rate-limited. Click on a...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Rate-Limited
These updates are currently rate-limited. Click on a checkbox below to force their creation now.
- [ ] <!-- unlimit-branch=renovate/autoprefixer-10.x -->Update dependency autoprefixer to v10.4.19
- [ ] <!-- unlimit-branch=renovate/element-ui-2.x -->Update dependency element-ui to v2.15.14
- [ ] <!-- unlimit-branch=renovate/postcss-8.x -->Update dependency postcss to v8.4.38
- [ ] <!-- unlimit-branch=renovate/semver-5.x -->Update dependency semver to v5.7.2
- [ ] <!-- unlimit-branch=renovate/axios-0.x -->Update dependency axios to v0.28.1
- [ ] <!-- unlimit-branch=renovate/luxon-3.x -->Update dependency luxon to v3.4.4
- [ ] <!-- unlimit-branch=renovate/prosemirror-model-1.x -->Update dependency prosemirror-model to v1.19.4
- [ ] <!-- unlimit-branch=renovate/vue-loader-15.x -->Update dependency vue-loader to v15.11.1
- [ ] <!-- unlimit-branch=renovate/webpack-4.x -->Update dependency webpack to v4.47.0
- [ ] <!-- unlimit-branch=renovate/node-20.x -->Update Node.js to v20
- [ ] <!-- unlimit-branch=renovate/axios-1.x -->Update dependency axios to v1
- [ ] <!-- unlimit-branch=renovate/babel-eslint-10.x -->Update dependency babel-eslint to v10
- [ ] <!-- unlimit-branch=renovate/babel-loader-9.x -->Update dependency babel-loader to v9
- [ ] <!-- unlimit-branch=renovate/compression-webpack-plugin-11.x -->Update dependency compression-webpack-plugin to v11
- [ ] <!-- unlimit-branch=renovate/eslint-loader-4.x -->Update dependency eslint-loader to v4
- [ ] <!-- unlimit-branch=renovate/eslint-plugin-vue-9.x -->Update dependency eslint-plugin-vue to v9
- [ ] <!-- unlimit-branch=renovate/file-loader-6.x -->Update dependency file-loader to v6
- [ ] <!-- unlimit-branch=renovate/hash-sum-2.x -->Update dependency hash-sum to v2
- [ ] <!-- unlimit-branch=renovate/html-webpack-plugin-5.x -->Update dependency html-webpack-plugin to v5
- [ ] <!-- unlimit-branch=renovate/js-cookie-3.x -->Update dependency js-cookie to v3
- [ ] <!-- unlimit-branch=renovate/marked-12.x -->Update dependency marked to v12
- [ ] <!-- unlimit-branch=renovate/mini-css-extract-plugin-2.x -->Update dependency mini-css-extract-plugin to v2
- [ ] <!-- unlimit-branch=renovate/normalize.css-8.x -->Update dependency normalize.css to v8
- [ ] <!-- unlimit-branch=renovate/optimize-css-assets-webpack-plugin-6.x -->Update dependency optimize-css-assets-webpack-plugin to v6
- [ ] <!-- unlimit-branch=renovate/ora-8.x -->Update dependency ora to v8
- [ ] <!-- unlimit-branch=renovate/path-to-regexp-6.x -->Update dependency path-to-regexp to v6
- [ ] <!-- unlimit-branch=renovate/postcss-loader-8.x -->Update dependency postcss-loader to v8
- [ ] <!-- unlimit-branch=renovate/rimraf-5.x -->Update dependency rimraf to v5
- [ ] <!-- unlimit-branch=renovate/sass-loader-14.x -->Update dependency sass-loader to v14
- [ ] <!-- unlimit-branch=renovate/semver-7.x -->Update dependency semver to v7
- [ ] <!-- unlimit-branch=renovate/svg-sprite-loader-6.x -->Update dependency svg-sprite-loader to v6
- [ ] <!-- unlimit-branch=renovate/svgo-3.x -->Update dependency svgo to v3
- [ ] <!-- unlimit-branch=renovate/uglifyjs-webpack-plugin-2.x -->Update dependency uglifyjs-webpack-plugin to v2
- [ ] <!-- unlimit-branch=renovate/major-vue-monorepo -->Update dependency vue to v3
- [ ] <!-- unlimit-branch=renovate/vue-i18n-9.x -->Update dependency vue-i18n to v9
- [ ] <!-- unlimit-branch=renovate/vue-loader-17.x -->Update dependency vue-loader to v17
- [ ] <!-- unlimit-branch=renovate/vue-router-4.x -->Update dependency vue-router to v4
- [ ] <!-- unlimit-branch=renovate/vuex-4.x -->Update dependency vuex to v4
- [ ] <!-- unlimit-branch=renovate/webpack-5.x -->Update dependency webpack to v5
- [ ] <!-- unlimit-branch=renovate/webpack-cli-5.x -->Update dependency webpack-cli to v5
- [ ] <!-- unlimit-branch=renovate/webpack-dev-server-5.x -->Update dependency webpack-dev-server to v5
- [ ] <!-- unlimit-branch=renovate/webpack-merge-5.x -->Update dependency webpack-merge to v5
- [ ] <!-- unlimit-branch=renovate/major-jest-monorepo -->Update jest monorepo to v29 (major) (`babel-jest`, `jest`)
- [ ] <!-- create-all-rate-limited-prs -->🔐 **Create all rate-limited MRs at once** 🔐
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate/babel-eslint-replacement -->[Replace dependency babel-eslint with @babel/eslint-parser](!330)
- [ ] <!-- rebase-branch=renovate/vue-test-utils-1.x -->[Update dependency @vue/test-utils to v1.3.6](!331)
- [ ] <!-- rebase-branch=renovate/vue-monorepo -->[Update vue monorepo to v2.7.16](!230) (`vue`, `vue-template-compiler`)
- [ ] <!-- rebase-branch=renovate/babel-monorepo -->[Update babel monorepo](!294) (`@babel/core`, `@babel/plugin-transform-runtime`, `@babel/preset-env`, `@babel/runtime`)
- [ ] <!-- rebase-branch=renovate/babel-loader-8.x -->[Update dependency babel-loader to v8.3.0](!320)
- [ ] <!-- rebase-branch=renovate/sass-1.x -->[Update dependency sass to v1.72.0](!332)
- [ ] <!-- rebase-branch=renovate/vuex-3.x -->[Update dependency vuex to v3.6.2](!328)
- [ ] <!-- rebase-branch=renovate/vue-test-utils-2.x -->[Update dependency @vue/test-utils to v2](!307)
- [ ] <!-- rebase-branch=renovate/css-loader-6.x -->[Update dependency css-loader to v6](!309)
- [ ] <!-- rebase-branch=renovate/eslint-8.x -->[Update dependency eslint to v8](!310)
- [ ] <!-- rebase-all-open-prs -->**Click on this checkbox to rebase all open MRs at once**
## Detected dependencies
<details><summary>dockerfile</summary>
<blockquote>
<details><summary>Dockerfile</summary>
- `node 16-alpine`
</details>
</blockquote>
</details>
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
- `node 20-alpine`
</details>
</blockquote>
</details>
<details><summary>npm</summary>
<blockquote>
<details><summary>package.json</summary>
- `@babel/runtime 7.19.0`
- `axios 0.27.2`
- `clipboard 2.0.11`
- `element-ui 2.15.12`
- `js-cookie 2.2.1`
- `localforage 1.10.0`
- `lodash 4.17.21`
- `lodash.debounce 4.0.8`
- `marked 0.8.2`
- `luxon 3.1.1`
- `normalize.css 7.0.0`
- `nprogress 0.2.0`
- `numeral 2.0.6`
- `tiptap 1.32.2`
- `tiptap-extensions 1.35.2`
- `vue 2.7.8`
- `vue-i18n 8.28.2`
- `vue-router 3.6.5`
- `vuex 3.0.1`
- `@babel/core 7.19.1`
- `@babel/plugin-syntax-dynamic-import 7.8.3`
- `@babel/plugin-transform-runtime 7.19.1`
- `@babel/preset-env 7.19.1`
- `@vue/babel-helper-vue-jsx-merge-props 1.4.0`
- `@vue/babel-preset-jsx 1.4.0`
- `@vue/test-utils 1.3.3`
- `autoprefixer 10.4.16`
- `babel-eslint 8.2.6`
- `babel-helper-vue-jsx-merge-props 2.0.3`
- `babel-jest 25.5.1`
- `babel-loader 8.2.5`
- `babel-plugin-dynamic-import-node-babel-7 2.0.7`
- `babel-plugin-transform-es2015-modules-commonjs 6.26.2`
- `compression-webpack-plugin 2.0.0`
- `connect 3.7.0`
- `cross-env 7.0.3`
- `css-loader 1.0.1`
- `eslint 4.19.1`
- `eslint-friendly-formatter 4.0.1`
- `eslint-loader 2.2.1`
- `eslint-plugin-vue 4.7.1`
- `file-loader 1.1.11`
- `flush-promises 1.0.2`
- `hash-sum 1.0.2`
- `html-webpack-plugin 3.2.0`
- `jest 25.5.4`
- `jest-transform-stub 2.0.0`
- `mini-css-extract-plugin 0.12.0`
- `sass 1.57.1`
- `optimize-css-assets-webpack-plugin 5.0.8`
- `ora 3.4.0`
- `path-to-regexp 2.4.0`
- `postcss 8.4.20`
- `postcss-loader 4.3.0`
- `postcss-url 10.1.3`
- `rimraf 2.7.1`
- `sass-loader 7.3.1`
- `script-loader 0.7.2`
- `semver 5.7.1`
- `serve-static 1.15.0`
- `svg-sprite-loader 3.9.2`
- `svgo 2.8.0`
- `uglifyjs-webpack-plugin 1.3.0`
- `vue-jest 4.0.1`
- `vue-loader 15.10.1`
- `vue-style-loader 4.1.3`
- `vue-template-compiler 2.7.8`
- `webpack 4.46.0`
- `webpack-cli 3.3.12`
- `webpack-dev-server 3.11.3`
- `webpack-merge 4.2.2`
- `node >= 6.0.0`
- `npm >= 3.0.0`
- `prosemirror-model 1.18.3`
</details>
</blockquote>
</details>https://git.pleroma.social/pleroma/admin-fe/-/issues/207Don't mix UI with technical jargon2022-09-18T06:33:51ZIljaDon't mix UI with technical jargonThis came up when talking to @fristi
On the one hand we have technical terms, like the name of a module. On the other hand you have settings where you activate said module. Currently admin-fe uses the name of the modules instead of a mo...This came up when talking to @fristi
On the one hand we have technical terms, like the name of a module. On the other hand you have settings where you activate said module. Currently admin-fe uses the name of the modules instead of a more human friendly name/description.
This should be improved so that it's more clear what each setting does and what it's about. Terms that are used should be widely known and accepted by end-users. E.g. We shouldn't talk about "status" and "activity". "post" is now the most universally accepted word for a regular message on the timeline.https://git.pleroma.social/pleroma/admin-fe/-/issues/205mfa administration accounts locked out admin-fe2023-04-19T22:39:37ZTassoman Pigimfa administration accounts locked out admin-feI've enabled 2FA/MFA authentication with OTP code but when I try to open admin interface, it simply fails with error 403.
Without presenting any pin code submission form.
My Pleroma installation is now 2.3.0I've enabled 2FA/MFA authentication with OTP code but when I try to open admin interface, it simply fails with error 403.
Without presenting any pin code submission form.
My Pleroma installation is now 2.3.0https://git.pleroma.social/pleroma/admin-fe/-/issues/203Can't insert IPv6 address in RemoteIP.Proxies2021-11-11T23:46:24ZElia ArgentieriCan't insert IPv6 address in RemoteIP.ProxiesI tried adding `::1/128` to Other -> Pleroma.Web.Plugs.RemoteIp -> Proxies, and pleroma crashed due to a malformed string.
Then I disabled RemoteIP and restarted pleroma and I was able to see the string.
It looks like this: ![image](/up...I tried adding `::1/128` to Other -> Pleroma.Web.Plugs.RemoteIp -> Proxies, and pleroma crashed due to a malformed string.
Then I disabled RemoteIP and restarted pleroma and I was able to see the string.
It looks like this: ![image](/uploads/e17ad604dd7db9153f5923abda5452d5/image.png)https://git.pleroma.social/pleroma/admin-fe/-/issues/202Language switcher2021-08-17T12:07:36Zmarcin mikołajczakLanguage switcherLooks like there are (partial?) translation of AdminFE for several languages, but there is no way to switch the language other than modifying cookies. Will there be an option to change the interface language?Looks like there are (partial?) translation of AdminFE for several languages, but there is no way to switch the language other than modifying cookies. Will there be an option to change the interface language?https://git.pleroma.social/pleroma/admin-fe/-/issues/200Option to not require HTTPS (Tor-Only Access)2021-08-09T00:08:03ZmindofjoeOption to not require HTTPS (Tor-Only Access)Pleroma maintains a guide for running a Tor-only instance ([link](https://docs.pleroma.social/backend/configuration/onion_federation/)). The guide runs users through configuration for HTTP-only access, since conventional wisdom says (1) ...Pleroma maintains a guide for running a Tor-only instance ([link](https://docs.pleroma.social/backend/configuration/onion_federation/)). The guide runs users through configuration for HTTP-only access, since conventional wisdom says (1) Tor's encryption and methodology are sufficient and (2) dealing with SSL certificates for onion addresses is tedious at best. Pleroma's Tor guide gives instruction to force the instance's scheme to HTTP as well as disabling CSP.
Unfortunately, when attempting to use AdminFE for administration, it seems AdminFE is requiring HTTPS.
Instructions to disable the requirement in AdminFE or additional instructions in Pleroma's Tor guide to deal with the requirement (additional nginx server blocks for port 443 listening & self-signed certs, maybe?) would help make the user experience seamless.https://git.pleroma.social/pleroma/admin-fe/-/issues/199Bring back emoji management2022-09-02T16:49:52ZHJBring back emoji managementWhy did you remove emoji management???
![image](/uploads/12c094687878921410ed83c700162ab5/image.png)Why did you remove emoji management???
![image](/uploads/12c094687878921410ed83c700162ab5/image.png)https://git.pleroma.social/pleroma/admin-fe/-/issues/197Adding a config value with a map makes AdminFE crash HARD2022-01-10T19:13:12ZAlex GleasonAdding a config value with a map makes AdminFE crash HARDSo I added this to my config file:
```elixir
# Non-RFC HTTP status codes
config :plug, :statuses, %{
# Cloudflare
# https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Cloudflare
520 => "Web Server Returned an Unknown Error",
...So I added this to my config file:
```elixir
# Non-RFC HTTP status codes
config :plug, :statuses, %{
# Cloudflare
# https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Cloudflare
520 => "Web Server Returned an Unknown Error",
521 => "Web Server Is Down",
522 => "Connection Timed Out",
523 => "Origin Is Unreachable",
524 => "A Timeout Occurred",
525 => "SSL Handshake Failed",
526 => "Invalid SSL Certificate",
527 => "Railgun Error"
}
```
Suddenly, AdminFE became unconfigurable. It refused to import config anymore and became greyed out.
I traced it back to this code: https://git.pleroma.social/pleroma/admin-fe/-/blob/4406dce589546797d670391fd1cc524fc1f8f718/src/store/modules/normalizers.js#L227-239
```js
export const valueHasTuples = (key, value) => {
const valueIsArrayOfNonObjects = Array.isArray(value) && value.length > 0 && value.every(el => typeof el !== 'object')
return key === ':meta' ||
key === ':types' ||
key === ':backends' ||
key === ':compiled_template_engines' ||
key === ':compiled_format_encoders' ||
typeof value === 'string' ||
typeof value === 'number' ||
typeof value === 'boolean' ||
value === null ||
valueIsArrayOfNonObjects
}
```
Apart from this function doing **the exact opposite** of what its name implies (eg it returns **false** if the value has tuples), it is whitelisting config values that are maps by name. There are a few problems with this:
1. It doesn't even check the group, it *only* checks the key. What if there are two different groups with the same key and a different type of value?
2. It makes adding new config values with maps impossible without modifying AdminFE.
3. It does not have to be this way. Detecting if the value is a tuple is easy. Just check that it's an object containing a key called "tuple".https://git.pleroma.social/pleroma/admin-fe/-/issues/195Cannot update AdminFE settings: TypeError: e.settings[n] is undefined2021-07-14T14:08:37ZioCannot update AdminFE settings: TypeError: e.settings[n] is undefinedI tried to set my instance's character limit to 100000 and the remote character limit to 2000000 and got this in the browser console when I hit submit:
```
Uncaught (in promise) TypeError: e.settings[n] is undefined
UPDATE_STATE set...I tried to set my instance's character limit to 100000 and the remote character limit to 2000000 and got this in the browser console when I hit submit:
```
Uncaught (in promise) TypeError: e.settings[n] is undefined
UPDATE_STATE settings.js:82
v vuex.esm.js:697
commit vuex.esm.js:389
commit vuex.esm.js:388
_withCommit vuex.esm.js:495
commit vuex.esm.js:387
commit vuex.esm.js:335
n settings.js:162
f runtime.js:63
_invoke runtime.js:293
settings.js:82:27
Babel 4
UpdateState settings.js:153
v vuex.esm.js:704
dispatch vuex.esm.js:426
dispatch vuex.esm.js:332
updateSetting Inputs.vue:390
updateSetting self-hosted:1175
update Inputs.vue:386
update self-hosted:1175
change Inputs.vue:2
VueJS 4
setCurrentValue element-ui.common.js:5402
setCurrentValue self-hosted:1175
handleInputChange element-ui.common.js:5411
handleInputChange self-hosted:1175
VueJS 4
handleChange input.js:885
handleChange self-hosted:1175
VueJS 33
```
Backend Version: 2.3.0-1-gb221d77a
Frontend Version: c3fcbbd9