Hi Stefano,

I'm not an expert in the internal database structure of umbraco, but I would assume
that every template has an entry in db with it's own unique key-id. And the document types refer to this id, but not the name of the templates. So when you delete a referenced template and add a new one with same name, it neverless gets its new own key-id. This new one is of course not referenced by your existing doc types.

Simple solution: Update the doc type references to the templates manually in the Umbraco backend.

Difficuilt solution:

Create and add an package action handler which will do basicly follow steps:

- get the current id of the name of the template to replace, e.g. MyTemplate - ID: 1234
- remove this current template,
- rename your new added template to the old name (this is the template you are about to update, (to avoid the error you described you must give the update template inside the package a different name to the existing one, e.g. MyTemplate_Update)
- change the ID of this new added template back to the ID of the old one (1234).

For this solution you must be able to write C# code. For more informations refer to:
Package Actions Contrib.

May be helpful: For this way you can use my little Package Action Tester:
http://www.ucc-bln.de/en/2009/3/28/package-action-tester.aspx

Immo

Hi Stefano,

I agree with you that you shouldn' have these errors. when you load an updated package. But for deployment it's maybe better to just ftp your modified Master pages/xslt and Usercontrols.

Cheers,

Richard

---

level 2 certified - Umbraco development - Soeteman Software

Import data into Umbraco? Consider using UmbImport

Hi Stefano,

Yes this is how I do it. And then create a package for the new items. Agree it's not ideal but I don't do much updates after a site is deployed. Don't know if the problems your are facing now are reported on Codeplex Maybe that is good to do also. Because you cannot automatically update items using a package.

Now that I'm thinking of it, maybe this will help you (just a theory never tested it)

- create a package with the template
- Do some updates in your template
- Create an update package, ONLY INCLUDE the masterpage in that package (under package files), Do NOT select the template (under package Contents).

In theory this should work because you only overwrite the template file.

Please let me know if this worked (or not).

Cheers,

Richard

---

level 2 certified - Umbraco development - Soeteman Software

Import data into Umbraco? Consider using UmbImport