Ask a Support Question

Questions already answered:

• AnsweredQuestions lists questions that are already answered.
  (Use WebSearch or Google:site:twiki.org+myproblem to find answers to your question that are already written - faster than waiting for a new answer!)
• Search for answered questions by
  Category: Select... Add-Ons Authentication Browser issue Contributing code Documentation Fatal error Forms General Usage Mail Missing functionality Performance Permissions Plugins Registration Search Security Skin Statistics Tables Version control

How to ask a new question:

• Each question is a TWiki topic - please ask a new question in a new topic, rather than adding to a current one where it can get lost.
• Please read the SupportGuidelines now so that you know what information to include, helping you get a quick and useful answer - filling in this form is not enough for installation problems
• You need username and password to edit pages - please create your own account in TWikiRegistration. You also can post anonymously as TWikiGuest, password is guest (case sensitive!).
• In case you find the answer by yourself after submitting a question: We would appreciate if you could document this here in your question and set the SupportStatus to AnsweredQuestions. That way you help making the Support web self-organized and more useful.

Questions Asked but Not Yet Answered

If you answer a question - or have a question you asked answered by someone - please remember to set the status in the form to answered!!

TableInsidBullets	r2 - 2020-07-15 - 14:35	PeterJones
Question Dear expert, I tried to create a table inside the bullets, but I can`t align the table just under the bullet. The idea case is a s like the table inside...
ConvertpublictwikitoCMSprivate	r1 - 2022-12-07 - 10:19	SwetaBaradia
Question How can we convert a existing public twiki into CMS private twiki? Environment Web Browser: Chrome User Location: External Categories...
SaveNotWorking	r1 - 2023-09-05 - 16:40	PierreDepasse
Question Since a few weeks, when I click on `Save`, `Quiet save` or `Save and Continue`, I obtain a message : ATTENTION The save script can only be called with POST...
HowToRestoreAPage	r1 - 2024-04-09 - 12:20	MohammadrezaEbrahimiKhuzani
Question Dear support, A few days ago, I wanted to create my personal document on TWiki by editing a page named ...

Discussions

Sam changed the order from newest questions first to oldest questions first. I am a bit concerned for the following reasons:

• Good first time impression: For an open source project it is important to give a good first time impression; showing newest questions last will reduce the number of quickly answered questions.
• Many unanswered questions: At any time we have 20 to 40 open questions. Unanswered questions get lost in the middle of the list. The reality is that stale questions are not looked at anyway. Once a month I close unanswered questions (there are many each time).
• Inconsistency: Support.WebHome shows asked questions in one direction, assigned and answered question the other way.

Overall I prefer to give a good first time impression 90% of the time with 5% unaswered q's, vs. an increase in bad first impression with a few more older questions answered. Nevertheless, lets keep this as an experiment for a while to see how this works out.

A better question to ask is how to get the the TWikiCommunity more involved in helping out in the Support web. If you look at the WebStatistics you can see that usually is the same few people who are answering questions.

-- PeterThoeny - 29 Apr 2006

"The reality is that stale questions are not looked at anyway"

Are they not looked at because they are stale or are they stale because they are not looked at. Maybe they remain unanswered because they are at the bottom of the list and people don't even get the opportunity to review them.

I reversed the order so that the oldest, an possibly overlooked or forgotten questions appeared first because I wanted to avoid people, myself included, from cherry picking the new questions without looking at the older unanswered questions.

If the most recently updated topics are at the top then it's easy for the more tricky to answer questions to disappear "below the fold" and take even longer to get answered. At the time of writing there are two NEW questions that haven't been answered by anyone near the middle and there's one NEW one that's almost the oldest one there. Once questions get to the bottom (where bottom = oldest update) it's even more likely that they will have to wait.

But if questions that have been replied to the least recently are at the top then they remain there for everyone to see. So they'll just get skipped over anyway, but at least people have to look at them every time. If they are going to get skipped over anyway then it makes no difference to those topics that would be skipped over, but if there is a topic that has been overlooked because of updates to a lot of other support topics, forcing it down the list, then if the oldest are at the top then it's more likely it will be seen.

Let's leave it like this for a bit and see what effect it has on how questions are answered.

-- SamHasler - 29 Apr 2006

Recently the topic name field got limited to 32 characters and that does not allow a proper descriptive question as topic name.

Look at the history of questions. Quite many are up round 40. I had a hell of a time making a good topic name the other day. We will end up with poor 2-3 word topic names like that do not tell what is underneath the question. Please leave at least 40 characters.

-- KennethLavrsen - 03 Aug 2006

We should cater for a minimum screen size of 1024x768. I initially set the topic maxlength to 32 chars to account for that, now increased to 36. I think this is a good balance between concise topic lists (header rows do not wrapped around) and understandable topic names.

-- PeterThoeny - 04 Aug 2006

-- PeterJones - 04 Nov 2007