Deleting resources - Revision history

Eshme: made this a redirect to the article this is in

2010-06-03T19:05:02Z

made this a redirect to the article this is in

ZeRux: Undo revision 10130 by Eshme (Talk)

2010-06-03T09:13:33Z

Undo revision 10130 by Eshme (Talk)

Eshme: Replaced content with 'obsolet'

2010-01-25T05:50:22Z

Replaced content with 'obsolet'

BryanDerksen: Category:Database

2009-08-21T21:24:42Z

Category:Database

BryanDerksen: split out of the resource palette page

2009-07-17T22:27:09Z

split out of the resource palette page

New page

A resource can't be deleted while it's [[checked out]]. To delete a resource, either check the resource back in or undo the checkout first. You can then delete it by selecting it in the resource palette and right-clicking on it to get a menu with the "delete" command.

To recover a deleted resource, select the "Deleted Resources" command from the "Tools" menu. This will bring up a deleted resource browser that allows you to examine and restore deleted resources.

== Dependencies ==

The toolset has some built-in safety mechanisms to ensure that resources don't wind up referencing nonexistent resources as dependencies. For example, it will refuse to delete a resource that another resource has as a dependency. If you had an area layout with a creature in it, you wouldn't be able to delete the creature's template from your database until you'd removed it from the area layout first.

This can interact with checked out resources in a potentially non-obvious way. If you check out the area layout and remove the creature, the toolset still won't let you delete the creature's template until you actually check in the layout. That's because if you were to delete the creature and then undo your area checkout you'd wind up with an area layout referencing a deleted creature template.

If you wish to delete resources, make sure that all of the other resources that may have depended on it are checked in beforehand.

=== Circular dependencies ===

It can sometimes occur that resource A references resource B, which references resource A. One set of resource where this is commonly possible are [[area]]s and [[stage]]s; an area references a stage that's placed in it, and the stage can itself reference the area. Another common pairing is a plot and its associated plot script.

The only way to delete resources involved in a circular dependency chain is to edit one or more of the resource to break the chain. For example, you could edit the area to remove the stage before deleting the stage, and then delete the area afterward. The toolset doesn't recognize a group of deletions as a single transaction.

← Older revision		Revision as of 21:24, 21 August 2009
Line 16:		Line 16:

	The only way to delete resources involved in a circular dependency chain is to edit one or more of the resource to break the chain. For example, you could edit the area to remove the stage before deleting the stage, and then delete the area afterward. The toolset doesn't recognize a group of deletions as a single transaction.		The only way to delete resources involved in a circular dependency chain is to edit one or more of the resource to break the chain. For example, you could edit the area to remove the stage before deleting the stage, and then delete the area afterward. The toolset doesn't recognize a group of deletions as a single transaction.
		+
		+	[[Category:Database]]

@@ Line 1: / Line 1: @@
-A resource can't be deleted while it's [[checked out]]. To delete a resource, either check the resource back in or undo the checkout first. You can then delete it by selecting it in the resource palette and right-clicking on it to get a menu with the "delete" command.
+#REDIRECT [[Designer_Resources#Deleting resources]]
-−
-To recover a deleted resource, select the "Deleted Resources" command from the "Tools" menu. This will bring up a deleted resource browser that allows you to examine and restore deleted resources.
-−
-== Dependencies ==
-−
-The toolset has some built-in safety mechanisms to ensure that resources don't wind up referencing nonexistent resources as dependencies. For example, it will refuse to delete a resource that another resource has as a dependency. If you had an area layout with a creature in it, you wouldn't be able to delete the creature's template from your database until you'd removed it from the area layout first.
-−
-This can interact with checked out resources in a potentially non-obvious way. If you check out the area layout and remove the creature, the toolset still won't let you delete the creature's template until you actually check in the layout. That's because if you were to delete the creature and then undo your area checkout you'd wind up with an area layout referencing a deleted creature template.
-−
-If you wish to delete resources, make sure that all of the other resources that may have depended on it are checked in beforehand.
-−
-=== Circular dependencies ===
-−
-It can sometimes occur that resource A references resource B, which references resource A. One set of resource where this is commonly possible are [[area]]s and [[stage]]s; an area references a stage that's placed in it, and the stage can itself reference the area. Another common pairing is a plot and its associated plot script.
-−
-The only way to delete resources involved in a circular dependency chain is to edit one or more of the resource to break the chain. For example, you could edit the area to remove the stage before deleting the stage, and then delete the area afterward. The toolset doesn't recognize a group of deletions as a single transaction.
-−
-[[Category:Database]]

← Older revision		Revision as of 09:13, 3 June 2010
Line 1:		Line 1:
−	~~obsolet~~	+	A resource can't be deleted while it's [[checked out]]. To delete a resource, either check the resource back in or undo the checkout first. You can then delete it by selecting it in the resource palette and right-clicking on it to get a menu with the "delete" command.
		+
		+	To recover a deleted resource, select the "Deleted Resources" command from the "Tools" menu. This will bring up a deleted resource browser that allows you to examine and restore deleted resources.
		+
		+	== Dependencies ==
		+
		+	The toolset has some built-in safety mechanisms to ensure that resources don't wind up referencing nonexistent resources as dependencies. For example, it will refuse to delete a resource that another resource has as a dependency. If you had an area layout with a creature in it, you wouldn't be able to delete the creature's template from your database until you'd removed it from the area layout first.
		+
		+	This can interact with checked out resources in a potentially non-obvious way. If you check out the area layout and remove the creature, the toolset still won't let you delete the creature's template until you actually check in the layout. That's because if you were to delete the creature and then undo your area checkout you'd wind up with an area layout referencing a deleted creature template.
		+
		+	If you wish to delete resources, make sure that all of the other resources that may have depended on it are checked in beforehand.
		+
		+	=== Circular dependencies ===
		+
		+	It can sometimes occur that resource A references resource B, which references resource A. One set of resource where this is commonly possible are [[area]]s and [[stage]]s; an area references a stage that's placed in it, and the stage can itself reference the area. Another common pairing is a plot and its associated plot script.
		+
		+	The only way to delete resources involved in a circular dependency chain is to edit one or more of the resource to break the chain. For example, you could edit the area to remove the stage before deleting the stage, and then delete the area afterward. The toolset doesn't recognize a group of deletions as a single transaction.
		+
		+	[[Category:Database]]