If a solution is given... Should be tagged as solution

Yes, but they’re diferent types of questions (In one category?) one thing is posting a problem where we need assitance (wich can be a bug) and other is a topic where i don’t know how to get an specific result and the community post steps to achieve that.

I’m saying this cause a see a lot of -notabug- or problems posted in Wappler general

Could it be as simple as changing ‘How to’ to ‘How do I?’ ?

Does the system allow for automatically moving a thread into another category once a solution is ticked? If so, how about ‘How do I?’ contains the initial question, then it’s moved to ‘How to’ once a solution is marked. How does that sound?

I think these are different things. When a person has a question they post in I Need Help/I have a Question category. They get answers there.
The Tips And Tricks / How Tos category will be used for people who want to share some tips an tricks how to do this and that.

Why not allow solutions in the General category?

That’s the default category for posts and since a large percentage of posts are most likely someone looking for help we should be able to mark a solution for them.

"HOW TO " in the years I’ve cruised around programming forums USUALLY was followed with demonstrations of how to solve a Problem with specific steps that might evolve in to what we call “Tutorials”.

Look at the “How To” category on Youtube.
“How To” in English has always invited Problem solvers to show how they devised Solutions .


Having Questions & Confusion about some topic is the common plight of the masses.

But, “How To Solve that Question by doing This” will always be a genius minority and, of course, of greatest value to the rest of us numbskulls.

I was conditioned by years of prowling programming forums to find Solutions in the “How To” category in the Wappler forum. But so often it is loaded with people “having a problem”.

1 Like

Wappler General is for general discussions.
Wappler General > How To (to be renamed to I Need Help or I Have a Question) is the place to ask questions and receive solutions.

It's not that hard to post in the correct category :slight_smile: And i see a lot of people not really caring about this, posting in Uncategorized ...

1 Like

I get it. Ideally posts are in the correct category, but without automation it’s always going to be a challenge to get everyone to understand or follow the normal practices. A compromise is to allow solutions across categories, yes?

Please, I consider that automatic system bumps of old topics should be disable.

If anything, rename 'How to' to 'How to question'.

But if I am really honest, I have no problem with the current name. Often I have moved a question that has a correct answer to the How to category and marked the answer as correct.

2 Likes

Thanks Ben.
I will wait for some more feedback by more users and will then decide what to do with the How To name :slight_smile:

1 Like

I agree with a renaming to make it more clear, combined with more active recategorization.

It often starts with a question and becomes a:

  1. feature request
  2. bug report
  3. Solved question (which with some small effort could often be turned into a “how to do X” guide - by simply combining the question with the answer).

In the long term the knowledge base being created here would benefit from recategorization + some automated reminder to ask the OP to pick a solution in case it hasn’t been picked.

For category names I suggest:

  1. Need help or Help me
  2. Guides or Tutorials

I actually like how to as a category name for guides, but since the meaning has become ‘contaminated’ I suggest to drop it altogether.

2 Likes

That’s my opinion also @ben.
I just want to point 2 things:

  1. There is always the ability to change the topic of a post (the poster, an Ambassador, a Team member…)
  2. We shouldn’t involve the BUG topics in our conversation because they are a different thing. A bug is a bug ONLY IF IT IS CONFIRMED as a bug (from an Ambassador, a Team member etc). We never know if a problem is a bug unless it is investigated (e.g: I forgot to pass the $_GET(id) to SA and it always returns no result… )
    So, BUG topic should remain a solid topic that only Ambassadors or Team members could drop a post in there (I believe so…)
1 Like

I think we (as a community) can confuse a Wappler bug with a bug in our project. The bug category is only for reporting bugs from the App.

I clearly have a bug on my project (see the topic on my first reply) wich can not find.
That’s why I think the “how to” category is not my best option and I guess others has the same opinion (cause they handle the way I do)

I think categories should be named like
-Need help
-How can I do this?
-Tricks/Tutorial/Guide
-Wappler bug

Also have in mind not everybody speaks english naturally, so the names I suggest are explicit for more understanding.

1 Like

Otherwise its a feature!

:smiley:

5 Likes

A surprising, new, undocumented feature we didn’t know about :rofl:

3 Likes