tag:support.markedapp.com,2011-09-11:/discussions/problems/151578-custom-processor-permissions-in-2531Marked: Discussion 2019-02-26T20:53:51Ztag:support.markedapp.com,2011-09-11:Comment/470085642019-02-26T19:53:57Z2019-02-26T19:53:59ZCustom processor permissions in 2.5.31<div><p>I recently upgraded to 2.5.31 (non-MAS) and I'm now getting an "ERROR: Custom processor is not executable. Please ensure that your user has permission to execute pandoc" popup when I try to use pandoc. This also happens with a custom script that I've used for quite a while.</p>
<p>I've hit the "Update Permissions" button without much luck and, at least as far as I can tell, I should have the appropriate permissions for pandoc. Would it be possible to downgrade to an older version?</p></div>Scott Hartleytag:support.markedapp.com,2011-09-11:Comment/470085642019-02-26T20:13:48Z2019-02-26T20:13:48ZCustom processor permissions in 2.5.31<div><p>Uh oh. I'll definitely look into this right away, and in the meantime<br>
you can download <a href="https://updates.marked2app.com/Marked2.5.30969.zip">https://updates.marked2app.com/Marked2.5.30969.zip</a> to<br>
downgrade.</p>
<p>Thanks for the report.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/470085642019-02-26T20:32:49Z2019-02-26T20:32:49ZCustom processor permissions in 2.5.31<div><p>Fixed this. Updating to build 971 should fix the issue (in the<br>
auto-updater).</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/470085642019-02-26T20:45:11Z2019-02-26T20:45:12ZCustom processor permissions in 2.5.31<div><p>That did it. Thanks! I can't believe how quickly you took care of this.</p>
<p>For what it's worth, it seemed to hang when I used the auto-updater. I had to download fresh from the website. No idea if that was a weird glitch on my end.</p></div>Scott Hartleytag:support.markedapp.com,2011-09-11:Comment/470085642019-02-26T20:53:50Z2019-02-26T20:53:50ZCustom processor permissions in 2.5.31<div><p>Yep, I had the same issue. Short explanation is that a glitch in my<br>
build files accidentally turned on sandboxing for the direct version,<br>
which then caused issues with EVERYTHING. Hopefully not too many people<br>
grabbed that bad update before I fixed it, but I'm sure I'll be fielding<br>
a bunch of questions now :/.</p>
<p>Sorry about that, but again, thanks for reporting it so quickly.</p>
<p>Thanks,<br>
Brett</p></div>Brett