Having similar problems with 2.5.4.1.  I believe (I'm not 100% sure) that if, for example, a template references .css or image files, those should be included in the package.  However, when I select "Package all", I do not get those referenced files.  I do get all the documents, templates, etc.

I've also found that "Add" does not work, as I would have been OK with just adding my .css and images.

I also believe Per fixed a bug between 2.5.4 and 2.5.4.1 where the relationships among templates did not get packaged, and they do now in 2.5.4.1.

I would really like to either see 1) feedback from Umbraco that referenced files are not included or 2) get a version with a bug fix.  The feedback from Umbraco folks is a little spotty, so apparently you have to wait and hope for the best.

Hope this helps.

-- Paul

Hi Paul and Aileen

Havn't seen issues with templates not picking up files, got a concrete sample, with a template, linking to a file, that I can run through our tests? 

We did a fix between 2.5.4.1 and 2.5.4 to fix an issue with a certain way courier looks up unique IDs compared to node ids, which can affect packaging of templates

/Per

Hi Per

I don't seem to have an issue with dependencies. My issue is more to do with explicitly selecting an item to get packaged (with a whole lot of other items) and it not getting included in the package. For example I select 14 macros and say Add and then it list 13 i.e. Macros(13). Sometimes it includes all 14 macos and sometimes it includes 13.

Thanks, Aileen

Hi Per,

I'll try to work up an example that I can send to you.  I can't send company-specific data as my employer might not like that.  I also have 2 questions about Courier which I will add to the end of this post.

In the mean time, I'll try to be more specific.  I have a number of templates, and they reference other files. I was trying to use the "Package All" - which is what I'd expect our content editors to use, to make it easy for them, and the Package All did not include the files referenced in the templates. The two types that they reference are .css files and .jpg files.

1) I just realized that Courier may not recognize the .css files, as they are referenced by a tag which looks like this, rather than a standard <LINK> element:

<asp:Content ContentPlaceHolderID="cphHeadEnd" runat="server">
  <fvm:CssLink Url="~/css/gra-gnv/CustSite.css" runat="server" />
</asp:Content>

If that's the case, is there any other way to get Courier to transfer these .css files, i.e. can I explicitly include them in the revision some how?

2) the .jpg files are referenced as follows:

<asp:Content ContentPlaceHolderID="cphCust" runat="server">
        <a href="<%= Page.ResolveUrl(((MobileComponentMasterPage)Page.Master).CustomerSiteCurrent.RootAppPath) %>" ><img src="img/gra-gnv/btn_home.gif" /></a>

</asp:Content>

And thus, the <IMG> element is a child of the <A> element.

Should the above work?

Question 1)  Is there any way to have Courier only include the changes since the last Revision that was transferred, from the originating instance rather than the target instance?  It seems like you do have that choice on the receiving instance, but it might be more reassuring if you could limit the stuff being packaged on the originating instance.  Of course there may be technical reasons why that would be difficult to implement.

Question 2)  Is there anyway to have Courier push a revision across to the receiving instance (i.e. from Staging to Production) withouth having to review and approve the revision at the receiving instance?  I also realize there may be technical issues here, and as well, many users might want the additional approval step.

Thanks in advance,

-- Paul

Hi Per,

I performed some tests.  First, the good news: in a template, I referenced a .jpg file with an <IMG> tag, did a "Package All", and the .jpg did show up on the target instance.

Now the bad news. In the same template, I added:

     <link href="css/test.css" type="text/css" rel="stylesheet" />

the file test.css was not transferred, although the template with the change was transferred.

I think you should be able to reproduce this without me sending anything?

-- Paul

Hi Paul

I've put in a fix in the next version, but recommended way of references those css files are referencing their absolute path, by prefixing with a "/" or else courier will have no idea where to look for the file

/Per

Hi Per,

I prefixed with the "/", verified that the .css is still being used, then tried to transfer.  The .css still does not come across in the transfer.

Also, any answers for my other questions?

Thanks,

-- Paul

is working on a reply...