SQ free urls for external links [message #15949 is a reply to message #15925] |
Sat, 10 January 2004 14:55 |
|
Wild_Cat
Messages: 144 Registered: November 2002 Location: Odessa, Ukraine
Karma:
|
Senior Member |
|
|
Just one more question about SQ string in the url:
The notification e-mails do have an SQ free URL of the form:
http://fud.prohost.org/forum/index.php?t=rview&goto=15935
More, you do have send a link option, making an SQ free url of the form:
http://fud.prohost.org/forum/index.php?t=rview&th=3275&rid=542
(BTW, what is user_id doing here? )
If I want to provide a separate 'link' url on my forum messages or threads for external linking (smth like {LINK}) thingy over a thread or {LINK} over a message), could this be a better option to make a similar url formations instead of just stripping SQ & rid from the url?
Oups, a FUDcode surprise with double square brackets:
It works just fine for obtaining [internal forum code] when used like this: [[url=?t=rview&th=3275]internal forum code[/url]] (as seems logical without any additional transformations)
But when I tried to write an external link in double square brackets like this [[url=http://fud.prohost.org/forum/index.php?t=rview&th=3275]LINK[/url]] I've got a desired linked text [LINK] but look at the url behind it: http://fud.prohost.org/forum/<br />http://fud.prohost.org/forum/index.php?t=rview&th=3275 especially the <br /> thingy looks strange, although I don't understand why and what for this transformation occured at all (certainly I just don't know something about new FUDcode? for in the 2.5.3 the double square brackets just made the url FUDtage not work as a tag any more but handled as simple message text, which gave the brackets and the url words visible and transformed the url itself to a link if it was a normal URI, not jut a query string, of course)
----------
P.S. My oh my, somtimes I still get dropped out to index with url like http://fud.prohost.org/forum/index.php?S=4ebbb111ee9ed71e2d354c5a5c495748 instead of posting or previewing my message! Could be totally disastrous with IE which doesn't keep the form text fields entered content on 'next' or 'back' navigation (the more with your anti-cashe headers and the more that it's still somehow the heckmost used browser I am allergic to ...) and I'm afraid it will do the trick to our users with this new engine, what's the possible cause of it? (then I go back and add this text and hit 'preview' or 'post' again and it would work fine)
Lady of Avalon
|
|
|