Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Multiple Word Topics/urlencoding/Netscape Linux

posted by Krow on 12:47 PM July 6th, 2001   Printer-friendly   Email story
billmoss writes "In Netscape on Linux, when clicking a topic's image, the search performed returns no results if the topic is more than one word. When %20's are added to the url in place of spaces, the search works. Seems like an easy fix (keep topics to one word ;-)), or maybe just a Netscape/Linux issue."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • by Anonymous Coward
    Spaces in URL's are not allowed! They should indeed be replaced with %20. It just so happens, that certain browsers who ignore standards do their usual trick of letting sloppy designers get away with it. As much as I dislike NS4 (although mozilla rocks!), it is actually right on this one. It shouldn't have to do it for you.
  • I think this is more a Slashcode issue? Because it arises when naming topics with multiple words... shouldn't that be allowed and expected to work on Netscape/Linux?
  • In fry the primary key is now a sequence, so this is no longer an issue. What is happening is that the old create a topic code never tested the key used for the primary key (so you could enter in spaces).

    You can't grep a dead tree.
  • primary key a difference? You mean I can't type in urls like but will have to write something like

    Oh dear.
    (Yes I know that isn't a real URL used in slash - but hopefully you'll see what I mean)
    -- SF and Computing Book News