It can be difficult to search through dozens of threads to find out whether a particular glitch has already been mentioned by other Hubbers.
I would like to see (permanently) a sticky forum thread where Hubbers can report whatever problem is happening currently and check with relative ease to see whether others have reported the same thing. Here, I'm not talking about suggestions for improvements, upgrades, new ideas, etc. - just actual problems.
Obviously, it would get full and unwieldy at some point. The solution to that that I would suggest would be to decide on a maximum number of posts (or pages), close the thread when it reaches the maximum, and open a new one. - Still easier to search, IMO. - OR, as a second option, a time period could be the factor for choosing when to close the old one and open a new one. A week? Longer? Shorter? (Staff should probably select the time length.)
Does anyone else think this is a good idea?
It wouldn't help, people don't look at the sticky threads that are there now.
Owww. That sounds like defeatism.
I have seen some sticky threads receive hundreds of posts, and it seems to depend on the topic.
I don't believe that what I suggested would completely do away with the matter of multiple threads reporting the same technical problems, but I believe it could be a big step towards making the process more efficient. As a matter of fact, melbel's suggestion sounds like a great one. Hubbers could check first to see whether their issue has been noted by staff, before opening a new thread.
With any attempt at a solution, there would probably be some period of learning the system. But I believe either of these suggestions would be an improvement over the free-for-all arrangement we have now.
QM, thanks for your contribution. I'm uncertain about your suggestion right now, because it seems to me to open up the possibility of throwing hundreds of tickets at the engineers. However, I realize that the staff are in a better position to evaluate the potential of that idea than I am.
Actually, I think it would be better to have a whole different section for problems.
"Tickets". People can open a ticket about a problem, add to other tickets, file them under different sections (hub, forum, affiliates etc) and staff can close them when the problem is fixed.
Or maybe a sticky created and edited by the staff as "known bugs"
by Person of Interest 6 weeks ago
Why do I say that? Because I'm guessing something happened that motivated HP to include this in the HubPages Weekly:*Start*What Are the HubPages Forums for? Are There Any Rules?The Forums allow the community to complement each individual Hubber’s talents and interests. We hope they provide a...
by Kate Swanson 5 years ago
I just noticed that Matthew replied to a question from a Hubber and immediately closed the threadThere used to be an unspoken policy on the forums - a thread was only closed if things got too heated and unpleasant. I hope that policy is not going to change, for several reasons. For one thing,...
by Laurel Rogers 6 years ago
Now I have nothing against Nincomp, that sweet lil pony who started a wildly successful thread so very long ago-http://hubpages.com/forum/topic/15440#top...But, folks, don't you think we're acting somewhat like lemmings in search of the unattainable cliff without a ledge?Seems to me that we,...
by Kenna McHugh 11 months ago
I am impressed that every now and then an old thread pops up with a new comment. Some threads are 6 years, 7 years or older. Nice to know Hubbers are still interested enough to comment.
by Judi Brown 5 years ago
I know it's been suggested before, but please reconsider allowing threads concerning sites posting stolen content to be stickied.Just today there are several threads regarding the same sites, people cross-posting and getting mixed up on which site is being discussed. It's not surprising; the...
by Tina 9 years ago
I was just curious. I have not seen a lot of hubbers that have been here at Hubpages for over two years..perhaps they are too busy hubbing away!
Copyright © 2019 HubPages Inc. and respective owners. Other product and company names shown may be trademarks of their respective owners. HubPages® is a registered Service Mark of HubPages, Inc. HubPages and Hubbers (authors) may earn revenue on this page based on affiliate relationships and advertisements with partners including Amazon, Google, and others.
|HubPages Device ID||This is used to identify particular browsers or devices when the access the service, and is used for security reasons.|
|Login||This is necessary to sign in to the HubPages Service.|
|HubPages Traffic Pixel||This is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.|
|Remarketing Pixels||We may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.|
|Conversion Tracking Pixels||We may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.|