[ 
https://issues.apache.org/jira/browse/SOLR-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534190#comment-13534190
 ] 

Steven Rowe commented on SOLR-4207:
-----------------------------------

Hi Aldo,

The wiki can be edited by anybody - when you see broken links like this, please 
go ahead and fix them yourself.

Until recently, the Solr API docs hosted on the website were not versioned - 
they were changed to reflect the latest release.  Now that they are versioned, 
links will need to be repaired to go to a specific version. 

For example, the DateField link on the SolrQuerySyntax page is currently

{noformat}
http://lucene.apache.org/solr/api/org/apache/solr/schema/DateField.html
{noformat}

but should be 

{noformat}
http://lucene.apache.org/solr/4_0_0/solr-core/org/apache/solr/schema/DateField.html
{noformat}

Just replace {{api/}} with {{4_0_0/solr-core/}}.  See 
http://lucene.apache.org/solr/4_0_0/ for other modules' base URLs.
                
> Links to lucene in wiki are broken
> ----------------------------------
>
>                 Key: SOLR-4207
>                 URL: https://issues.apache.org/jira/browse/SOLR-4207
>             Project: Solr
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Aldo Stracquadanio
>              Labels: documentation
>
> Since 4.0.0 has been released there are all links pointing to the 
> lucene.apache.org domain are broken. Some examples:
> On the SolrQuerySyntax page selecting a link to any function or to either 
> DateField or DateMath will result in a 404.
> On the SearchComponent page selecting any link to a specific component in the 
> first list wil result in a 404.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to