jump to last post 1-1 of 1 discussions (6 posts)

FIXED: Suggest Links Tool shows only community posts (use FF)

  1. Faceless39 profile image92
    Faceless39posted 4 years ago

    http://s2.hubimg.com/u/6893577_f248.jpg

    OS:  Microsoft
    Browser:  Chrome 20.0.1132.57 m
                   Firefox 13.0.1

    The "suggest links" tool is not working in Chrome on any of my hubs.  I cleared my cache, cookies, browsing history, and restarted my computer.  I then tried Firefox, which also didn't work. 

    I've attached a screenshot of what happens when I click the tool, then highlight a key word.  The link box pops up, but contains no links to either my own hubs or anyone else's.  It just contains the community pages linked to the topic.

    This has been going on for 2 days.  Thanks for looking into this!

    1. Matthew Meyer profile image78
      Matthew Meyerposted 4 years ago in reply to this

      @Faceless39

      Sorry for any frustration this may be causing.

      I was able to reproduce the issue you are experiencing in both Firefox 13 and Chrome 20 in Windows 7.

      I have sent this issue to our engineering team to be addressed.

      Thank you for taking the time to bring this to our attention.

      1. mary615 profile image93
        mary615posted 4 years ago in reply to this

        Thanks for your help.  I really miss that linking tool!

      2. Peggy W profile image89
        Peggy Wposted 4 years ago in reply to this

        Appreciate your help on this.  At least the regular links tool is now working for adding similar hubs at the bottom of our pages.  Will look forward to this being corrected as well.

      3. Faceless39 profile image92
        Faceless39posted 4 years ago in reply to this

        HubPages is at the top of their game; thanks very much for being so quick to reply, and for always addressing our concerns quickly.

        I can speak for all of us:  we appreciate your work and look forward to what's to come.

      4. Matthew Meyer profile image78
        Matthew Meyerposted 4 years ago in reply to this

        This should now be working for all but Internet Explorer.
        The engineering team is working on a resolution for that as well.
        In the meantime, you can use Firefox nd bypass the issues.

 
working