#22706 [Opn]: mirror site has hard-coded links to www.php.net
| From: | goba@php.net | Date: | Wed, 23 Apr 2003 19:48:48 +0000 |
| Subject: | #22706 [Opn]: mirror site has hard-coded links to www.php.net | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-16964@lists.php.net to get a copy of this message | ||
ID: 22706
Updated by: goba@php.net
Reported By: vbhackattack at hotmail dot com
Status: Open
Bug Type: Website problem
Operating System: Windows 2000
PHP Version: 4.3.1
New Comment:
Part of this issue is fixed: Now on the search result pages, links at
the top and bottom navbars also point back to the originating server,
from where the search request came from...
The absolute link issue, is however not solved yet.
Previous Comments:
------------------------------------------------------------------------
[2003-03-17 10:18:47] vbhackattack at hotmail dot com
Regarding hard-coded links to www.php.net on mirror sites:
> It may make sense to make those relative
> links when the manual is generated for php.net
Yes please, feature request :)
------------------------------------------------------------------------
[2003-03-17 10:10:26] vbhackattack at hotmail dot com
Ooops, I spoke too soon on my last post. The "search results" links are
now domain based correctly, but there are other links on the results
page that are still not based correctly, i.e. those in the header and
footer.
I think the problem here is not a question of patching up search
results to re-base them to the source domain. Rather the real problem
is search results should be display by the originating domain not
ch.php.net.
For example, any mirror can post a search request to ch.php.net, then
the search server ch.php.net could post the results back to the
originating server for the latter to display. Or pick another
architecture but keep the display of results under the control of the
originating domain.
------------------------------------------------------------------------
[2003-03-17 09:57:31] vbhackattack at hotmail dot com
Regarding the search base parameter, the links on the results page are
now based on my starting domain. Thank you :)
One observation, the URL of the search results the first time around
contains a whack of query string parameters, whereas for subsequent
searchs the URL is bare. It seems like there are two different
implementations of preserving the search base parameter.
------------------------------------------------------------------------
[2003-03-15 07:00:16] goba@php.net
Can you please check if the search base parameter is carried on for
additional searches as you expected now? Jacques has fixed this.
The links are fixed there, because the same text is included in the
HTML downloadable versions (and will be included in the PDF too), so we
cannot use relative links. It may make sense to make those relative
links when the manual is generated for php.net...
The search issue, is simply by design. If you search on the website,
that means "the website" and not a part of it. If you search in the
manual, that is a part of the website ;) Which is restricted to English
now. We are still working on better language selection modes, so users
really get the language they want automatically. While we still get bug
reports about these, we would not like to start into modifying the
search page too to use those preferences, because that would make more
bug reports about this...
------------------------------------------------------------------------
[2003-03-14 20:07:01] jacques@php.net
Hi
Using the search box on the top of the browser while on the search
results page now remembers which mirror you originated from, so that
when you click on the results it takes you back to the original site
you came from.
There are various links to www.php.net in the manuals, etc. for
downloads, etc. as lots of people do download the manuals for use on
their pc's, and linking to www.php.net does make sense.
Regards
--jm
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/22706
--
Edit this bug report at http://bugs.php.net/?id=22706&edit=1