[
https://issues.apache.org/jira/browse/SOLR-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-10595:
----------------------------
Attachment: new-page-urls.txt
bq. ask infra to modify the cwiki configs so any
{{https://cwiki.apache.org/confluence/display/solr/.*}} URLs get rewritten ...
Hmmm... the only hitch to that plan is that for pages with "special" characters
in their names, cwiki doesn's use URLs with the space ({{/solr/}} in them, and
just uses the pageId as the URL...
* Cross Data Center Replication (CDCR)
** https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62687462
* Collections / Core Admin
** https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=32604191
* Plugins & Stats Screen
** https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=32604180
...i think there are handul more like that (with "/" in their title)
In any case, i'm attaching a tab delimited file based on the page-tree.xml that
cassandra provided with the {{pageId,new-short-name,Original Title}} of every
cwiki page -- we can ultimately use this to create whatever type of redirect
mapping we need (mod_rewrite {{RewriteMap}} dbm file, javascript, whatever...)
----
File created via with the following perl one liner, followed by a little manual
cleanup...
{code}
perl -nle 'if (/<page id="(.*?)" title="(.*?)"/) { my ($n, $title) = ($1,$2);
my $url = $title; $url =~ tr/A-Z/a-z/; $url =~ s/[^a-z0-9]+/-/g; print
"$n\t$url\t$title" }' < page-tree.xml > new-page-urls.txt
{code}
> 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
> Attachments: new-page-urls.txt, page-tree.xml
>
>
> 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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
