[ 
https://issues.apache.org/jira/browse/SOLR-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-10595:
----------------------------
    Attachment: solr_name_to_new.map.txt
                solr_id_to_new.map.txt
                solr_redirects.conf


bq. An elegant approach would be that ...

I'm not really sure that understand what you're suggesting, or how it would be 
beneficial in the long run -- but it definitely seems to be off topic for this 
particular jira given the concensus so far... Did you mean to post that in the 
LUCENE-7924 issue i spun off?

----


Ugh ... it's been far too long since i had to do non-trivial stuff with 
mod_rewrite.  My RewriteMap+RewriteCond-fu was weak and took far longer then i 
expected to get these working...

I've tested the attached solr_redirects.conf as best I could using a 
mock-server, with the attached *.map.txt files generated using the following 
perl scripts...

{noformat}
perl -nle 'chomp; @x = split /\s+/, $_, 3; print "$x[0] /$x[1].html"' < 
../new-page-urls.txt > solr_id_to_new.map.txt

perl -nle 'chomp; @x = split /\s+/, $_, 3; $x[2] =~ s/\s+/\+/g; print "$x[2] 
/$x[1].html"' < ../new-page-urls.txt > solr_name_to_new.map.txt
{noformat}

...and then manually tweaking the entry for "/" and adding the header comments.

I'll open an INFRA ticket with a summary of what we want and link back here.


> Redirect Confluence pages to new HTML Guide
> -------------------------------------------
>
>                 Key: SOLR-10595
>                 URL: https://issues.apache.org/jira/browse/SOLR-10595
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Cassandra Targett
>            Assignee: Hoss Man
>         Attachments: new-page-urls.txt, page-tree.xml, 
> solr_id_to_new.map.txt, solr_name_to_new.map.txt, solr_redirects.conf
>
>
> Once the new Ref Guide is live, we may want to redirect pages from Confluence 
> to the new HTML version. 
> I'm undecided if this is the best idea, I can see pros and cons to it. On the 
> pro side, I think it helps firmly establish the move away from Confluence and 
> helps users adjust to the new location. But I could see the argument that 
> redirecting is overly invasive or unnecessary and we should just add a big 
> warning to the page instead.
> At any rate, if we do decide to do it, I found some Javascript we could tell 
> Confluence to add to the HEAD of each page to auto-redirect. With some 
> probably simple modifications to it, we could get people to the right page in 
> the HTML site: 
> https://community.atlassian.com/t5/Confluence-questions/How-to-apply-redirection-on-all-pages-on-a-space/qaq-p/229949
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to