Search teh forums



  • So i tried to do a forum search with the following search entry :

    KB's in a GB

    First entry has an ok content, but links to a completely different thread
     


  • Discourse touched me in a no-no place

    ...?



  •  Indeed. It's probably a Google problem, maybe something went wrong when it was indexing the pages?



  • Look at the URL and you'll immediately see the problem -- Google spidered this thread by clicking "Previous" on another thread.  As soon as thread order changes, the link is broken.

    http://forums.worsethanfailure.com/forums/ThreadNavigation.aspx?PostID=139140&NavType=Previous

    Of course, TRWTF is that pressing enter in the search box at the top of this page searches neither site NOR web. It clears the search box and reloads the same page.



  • TRWTF is that the previous/next buttons don't link directly to the previous/next thread.



  • @freelancer said:

    TRWTF is that the previous/next buttons don't link directly to the previous/next thread.

    SMF does the same thing with its previous/next links... It's incredibly annoying.



  • Perhaps try searching for "KBs in a GB" instead? I can't imagine that unnecessary apostrophe is helping your search relevancy.



  • And just as we mention it, it's fixed now! =o

    I can't imagine that unnecessary apostrophe is helping your search relevancy.

    I agree (the apostrophe is incorrect), but the original topic here had the apostrophe in it.



  • @joemck said:

    Of course, TRWTF is that pressing enter in the search box at the top of this page searches neither site NOR web. It clears the search box and reloads the same page.

    My University's webmail does that. Hitting enter does nothing but reload the search page, you HAVE to click Submit. Here's the HTML:

     ...

    <table><tr>
    <td><input type="submit" name="sub_cancel" value="Cancel"></td>
    <td><input type="submit" name="sub_fresh" value="Search"></td>
    </tr></table>
    ...
    I'm sure a form is supposed to have only ONE submit button! Evidently hitting enter just uses the first one, which is Cancel. 

     



  • @m0ffx said:

    I'm sure a form is supposed to have only ONE submit button! Evidently hitting enter just uses the first one, which is Cancel. 

    A form can have as many submit buttons as you like, and since the activated button is sent along, the information provided by that button that is submitted can be used by the server to process data from the same form in different ways. See http://www.w3.org/TR/html401/interact/forms.html#buttons.

    I also believe that submitting using the first button is the expected behavior when pressing Enter (but I can't find a reference for that right now).



  • @m0ffx said:

    @joemck said:

    Of course, TRWTF is that pressing enter in the search box at the top of this page searches neither site NOR web. It clears the search box and reloads the same page.

    My University's webmail does that. Hitting enter does nothing but reload the search page, you HAVE to click Submit. Here's the HTML:

    My university's webmail decided to use alt-d for "delete e-mail"... 



  • @aib said:

    My university's webmail decided to use alt-d for "delete e-mail"... 
    Expected behavior was?



  • @Lingerance said:

    @aib said:
    My university's webmail decided to use alt-d for "delete e-mail"... 
    Expected behavior was?

    Jump to editing the URL bar? 



  • @capnPedro said:

    @Lingerance said:

    @aib said:
    My university's webmail decided to use alt-d for "delete e-mail"... 
    Expected behavior was?

    Jump to editing the URL bar? 


    That would be why I didn't notice anything, I expect Alt to bring down a menu like it does in every other program (except games). Anyways, F6 does the same thing.



  • @Lingerance said:

    @capnPedro said:

    @Lingerance said:

    @aib said:
    My university's webmail decided to use alt-d for "delete e-mail"... 
    Expected behavior was?

    Jump to editing the URL bar? 


    That would be why I didn't notice anything, I expect Alt to bring down a menu like it does in every other program (except games). Anyways, F6 does the same thing.

    Bah, F6 is too far. (Thanks for the tip, though)

    I like being able to use alt-shorcuts on Firefox; alt-left/right for back/forward, alt-d to jump to the address bar, anything else for custom, site-specific behavior. I did change Firefox' default behavior of using alt-shift-[key] for custom shortcuts for this reason; it's just an awkward combination and I don't mind pages catching alt-f for the file menu, etc. (Commonly used menu items have Ctrl shortcuts anyway) but only has long as they leave alt-d alone.



  • @Daniel15 said:

    @freelancer said:
    TRWTF is that the previous/next buttons don't link directly to the previous/next thread.

    SMF does the same thing with its previous/next links... It's incredibly annoying.

    It is a stupid violation of good practice in websites (one URL, one resource), and my opinion of SMF (otherwise kind of high) just dropped.

    Seriously, if they don't want to link directly, they could at least redirect with 302 Found, which prevents this temporary URL from harboring the same content as the actual thread.
     



  • Wouldn't rel="nofollow" fix that?



  • @Arancaytar said:

    @Daniel15 said:

    @freelancer said:
    TRWTF is that the previous/next buttons don't link directly to the previous/next thread.

    SMF does the same thing with its previous/next links... It's incredibly annoying.

    It is a stupid violation of good practice in websites (one URL, one resource), and my opinion of SMF (otherwise kind of high) just dropped.

    Seriously, if they don't want to link directly, they could at least redirect with 302 Found, which prevents this temporary URL from harboring the same content as the actual thread.
     

    I'll report it to the team and see what they think about changing it in a future release.

    I guess doing it that way saves two database queries per topic view (getting the IDs of the previous and next topic), but I definitely agree when you say that it should return a 302 Found.



  • @Daniel15 said:

    I guess doing it that way saves two database queries per topic view (getting the IDs of the previous and next topic),

    Which leads us to the obvious question: why have this feature at all? Who actually wants to see the 'previous' and 'next' topic, for some arbitrary definition of 'previous' and 'next' that is not apparent? This is not a webcomic.



  • I agree with asuffield, it's a fairly useless feature that seems to pollute an awful lot of forums. I've never known anyone to use the "previous" and "next" buttons before.



  • @Nozz said:

    I agree with asuffield, it's a fairly useless feature that seems to pollute an awful lot of forums. I've never known anyone to use the "previous" and "next" buttons before.
    Exactly. They might just as well both link back to ViewThread.aspx?ThreadID=RAND().



  • @aib said:

    @Lingerance said:
    @capnPedro said:
    Jump to editing the URL bar?

    Anyways, F6 does the same thing.

    Bah, F6 is too far.

    ...leave alt-d alone.

    Another possibility, for such times: Ctrl-L...


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.