New message on opening a doc in B16
Running beta 16 on OS X 10.12.6.
I dl'd beta 16 just now and then opened a document I've opened a half-dozen times in past MMD betas and got a message I've never seen before (from MMD or any other program). After I chose the document from the file dialog, I immediately got another file dialog. The top line of this one says,
MMD Composer needs access to "<a path>" to read referenced in your document. Press "Open" to approve.
1. What is that message, and why is it happening? The <path> above is a subdirectory in my iCloud drive, the directory where the file I just opened lives. That file doesn't contain any references to other files; it contains two URL links to websites, but that's it.
2. What does "approving" do? Are we granting some permission to MMD (and if so what), are we updating permissions on the directory, what?
3. I canceled out of the dialog rather than clicking "Open", and I still have my file open in the editor. What did that not do that it wanted to do, and how (or will) editing this file be impacted?
4. On a very minor note, whatever that message is, it appears to be grammatically incorrect. I'm guessing there should be something between "read" and "referenced" in that sentence.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Fletcher on 19 Aug, 2017 07:04 PM
That's the message Composer uses to request read access to other files
when sandboxing is enabled. The typo is fixed in next build.
When you open a file, a sandboxed app is automatically given permission
to read that file, and that file only. Other files referenced by that
file are not accessible without explicit permission -- this includes
images, local css files, transcluded files, etc. Images on remote
servers are fine.
The next build has a slight tweak to make sure that the dialog is not
displayed when the count of local assets == 0. (It looked for changes,
but since undefined != 0, that still triggered a check). It also fixes
a bug whereby an empty asset caused the app to request access one
directory above that needed.
Once Composer obtains permission for a folder, it won't ask again, and
remembers permissions across restarts (they may eventually expire, but
it will just ask again if needed).
Unfortunately, to my knowledge, Apple does not provide a more elegant
way to do this. Would love to use something else if I can.
Fletcher closed this discussion on 19 Aug, 2017 07:22 PM.
Vince re-opened this discussion on 19 Aug, 2017 07:41 PM
2 Posted by Vince on 19 Aug, 2017 07:41 PM
I'll take that third paragraph to mean that this is a bug you've fixed since I have no external references in the file (IOW, I shouldn't be seeing the message). Thanks!
3 Posted by Vince on 19 Aug, 2017 07:46 PM
Also, you might consider restructuring the sentence. In the dialog that comes up, the message is cutoff if it's a long path, so maybe you could put the path at the end of the sentence. (By cutoff I mean we can't see it without manually widening the dialog window, not that it isn't there at all.) Just a thought.
Support Staff 4 Posted by Fletcher on 19 Aug, 2017 08:09 PM
Changed to appear on two lines.
Thanks!
Fletcher closed this discussion on 21 Aug, 2017 05:19 AM.