This request is related to another: http://dev.tiki.org/make+a+wish+-+thank+you?itemId=5052
I am trying to hide the internals of my trackers from the users as much as possible. In particular, I do not want them to have to understand how item-list fields work.
Say:
Tracker 1 includes an item-list field.
Tracker 1 has items a, b, and c
Tracker 2 includes an item-link field that points to tracker 1
Tracker 2 has items d, e, and f. Items d and e point to item a.
If the user deletes item (a), (d) and (e) are ophaned, so to speak. As the admin, I can go search for these and delete them on occasion, but it would be far better if these linked items were removed at the same time.
So the feature request is for a plugin that searches for orphaned items and deletes them. You might consider the following fields:
PluginTrackerRemoveOrphans
How I would use this:
I list the items of tracker 1 on a wiki page using pluginTrackerFilter. Let's say it is named "Catalog". A wiki template page is specified for formatting.
The template includes edit and delete links. The delete link is to a wiki page using pluginTracker or pluginRemoveItem (see http://dev.tiki.org/make+a+wish+-+thank+you?itemId=5052) to remove the item in tracker1. The URL field for this plugin points to a third page that uses PluginTrackerRemoveOrphans. The trackerId field is set to the ID for tracker 2, the confirm field is set to false so the action takes place without user action, and the URL field is set to "Catalog" so that the user returns to the original list of item - {PluginTrackerRemoveOrphans(trackerId="2", confirm='false", url="Catalog") \}.
The user has removed the item from the catalog and all items that linked to it, without knowing anything about the internals.
Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |