This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: "https://hubpages.com/privacy-policy#gdpr"

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis 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.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe 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 PixelsWe 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.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
jump to last post 1-3 of 3 discussions (5 posts)

Glitch Sticky Thread

  1. Aficionada profile image87
    Aficionadaposted 6 years ago

    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?

    1. Uninvited Writer profile image85
      Uninvited Writerposted 6 years agoin reply to this

      It wouldn't help, people don't look at the sticky threads that are there now.

      1. Aficionada profile image87
        Aficionadaposted 6 years agoin reply to this

        Owww.  sad  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.

  2. QuestionMaster profile image85
    QuestionMasterposted 6 years ago

    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.

  3. melbel profile image96
    melbelposted 6 years ago

    Or maybe a sticky created and edited by the staff as "known bugs"

 
working