![]() |
|
|||
|
Double // issue
Can someone please explain why this forum and the links within all appear to be suffering from a double // issue?
I say this because some browsers have a problem with such incorrect formatting plus it breaks some of the redirects. Ex. I tried to reply to a post the link was like below: http://www.dvdrbase.com//reply.php?blahblahblah For some reason the forum thought I wasn't logged in. So it sent me wanted me to login. Fine, that should have worked. However, after I logged in the redirect went to http://reply.php/?blahblahblah Naturally that did not work. This was a direct result of the double //. Actually even coming to post this message the link was: http://www.dvdrbase.com//newthread.php?do=newthread&f=8 that was from clicking on the New Thread Link at the top of this forum. Is there any chance this can be looked into and corrected? Sorry it this has been mentioned, but search does not accept // and return results. |
|
|||
|
Unless already fixed, the page source looks ok to me in IE 5.5sp2 on Win98SE
Are you using an unusual browser, or page modifier such as proxomitron ? AH! - UNTIL I replied and now I can see it! http://www.dvdrbase.com//showthread....592#post204592 I'll add some feedback for the Admins......
__________________
¡uʍop ǝpısdn ɹoʇıuoɯ ʎɯ pǝuɹnʇ oɥʍ ¡ʎǝɥ |
|
||||
|
i got the same thing, but firebird doesnt care about it so no prob for me.
i think its a problem of the redirect: new page for index.php -> forums are ok, posts too, the link for get new posts is fine but the page that appears then has //search.php... lets wait for nb ... forti
__________________
..:: Goddamn not an angel when i die. ::.. ..:: Heaven must be hell in the sky. ::.. |
|
|||
|
Quote:
Actually I do use Proxomitron and originally thought that might be the cause. I then completely removed my proxy settings from the browser and tried with the same results. For now I have just made a real quick and dirty Proxomitron filter to fix the problem locally for myself. If anyone wants the filter just let me know. Since I was the only one who had any issue with the // I gather most browsers work just fine with it. I am working with some not quite up to snuff browser code so that could be why it chokes on it occasionally. Still it is technically not properly linked. Whether it's worth the effort to fix it or not, I don't know. That's for the site owner to decide. Just figured I would point it out.
|
|
|||
|
Well, I'm pretty sure it wasn't like it before ... it's probably some fallout from the Forum update to VBB 3.0.0 RC1 ... surprised it wasn't an issue in the supposedly high risk "gamma" update, where a LOT of new stuff was rolled out.
It could be an issue that ends up back at Jelsoft (VBB developer) for 3.0.0 final
__________________
¡uʍop ǝpısdn ɹoʇıuoɯ ʎɯ pǝuɹnʇ oɥʍ ¡ʎǝɥ |
|
|||
|
The update to VBB 3.0.0 RC2 (or other changes as a result) seems to have fixed it for me.
If you are still having this problem, please report back here.
__________________
¡uʍop ǝpısdn ɹoʇıuoɯ ʎɯ pǝuɹnʇ oɥʍ ¡ʎǝɥ |