I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Migrated /ticket919

Browse Source
This commit is contained in:
str4d
2013-05-24 02:11:52 +00:00
parent bc6f8e4b88
commit 5ff9938899
2 changed files with 12 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
i2p2www/legacy.py
View File

@ -101,6 +101,7 @@ LEGACY_PAGES_MAP={
'supported_applications': 'docs/applications/supported', 'supported_applications': 'docs/applications/supported',
'team': 'about/team', 'team': 'about/team',
'techintro': 'docs/how/tech-intro', 'techintro': 'docs/how/tech-intro',
'ticket919': 'misc/ticket919',
'todo': 'volunteer/todo', 'todo': 'volunteer/todo',
'transition-guide': 'misc/transition-guide', 'transition-guide': 'misc/transition-guide',
'transition-guide.txt': 'misc/transition-guide.txt', 'transition-guide.txt': 'misc/transition-guide.txt',

22
www.i2p2/pages/ticket919.html → i2p2www/pages/site/misc/ticket919.html
View File

@ -1,11 +1,11 @@
{% extends "_layout.html" %} {% extends "global/layout.html" %}
{% block title %}Ticket 919/920 fix{% endblock %} {% block title %}Ticket 919/920 fix{% endblock %}
{% block content %} {% block content %}
<p>The issue described on this page only affects Windows systems that originally installed I2P <p>The issue described on this page only affects Windows systems that originally installed I2P
with version 0.9.5. Other operating systems are not affected. with version 0.9.5. Other operating systems are not affected.
</p> </p>
<p>This issue has been corrected as of the <a href="http://mirror.i2p2.de/i2pinstall_0.9.5-win1_windows.exe">0.9.5-win1 release</a>.</p> <p>This issue has been corrected as of the <a href="{{ get_url('downloads_select', file='i2pinstall_0.9.5-win1_windows.exe') }}">0.9.5-win1 release</a>.</p>
@ -25,7 +25,7 @@ eepsite it is important to follow this procedure prior to upgrading to 0.9.6.
</p> </p>
<p> <p>
Tickets <a href="http://trac.i2p2.de/ticket/919">919</a> &amp; <a href="http://trac.i2p2.de/ticket/920">920</a> correspond to this issue. Tickets <a href="http://{{ i2pconv('trac.i2p2.i2p') }}/ticket/919">919</a> &amp; <a href="http://{{ i2pconv('trac.i2p2.i2p') }}/ticket/920">920</a> correspond to this issue.
</p> </p>
<h2>Fixing the configuration</h2> <h2>Fixing the configuration</h2>
@ -37,20 +37,20 @@ eepsite it is important to follow this procedure prior to upgrading to 0.9.6.
<ol> <ol>
<li>From the Home page of the I2P Router Console, click the I2P logo in the upper-left corner. <li>From the Home page of the I2P Router Console, click the I2P logo in the upper-left corner.
<a href="/_static/images/ticket919/home.png"> <a href="{{ url_for('static', filename='images/ticket919/home.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="/_static/images/ticket919/home.png" /></a> <img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/home.png') }}" /></a>
</li> </li>
<li>Click the <a href="http://127.0.0.1:7657/configclient">I2P Services</a> link. <li>Click the <a href="http://127.0.0.1:7657/configclient">I2P Services</a> link.
<a href="/_static/images/ticket919/i2p-services.png"> <a href="{{ url_for('static', filename='images/ticket919/i2p-services.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="/_static/images/ticket919/i2p-services.png" /></a> <img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/i2p-services.png') }}" /></a>
You should see something like the following: You should see something like the following:
<a href="/_static/images/ticket919/paths.png"> <a href="{{ url_for('static', filename='images/ticket919/paths.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="/_static/images/ticket919/paths.png" /></a> <img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/paths.png') }}" /></a>
If the path at number 1 in the image above is set to <code>eepsite/jetty.xml</code>, the path needs to be updated. If the path at number 1 in the image above is set to <code>eepsite/jetty.xml</code>, the path needs to be updated.
</li> </li>
<li>Click the <code>Edit</code> button next to <em>I2P webserver (eepsite)</em>. The page will reload to allow the path to be edited as shown below: <li>Click the <code>Edit</code> button next to <em>I2P webserver (eepsite)</em>. The page will reload to allow the path to be edited as shown below:
<a href="/_static/images/ticket919/edit.png"> <a href="{{ url_for('static', filename='images/ticket919/edit.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="/_static/images/ticket919/edit.png" /></a> <img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/edit.png') }}" /></a>
Insert the full path to your I2P configuration directory <em>before</em> the text "eepsite/jetty.xml" as shown above, Insert the full path to your I2P configuration directory <em>before</em> the text "eepsite/jetty.xml" as shown above,
then click Click the <code>Save Client Configuration</code> button. then click Click the <code>Save Client Configuration</code> button.
</li> </li>