your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.5k Projects 2 Wiki

It is very cumbersome to change an entry in the FAQ ... #6060

New Issue
Closed
opened 2024-01-23 20:08:53 +00:00 by Boot · 9 comments
Boot commented 2024-01-23 20:08:53 +00:00
Member
Copy Link

... because at the moment you have to write off the previous entry, then delete the old entry and then make the changed entry again. This is ok in itself, but unfortunately there is no way to view the original keywords and thus it can happen that original keywords are lost.

... because at the moment you have to write off the previous entry, then delete the old entry and then make the changed entry again. This is ok in itself, but unfortunately there is no way to view the original keywords and thus it can happen that original keywords are lost.
AliasAlreadyTaken was assigned by Boot 2024-01-23 20:09:01 +00:00
flux added the
1. kind/enhancement
 label 2024-01-24 00:19:20 +00:00
flux commented 2024-01-24 00:19:44 +00:00
Member
Copy Link

probably there should be some formspec to edit faq entries

probably there should be some formspec to edit faq entries
AliasAlreadyTaken commented 2024-01-24 03:07:51 +00:00
Owner
Copy Link

Actually those faq entries are in a git repo. They can be checked out and edited outside, then checked in again.

Now we only need hot reload: #6064

Actually those faq entries are in a git repo. They can be checked out and edited outside, then checked in again. Now we only need hot reload: #6064
👍 1
AliasAlreadyTaken added the
4. step/ready to QA test
 label 2024-01-24 08:13:41 +00:00
AliasAlreadyTaken commented 2024-01-24 08:14:43 +00:00
Owner
Copy Link

Please test, if the git workflow and hotreload works in a less cumbersome way. faq repo is here:

https://gitea.your-land.de/your-land/yl_faq_database

Please test, if the git workflow and hotreload works in a less cumbersome way. faq repo is here: https://gitea.your-land.de/your-land/yl_faq_database
👍 1
AliasAlreadyTaken added this to the 1.1.123 milestone 2024-01-24 08:14:49 +00:00
Boot commented 2024-01-24 15:37:56 +00:00
Author
Member
Copy Link

Accordingly, the FAQ automatically generates almost all words of the question and the answer as searchwords. That was new to me. Then you rarely need to add more searchwords manually.

Accordingly, the FAQ automatically generates almost all words of the question and the answer as searchwords. That was new to me. Then you rarely need to add more searchwords manually.
whosit commented 2024-01-24 16:16:20 +00:00
Member
Copy Link

Is there any reason json files have non-descriptive number names like 12.json instead of named after the keyword like priest.json?
Using only web editor is hard to find the right one...

Is there any reason json files have non-descriptive number names like `12.json` instead of named after the keyword like `priest.json`? Using only web editor is hard to find the right one...
AliasAlreadyTaken commented 2024-01-24 16:54:08 +00:00
Owner
Copy Link

The search words are meant to complement the question and answer. You'd add words there that do not appear directly in either, but are synonyms people might search for when they in fact want the entry.

The search words are meant to complement the question and answer. You'd add words there that do not appear directly in either, but are synonyms people might search for when they in fact want the entry.
whosit commented 2024-01-28 19:50:27 +00:00
Member
Copy Link

f199e0992a
I've added an entry through gitea web interface...

But it does not seem able to pull it using /faq_reload. Or maybe there's an error but I can't see it...

https://gitea.your-land.de/your-land/yl_faq_database/commit/f199e0992a3c470f9b86cb20cf5002fdf358ef02 I've added an entry through gitea web interface... But it does not seem able to pull it using `/faq_reload`. Or maybe there's an error but I can't see it...
AliasAlreadyTaken commented 2024-01-29 06:25:16 +00:00
Owner
Copy Link

That's because on top of adding them to git, the Alias must pull them to the server. Which he just did.

That's because on top of adding them to git, the Alias must pull them to the server. Which he just did.
AliasAlreadyTaken added the
ugh/QA OK
 label 2024-03-12 13:21:07 +00:00
flux added
5. result/fixed
 and removed
4. step/ready to QA test
 labels 2024-03-28 20:45:43 +00:00
AliasAlreadyTaken was unassigned by flux 2024-03-28 20:45:46 +00:00
flux commented 2024-03-28 20:46:01 +00:00
Member
Copy Link

this is live (or at least the command is available)

this is live (or at least the command is available)
flux closed this issue 2024-03-28 20:46:01 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
ugh/QA NOK

Fix didn't yield the expected results

  
ugh/QA OK

tested

No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
Milestone
Clear milestone
No items
No Milestone
1.1.123
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#6060
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?