My current work around is to use copy/paste of files in Windows rather than drag/drop.
In our style sheets and master pages we have some relative paths for images, or urls, similar to the following example from the Flare sample Top Navigation template.
Code: Select all
div.topic-hero
{
padding: 8% 0;
background-image: url('../Images/Hero-Image.png');
background-size: cover;
background-attachment: scroll;
}
I updated another feature in the global stylesheet (Styles.css) – for example, the color of the H1 tag – did not change anything with a path in it.
The templates are stored on our file server with a path something like the following:
Code: Select all
\\servername\techwriters\Projects\examples.flprj
Code: Select all
div.topic-hero
{
padding: 8% 0;
background-image: url('file://servername/techwriters/Projects/examples.flprj/Content/Resources/Images/Hero-Image.png');
background-size: cover;
background-attachment: scroll;
}
The URL to the image now has the file server path hard coded instead of a relative reference to the local image.
I don't think drag and drop should change the code like this - I want the file to come in as is.
When reading the help, there is an implication that you have a choice of importing (where processing might occur) or just copy/paste. In this instance I wanted to copy/paste but I did not get a choice.
This happened to URLs in style sheets and in master pages. I spotted the error when I was working remotely - it slowed the build down as it was constantly going back to the server to grab image files.