Comments for Tridion Developer

Comment on Special characters within Tridion webdav URL’s by SDL Tridion naming rules for items and WebDav | Tridion Developer

SDL Tridion naming rules for items and WebDav | Tridion Developer — Wed, 31 Mar 2010 16:04:12 +0000

[...] you simply must have special chars in your naming this post may help you should you ever need to obtain such items using [...]

Comment on Special characters within Tridion webdav URL’s by admin

admin — Thu, 11 Mar 2010 11:19:28 +0000

Hi Albert,

Thanks for the message, I’ve not actually had a play with the customisation framework, but it sounds like a great inclusion. I shall get it installed and have a play.

Regards,

Comment on Special characters within Tridion webdav URL’s by Albert Romkes

Albert Romkes — Wed, 10 Mar 2010 13:19:27 +0000

Maybe something went wrong when I submitted this comment the first time…

There is a customization framework (Created by Ryan O’Dell, supported by SDL Tridion), which provides a right-menu extension ‘Copy webdav path’. It works like a charm. No more typo’s. Of course, this table is useful when you don’t have that extension…

Comment on Special characters within Tridion webdav URL’s by admin

admin — Tue, 09 Mar 2010 19:08:52 +0000

Hi Bas, that's a great tip, thanks for sharing @Bas Bosman

Comment on Special characters within Tridion webdav URL’s by Bas Bosman

Bas Bosman — Tue, 09 Mar 2010 17:47:47 +0000

When working with for instance Components you can right click it, selecte Open with webdav and copy and past the Webdav URL from the browser address bar.

Doesn’t work for all item types, but it saves some typo’s.

Comment on SDL Releases Tridion 2009 Service pack 1 by Tridion Developer » Content Delivery API – GetTaxonomyComponentPresentations Bug

Fri, 26 Feb 2010 18:44:51 +0000

[...] a shame they have just released Service Pack 1 for WCMS 2009 as this would have been a nice issue to have resolved. I wonder if this will be resolved in [...]

Comment on Why won’t this publication delete? – Published items by admin

admin — Wed, 04 Feb 2009 08:14:50 +0000

Quirijn, thanks for the comments and feedback.

Erwin - thanks, there are a variety of reasons why unpublishing the whole publication will not work. Here are a couple of examples (i'm sure there are many more!):

1) There are X amount of published pages within a structure group. The structure group is modified so that it is no longer publishable. Unfortunately removing the right to publish also removes the right to unpublish.

2) Pages are checked-out

3) If the publication uses 2 different publication targets and all containing pages are published. Then the publication is modified to use only one publication target without the pages first being published.

The idea of the code published is to give you an idea where these pages are located, then you can do you own analysis as to why they are not unpublishing. I've recently written a little bit of code to search structure groups and set their isPublishable value to true, i'll post it later.

Comment on Why won’t this publication delete? – Published items by Erwin Sigterman

Erwin Sigterman — Wed, 04 Feb 2009 07:06:06 +0000

Why don’t you unpublish the whole publication before trying to delete it?

Comment on Why won’t this publication delete? – Published items by Quirijn

Quirijn — Tue, 03 Feb 2009 09:16:05 +0000

This is definitely a recognizable problem, and you have provided a helpful solution. Don’t forget by the way that there may also be components that are published dynamically. You would need to run a similar script to find those.
And why not unpublish them from the page template while you’re at it?
Set up an array with all the relevant publishing targets, and unpublish the pages and components once you have found them.