tag:support.multimarkdown.com,2013-02-12:/discussions/betas/28-sandboxingMultiMarkdown Software, LLC: Discussion 2017-09-18T22:19:39Ztag:support.multimarkdown.com,2013-02-12:Comment/432254162017-08-16T20:15:49Z2017-08-16T20:15:49Zsandboxing<div><p>I enabled Sandboxing for exactly this reason -- too many things sneak by when it's turned off and enabled in later testing.</p>
<p>Sandboxing compatibility should be finished in the next day or two.</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-08-19T02:13:58Z2017-08-19T02:13:58Zsandboxing<div><p>v16 includes support for sandboxing access in the preview (e.g. images) and in file transclusion.</p>
<p>Let me know how it works -- it's been rewritten from scratch since Composer v2, so needs some more testing.</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T14:39:58Z2017-09-17T14:39:59Zsandboxing<div><p>hi</p>
<p>I eagerly just tried the new version from the app store. Looks great, but I’m still confused about sandboxing. My indirect referencing to image locations is not followed.</p>
<p>Thanks for the pro redemption but there was no way to apply it so I purchased pro as successive update from purchased standard.</p>
<p>thanks<br>
Ray Brock</p>
<p>On Aug 18, 2017, at 10:13 PM, Fletcher > wrote:</p></div>Raymond Brocktag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T14:47:40Z2017-09-17T14:47:40Zsandboxing<div><p>Send me an example of a file that is not working. If you use a proper<br>
URL, Composer will ask for permission to access the necessary folder.</p>
<p>Sorry that you couldn't redeem the Pro token -- you redeem it in the App<br>
Store app (all purchases handled by Apple). Instead, share it with<br>
someone who you think would benefit from using Composer.</p>
<p>Fletcher</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T14:52:56Z2017-09-17T14:52:56Zsandboxing<div><p>Hmm... I just checked on machine, and it seems that something broke in<br>
the App Store build in regards to sandboxing....</p>
<p>Let me dig into it.</p>
<p>F-</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T15:01:41Z2017-09-17T15:01:41Zsandboxing<div><p>I think I figured it out -- sandboxing is ok, there's an issue where<br>
it's only finding images defined by reference:</p>
<p>e.g.</p>
<pre>
<code>![foo][bar]
[bar]:/path/to/image</code>
</pre>
<p>works, but this doesn't:</p>
<pre>
<code>![foo](/path/to/image)</code>
</pre>
<p>Can you verify that fixes it for you? I'll fix for next release.</p>
<p>Fletcher</p>
<p>On 9/17/17 10:52 AM, Fletcher T. Penney wrote:</p>
<blockquote>
<p>Hmm... I just checked on machine, and it seems that something broke in the App Store build in regards to sandboxing....</p>
<p>Let me dig into it.</p>
<p>F-</p>
<p>On 9/17/17 10:47 AM, Fletcher T. Penney wrote:</p>
<blockquote>
<p>Send me an example of a file that is not working. If you use a proper URL, Composer will ask for permission to access the necessary folder.</p>
<p>Sorry that you couldn't redeem the Pro token -- you redeem it in the App Store app (all purchases handled by Apple). Instead, share it with someone who you think would benefit from using Composer.</p>
<p>Fletcher</p>
<p>On 9/17/17 10:39 AM, Raymond Brock wrote:</p>
</blockquote>
</blockquote></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T15:14:39Z2017-09-17T15:14:41Zsandboxing<div><p>hi<br>
Thanks for the quick response. I went through the App store, BTW. The upgrade buttons take you to the apple store with no redemption possibility. However, this is $30 well-spent if it fills my needs, which are intensive these days.</p>
<p>The file is actually a Jekyll-based document and functions fine in Typora and other markdown apps. Everyone deals with this apple sandbox security thing differently. I’ve attached it.</p>
<p>But actually, just sitting here doing something else the app crashed. When I brought it back up it said to send the crash report, two of which are attached. I’ve also pasted the Problem Report from the apple tool below. Tell me if there’s another multimarkdown-specific report?</p>
<p>thanks<br>
Ray</p>
<p>PS Does Multimarkdown Converter go from LaTeX to mmd also? Or just the other way around. I’m converting hundreds of pages of a textbook I wrote to mmd and Pandoc is sometimes squirrelly.</p></div>Raymond Brocktag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T15:40:50Z2017-09-17T15:40:50Zsandboxing<div><p>Ray,</p>
<ol>
<li>Correct -- there is no mechanism from Composer itself to redeem<br>
tokens. You have to use the App Store app, and in the main window there<br>
is a "redeem" link.</li>
</ol>
<p>My apologies for not making that clear, that was not my intent. And I<br>
certainly hope the $30 feels well spent after a couple of days</p>
<ol>
<li>
<p>Your doc uses explicit images (<code>![foo](/path/bar)</code>). If you change<br>
one of these (at the "highest" directory level, e.g. closest to the<br>
drive root) to a reference image (<code>![foo][bar]</code>, and <code>[bar]: /path/to/image</code>), that will trigger the sandboxing and it should work. You will need to save, close, and reopen your document (maybe twice).<br>
I'll fix explicit links for next release.</p>
</li>
<li>
<p>Thanks for sending crash reports -- I've never seen an issue there,<br>
so not sure what happened. I added a fix that should prevent the issue<br>
in next release. But this occurred during synchronized scrolling (e.g.<br>
when you scroll the editor, the preview scrolls with it). You can<br>
disable that functionality in the preferences to avoid another crash<br>
until the next version is released (later today??)</p>
</li>
<li>
<p>I don't create any tools to convert LaTeX to MMD. LaTeX is so<br>
complex, there's no way to do it "right." You can guess at the basics.<br>
I've got an idea that would allow this (for the basics), but it's part<br>
of a more complex project that may or may not make it off the ground.<br>
For the moment, pandoc is probably the best bet.</p>
</li>
</ol>
<p>F-</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T18:02:54Z2017-09-17T18:02:55Zsandboxing<div><p>hi<br>
Thanks…in-line question:</p>
<p>On Sep 17, 2017, at 11:40 AM, Fletcher > wrote:</p></div>Raymond Brocktag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T18:13:24Z2017-09-17T18:13:24Zsandboxing<div><p>Tender does strange things to inline editing -- was there another question that you had? I couldn't see one.</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T18:19:58Z2017-09-17T18:19:59Zsandboxing<div><p>Sorry… It was in response to:</p>
<ol>
<li>Your doc uses explicit images (<code>![foo](/path/bar)</code>). If you change<br>
one of these (at the "highest" directory level, e.g. closest to the<br>
drive root) to a reference image (<code>![foo][bar]</code>, and <code>[bar]: /path/to/image</code>), that will trigger the sandboxing and it should work. You will need to save, close, and reopen your document (maybe twice).<br>
I'll fix explicit links for next release.</li>
</ol>
<p>and was:</p>
<p>“</p>
<p>I’m not sure what you mean. First, many of the images in this file are html <img src… as the only way I could figure out to control the size of the image in the preview of most apps, like LightPaper and Typora. But should I go back to the markdown call to images (previous chapters have this mostly as I wanted to stay as close to mmd as possible and gave up at this point…) to something like</p>
<p><img src="../../assets/EM/figs/gilbert.png" alt="foo">{:width="500px"}<br>
<em>caption</em></p>
<p>How explicitly … and where in the file …are you suggesting the foo bar changes? I couldn’t parse your suggestion.</p>
<p>"</p>
<p>thanks for staying with me on what must be a busy day for you,<br>
Ray</p>
<p>On Sep 17, 2017, at 2:13 PM, Fletcher > wrote:</p></div>Raymond Brocktag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T18:43:29Z2017-09-17T18:43:29Zsandboxing<div><ol>
<li>
<p>HTML links won't work (unless there's another link to trigger asking<br>
for sandbox permission, like below).</p>
</li>
<li>
<p>If you trust that I am not doing anything nefarious, add something<br>
like this to your document:</p>
<p>![fake]</p>
<p>[fake]: /Users//fake.png</p>
</li>
</ol>
<p>This should trigger Composer to ask for read permission of your home<br>
directory. Any images inside that folder should now work (you may need<br>
to close and reopen to reset the cache).</p>
<ol>
<li>
<p>If you don't trust me, you can be more specific with the image path:</p>
<p>[fake]: /Users//some/folder/that/is/isolated/fake.png</p>
</li>
</ol>
<p>(But only images inside that folder will work -- the "higher up" that Composer can access, the more folders you can use without worrying about<br>
it).</p>
<p>F-</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T19:57:11Z2017-09-17T19:57:11Zsandboxing<div><p>hi<br>
Thanks. That indeed works, but of course I don’t have such an image and so I’ll always have a broken image in each file.</p>
<p>I hate to say it, but this seems sort of cumbersome. I can’t even use it to point to a legitimate folder/image since your second suggestion is an absolute path and I work on multiple computers where my home directory doesn’t always sit on the volume where references point.</p>
<p>I’ve had other apps ask for permission…and then that works from that point on without any skulduggery …that’s visible to the user. I see what the hidden skulduggery is now with your suggestion. Can you do something like that without going to Apple Jail?</p>
<p>thanks…sorry,<br>
Ray</p>
<p>BTW. I am not pointing to URLs (“links”) for images, just using HTML commands/tags inside of the markdown document. All pointing at the same image folders that I reference with mmd commands.</p>
<p>On Sep 17, 2017, at 2:43 PM, Fletcher > wrote:</p></div>Raymond Brocktag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T20:01:17Z2017-09-17T20:01:17Zsandboxing<div><p>Once you get the permission, you can delete the link. It's a one time<br>
thing (or until you reset preferences, or the permission expires). You<br>
don't have to do it in every document.</p>
<p>And again, the next release fixes the issue with explicit vs reference<br>
links.</p>
<p>F-</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-17T20:04:18Z2017-09-17T20:04:19Zsandboxing<div><p>ah. and hence the skulduggery.</p>
<p>Thanks<br>
Ray</p>
<p>On Sep 17, 2017, at 4:01 PM, Fletcher > wrote:</p></div>Raymond Brocktag:support.multimarkdown.com,2013-02-12:Comment/432254162017-09-18T22:19:37Z2017-09-18T22:19:37Zsandboxing<div><p>4.0.1 is out, and this should be fixed.</p>
<p>Thanks!</p>
<p>Fletcher</p></div>Fletcher