[ 
http://jira.magnolia-cms.com/browse/MGNLWEBDAV-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24993#action_24993
 ] 

Grégory Joseph commented on MGNLWEBDAV-22:
------------------------------------------

For the most part, this is simply due to files/directories that Dashcode 
attempts to create on the filesystem and are not allowed by the webdav module; 
allowing "all" files would create garbage in the repository. Not sure how to 
get about this. Maybe there's a dashcode-specific configuration to have it 
store its stuff elsewhere. Otoh, I'd argue that Dashcode isn't the tool you 
want to use to edit your Magnolia css files; it's probably mapped to css by 
default on your machine because either it's the last css editor you installed, 
.. or the only one that took over the file association.

> css files on osx get opened by Dashcode but cannot be saved
> -----------------------------------------------------------
>
>                 Key: MGNLWEBDAV-22
>                 URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-22
>             Project: Magnolia WebDAV Module
>          Issue Type: Bug
>         Environment: OSX
>            Reporter: Boris Kraft
>            Assignee: Jan Haderka
>
> css files are associated with Dashcode on my machine (no idea why) - double 
> clicking them will open Dashcode, and I can edit but not save the files.
> Dashcode says: The document "styles.css" could not be saved. The file does 
> not exist.
> Console says:  webdavfs_agent[15987]: unexpected statusCode 500

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to