[MGNLWEBDAV-21] the extensions for the templates are mapped incorrectly on OSX Created: 16/Nov/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: WebDAV (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Boris Kraft Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OSX


Issue Links:
relation
is related to MGNLWEBDAV-22 css files on osx get opened by Dashco... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When mapping the templates repository via webdav, the template extension "ftl" is mapped to be executable and opened with a shell.
I cannot change that association with the finder assumably because Finder would try to write a property to the file, and can't because its mapped via webdav. In other words, I cannot open templates by double-clicking on them, but should be able to do so. I should at best be able to change that association through the finders info dialog, which allows me to set the association for every file.



 Comments   
Comment by Magnolia International [ 16/Nov/09 ]

Changing the association via the file's meta info can't work, because osx tries to write that information in the .DS_Store file (which we don't allow). Unfortunately, you'd need that to work to be able to then click "change all". Pro tip: change the association for one file on your machine, then "change all", and the association will indeed be changed for all files, including those on WebDAV.

You could also use an app like RCDefaultApp which provides a gui to do exactly that.

I'll investigate if allowing .DS_Store but silently not-creating-it would help (but that sounds like an open door for unwanted ugly side effects)

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 11:11:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.