Timeline for Moving components/folders from child publication to parent publication without breaking its dependencies
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2013 at 19:44 | history | tweeted | twitter.com/#!/StackTridion/status/407596049302581248 | ||
| Nov 15, 2013 at 5:10 | comment | added | Alvin Reyes | Oh and if you have Experience Manager, Page Types, Content Types, and XPM's context settings will reduce this as well. | |
| Nov 15, 2013 at 5:08 | comment | added | Alvin Reyes | I've had colleagues suggest a higher threshold of 100 items (under 100 means authors get to do it). :-) A kindler approach is to remove write options from the children publications or remove scope if the authors shouldn't see those publications at all. Good mantra for authors: "what publication am I in?" | |
| Nov 14, 2013 at 2:35 | comment | added | Dylan .. Mark Saunders | I actually agree with Will here. The issue seems to be education (and punishment!) fix the root cause and not just resolve it technically. If it's 200 components - it's a punch and a technical solution; if it's <25 components - make them do it and learn a valuable lesson or the tool will just hide an issue of use. | |
| Nov 13, 2013 at 13:04 | vote | accept | Patan | ||
| Nov 13, 2013 at 11:49 | history | edited | Pankaj Gaur | CC BY-SA 3.0 |
added 1 characters in body
|
| Nov 13, 2013 at 11:40 | comment | added | Will Price | Have whoever created them in the wrong publication create them again in the right one, and re-link into the pages again, before deleting the old components - the frustration at having to do this will pretty much guarantee that they never make this mistake again ;o) | |
| Nov 13, 2013 at 10:48 | answer | added | johnwinter | timeline score: 9 | |
| Nov 13, 2013 at 10:37 | history | asked | Patan | CC BY-SA 3.0 |