self-hosted/joplin
1
0
Fork 0
mirror of https://github.com/laurent22/joplin.git synced 2025-01-23 18:53:36 +02:00
Code Issues Releases Activity

Updated website

Browse Source
This commit is contained in:
Laurent Cozic 2018-06-11 22:10:04 +01:00
parent b08dcdfd90
commit f79326b2d5
2 changed files with 31 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/clipper/index.html
View File

@ -246,7 +246,7 @@
</li>
</ul>
</div>
<h2 id="troubleshooting-the-web-clipper-service">Troubleshooting the web clipper service</h2>
<h1 id="troubleshooting-the-web-clipper-service">Troubleshooting the web clipper service</h1>
<p>The web clipper extension and the Joplin application communicates via a service, which is started by the Joplin desktop app.</p>
<p>However certain things can interfer with this service and prevent it from being accessible or from starting. If something does not work, check the following:</p>
<ul>
@ -258,7 +258,8 @@
</li>
</ul>
<p>If none of this work, please report it on the <a href="https://discourse.joplin.cozic.net/">forum</a> or <a href="https://github.com/laurent22/joplin/issues">GitHub issue tracker</a></p>
<h2 id="debugging-the-extension">Debugging the extension</h2>
<h1 id="debugging-the-extension">Debugging the extension</h1>
<h2 id="in-chrome">In Chrome</h2>
<p>To provide as much information as possible when reporting an issue, you may provide the log from the various Chrome console.</p>
<p>To do so, first enable developer mode in <a href="chrome://extensions/">chrome://extensions/</a></p>
<h3 id="debugging-the-popup">Debugging the popup</h3>
@ -267,6 +268,16 @@
<p>In <code>chrome://extensions/</code>, click on &quot;Inspect background script&quot;.</p>
<h3 id="debugging-the-content-script">Debugging the content script</h3>
<p>Press Ctrl+Shift+I to open the console of the current page.</p>
<h2 id="in-firefox">In Firefox</h2>
<ul>
<li>Open <a href="about:debugging">about:debugging</a> in Firefox.</li>
<li>Make sure the checkox &quot;Enable add-on debugging&quot; is ticked.</li>
<li>Scroll down to the Joplin Web Clipper extension.</li>
<li>Click on &quot;Debugging&quot; - that should open a new console window.</li>
</ul>
<p>Also press F12 to open the regular Firefox console (some messages from the Joplin extension can go there too).</p>
<p>Now use the extension as normal and replicate the bug you&#39;re having.</p>
<p>Copy and paste the content of both the debugging window and the Firefox console, and post it to the <a href="https://discourse.joplin.cozic.net/">forum</a>.</p>
<script>
function stickyHeader() {

19
readme/clipper.md
View File

@ -1,4 +1,4 @@
## Troubleshooting the web clipper service
# Troubleshooting the web clipper service
The web clipper extension and the Joplin application communicates via a service, which is started by the Joplin desktop app.
@ -12,7 +12,9 @@ However certain things can interfer with this service and prevent it from being
If none of this work, please report it on the [forum](https://discourse.joplin.cozic.net/) or [GitHub issue tracker](https://github.com/laurent22/joplin/issues)
## Debugging the extension
# Debugging the extension
## In Chrome
To provide as much information as possible when reporting an issue, you may provide the log from the various Chrome console.
@ -29,3 +31,16 @@ In `chrome://extensions/`, click on "Inspect background script".
### Debugging the content script
Press Ctrl+Shift+I to open the console of the current page.
## In Firefox
- Open [about:debugging](about:debugging) in Firefox.
- Make sure the checkox "Enable add-on debugging" is ticked.
- Scroll down to the Joplin Web Clipper extension.
- Click on "Debugging" - that should open a new console window.
Also press F12 to open the regular Firefox console (some messages from the Joplin extension can go there too).
Now use the extension as normal and replicate the bug you're having.
Copy and paste the content of both the debugging window and the Firefox console, and post it to the [forum](https://discourse.joplin.cozic.net/).